Changes between Version 10 and Version 11 of translateeffort


Ignore:
Timestamp:
Mar 30, 2015 1:22:29 PM (5 years ago)
Author:
zzz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • translateeffort

    v10 v11  
     1== Welcome to the I2P Translation help page! ==
     2
     3Please help spread the word about I2P by translating the application and the website to YOUR language!
     4
    15All translation is now done on Transifex: https://www.transifex.com/projects/p/I2P/
    26
     
    3236Copy and edit, then let us know on IRC #i2p-dev where to get it, we will copy it in.
    3337
     38We know this is a pain, we are working to migrate the remaining resources to Transifex.
     39
    3440=== Related I2P Projects ===
    3541
    3642Put links to associated projects and Transifex pages here
    3743
     44- i2pd: Does not support translations yet
     45
     46- Vuze: ?
     47
     48- others?
     49
    3850=== Tips on Formatting and Strings ===
     51
     52- All translated files must be in UTF-8. If you use the Transifex editor, this will happen automatically. If you do your translations offline and upload the new po file, please ensure it is UTF-8.
     53
     54==== Most non-website resources ====
    3955
    4056- Strings should never include a trailing \n
    4157
    42 - In any string containing {0}, single quotes ' must be escaped as TWO single quotes ''
    43 This is a Java requirement.
     58- In any string containing {0}, single quotes ' must be escaped as TWO single quotes '' This is a Java requirement.
    4459
    45 - Website rules are different
     60==== Website rules are different ====
    4661
    47 - Website Strings containing % symbols
    48 Several translators have posted issues about problems translating strings containing a % symbol as part of the text (e.g. "Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time?"). These strings have now been fixed. The % symbols have been replaced with their HTML code % and this code should be used instead of % in the translation as well. Please mark your open issues relating to this bug as resolved when you translate the string.
     62- Website Strings containing % symbols: Several translators have posted issues about problems translating strings containing a % symbol as part of the text (e.g. "Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time?"). These strings have now been fixed. The % symbols have been replaced with their HTML code % and this code should be used instead of % in the translation as well. Please mark your open issues relating to this bug as resolved when you translate the string.
     63
     64- Doesn't matter if you include the \n or keep them in the same place as the English string
    4965
    5066=== Other Helpful Hints ===
     
    6682==== Plugins ====
    6783
    68 itoopie: released periodically
     84
    6985
    7086I2P-Bote has not had a release in a while, but hopefully will soon.
     
    7288
    7389==== Other Applications ====
     90
     91itoopie: released periodically
    7492
    7593Robert has not had a release in years.
     
    8199==== Website ====
    82100
    83 Strings updated occasionally. Translate anytime.
     101Strings updated occasionally. Translate anytime. If you do not see your updates on the live website https://geti2p.net/ after several weeks, remind us on IRC #i2p-dev to pull the new translations.
     102
     103=== Testing ===
     104
     105To test your new translations, get the I2P source https;//geti2p.net/get and the "tx" program (in your favorite package manager), then do 'tx pull' then 'ant updater'. Copy i2pupdate.zip to ~/.i2p and restart. More info: https://geti2p.net/newdevelopers
    84106
    85107=== Per-string "issues" ===
    86108
    87 Hi! I see several of you are using the new "issues" feature to identify problems with individual strings. That's great, but we didn't see this feature coming and don't really have anybody at the moment to go through the issues, research, fix in monotone, and respond in tx. We're working to find a volunteer and we'll let you know. Don't stop filing issues if that's the way you'd like to do it, but please be patient.
     109Several of you are using the new "issues" feature to identify problems with individual strings. That's great, but we didn't see this feature coming and don't really have anybody at the moment to go through the issues, research, fix in monotone, and respond in tx. We're working to find a volunteer and we'll let you know. Don't stop filing issues if that's the way you'd like to do it, but please be patient.
    88110
    89111I also see a few issues that are really questions. For those, the best way to do research on what a string really means is to look in a running copy of I2P, or get the source from monotone or github. The po files in the source have a cross-reference to the source code for each string, if you need to find the exact line in the code defining the string. The 'poedit' tool may help here. You may also get faster answers on IRC #i2p-dev.