mirror of
https://github.com/vdr-projects/vdr.git
synced 2025-03-01 10:50:46 +00:00
d1b0368a15
VDR developer version 1.7.41 is now available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.41.tar.bz2
A 'diff' against the previous version is available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.40-1.7.41.diff
MD5 checksums:
c7928bff45fa1c0e6dadf2c0a5adf94b vdr-1.7.41.tar.bz2
d20f62005288f54bb4596e1e091419ac vdr-1.7.40-1.7.41.diff
WARNING:
========
This is a developer version. Even though I use it in my productive
environment, I strongly recommend that you only use it under controlled
conditions and for testing and debugging.
Approaching version 2.0.0:
==========================
If there are no more serious bug reports, the final version 2.0.0 of VDR
shall be released on March 31, 2013.
So please test this developer version intensely and report any problems
you might encounter as soon as possible.
The following language files still have the given number of untranslated texts:
da_DK.po: 134
el_GR.po: 197
hr_HR.po: 134
lt_LT.po: 1
nn_NO.po: 262
pt_PT.po: 28
sl_SI.po: 1
sr_SR.po: 80
tr_TR.po: 134
If nobody takes care of these, they will remain untranslated in version 2.0.0.
From the HISTORY file:
- Updated the Hungarian OSD texts (thanks to István Füley).
- Updated the Russian OSD texts (thanks to Oleg Roitburd).
- Updated the Polish OSD texts (thanks to Marek Nazarko).
- Fixed using PATH_MAX and NAME_MAX (+/-1 because the first one includes the
terminating 0, while the latter doesn't).
- The 'plugins' target of the VDR Makefile now also copies files matching the wildcard
"lib$$i-*.so" (previously only "libvdr-*.so") and also descends into subdirectories
of the plugin source.
- The parameters PATH and NAME to the --dirnames command line option may now be left
empty to use the default values if only ENC shall be set (thanks to Helmut Auer for
some improvements to this change).
- Fixed a possible "Channel not available" if a recording starts on a system with
bonded devices (thanks to Siegfried Bosch).
- Fixed stopping an ongoing recording on a system with bonded devices, if a timer with
a higher priority requires a different band.
- Updated the introductory text of the vdr.1 man page.
- Added a note to the INSTALL file regarding multiple disk setup becoming deprecated
in a future version of VDR.
- When switching to a less privileged user id, VDR now sets the environment variables
HOME, USER, LOGNAME and SHELL accordingly (thanks to Manuel Reimer).
- Updated the help and man page entry about the location of the epg.data file (thanks
to Ville Skyttä).
- Fixed creating a new VPS timer with the SVDRP command NEWT (thanks to Johann
Friedrichs).
57 lines
2.2 KiB
Plaintext
57 lines
2.2 KiB
Plaintext
Video Disk Recorder ('VDR') - Internationalization
|
|
--------------------------------------------------
|
|
|
|
The internationalized texts of VDR and its plugins use the 'gettext'
|
|
functionality. This file provides information on how to maintain
|
|
these texts. The instructions apply equally to VDR itself or any
|
|
plugin.
|
|
|
|
|
|
How to initiate internationalization support
|
|
--------------------------------------------
|
|
|
|
Not every plugin necessarily has texts that are visible to the
|
|
user, therefore there is by default no 'po' directory.
|
|
If your plugin source contains texts marked for translation
|
|
with tr(), you need to
|
|
|
|
- Change into the source directory.
|
|
- Enter the command 'mkdir po'.
|
|
|
|
After that, continue with "How to translate to a new language".
|
|
|
|
How to translate to a new language
|
|
----------------------------------
|
|
|
|
- Change into the source directory.
|
|
- Do a 'make i18n' to have the current *.pot file created.
|
|
- Make sure your locale is set to the language you want to
|
|
translate to.
|
|
- Change into the 'po' subdirectory and run 'msginit'. This
|
|
will create a new *.po file for your language.
|
|
- Edit the new *.po file and translate the texts.
|
|
You can do this either with your favorite text editor, or
|
|
with a specialized tool like POEdit, GTranslator, KBabel
|
|
or whatever you have.
|
|
|
|
How to maintain an existing language file
|
|
-----------------------------------------
|
|
|
|
- Change into the source directory.
|
|
- Do a 'make i18n' to have the *.po files brought up-to-date
|
|
with the texts in the source code.
|
|
- Edit the modified *.po file(s) and translate the texts.
|
|
If you are using a plain text editor, you should search for
|
|
empty strings ("") to find new, untranslated texts. Also,
|
|
look for the "fuzzy" keyword to find translations that have
|
|
been "guessed" from other, similar texts, and make sure they
|
|
are correct. After that you may want to remove the "fuzzy"
|
|
keyword. Specialized tools for maintaining translation
|
|
files may provide particular functions to guide you through
|
|
updating translations.
|
|
|
|
Once you have created or updated a translation file, please
|
|
send it to the maintainer of the respective plugin (in case
|
|
it belongs to a plugin) or to vdr@tvdr.de (for core VDR
|
|
language files).
|