mirror of
https://github.com/vdr-projects/vdr.git
synced 2025-03-01 10:50:46 +00:00
ea01358b3b
- Updated the Italian OSD texts (thanks to Diego Pierotto). - Fixed wrong bracketing in cChannel::SubtitlingType() etc. (thanks to Rolf Ahrenberg). - Fixed not logging changes for channels that have no number (reported by Timothy D. Lenz). - Changed the project's URLs and email to tvdr.de. - Added Lithuanian language translations (thanks to Valdemaras Pipiras). - Updated Chinese language texts (thanks to Nan Feng). - Only checking DVB_API_VERSION to be >=5 in order to stay compileable in case the DVB API version number is increased (the API claims to always be backward compatible). - Fixed saving terminal settings when running in background (thanks to Manuel Reimer). - Fixed cFrameDetector::Analyze() to handle video streams where the frame type is not detectable from the first TS packet of a frame. - Fixed writing the PCR pid into the PMT in cPatPmtGenerator::GeneratePmt() (reported by Rene van den Braken). - Added Slovakian language texts (thanks to Milan Hrala). - Fixed EntriesOnSameFileSystem() to avoid using f_fsid, which may be 0 (thanks to Frank Schmirler). - Fixed starting a recording at an I-frame. - Fixed generating the index for recordings from channels that put a whole GOP into one payload unit. - The index file for TS recordings is now regenerated on-the-fly if a recording is replayed that has no index. This can also be used to re-create a broken index file by manually deleting the index file and then replaying the recording (at least until the index file has been generated). - The cRingBufferLinear::Read() function now returns -1 and sets errno to EAGAIN if the buffer is already full. - Fixed handling DVB subtitles for PES recordings (thanks to Rolf Ahrenberg). - Added the audio id to the call of PlayAudio() in cDevice::PlayTsAudio() (thanks to Andreas Schaefers). - Fixed references to old *.vdr file names in MANUAL (reported by Arthur Konovalov). - Reverted "Removed limitation to PAL resolution from SPU handling" because it cause nothing but trouble. Besides, the core VDR doesn't use this, anyway. - Fixed the default value for "Pause key handling" in the MANUAL (reported by Diego Pierotto).
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 kls@tvdr.de (for core VDR
|
|
language files).
|