Line 41: |
Line 41: |
| The workaround is to find and replace the problem code | | The workaround is to find and replace the problem code |
| | | |
− | this needs work, when creating the first po files
| + | Create a clean .po file with newpo, either edit your lexicon or add s///g commands to workaround new problems |
− | :br maybe shouldn't be used testing
| + | |
| + | After you have a clean english .po you can use that as a template and copy and paste the translation in, |
| + | it's better to do it on pootle, you get fewer errors, at least use pootle for multiline and cdata. |
| | | |
| ====newpo==== | | ====newpo==== |
Line 134: |
Line 136: |
| perl -i.old -ne 'print unless 1 .. 1' $1.xml | | perl -i.old -ne 'print unless 1 .. 1' $1.xml |
| | | |
− | #rm $1.bak $1.xml.old | + | rm $1.bak $1.xml.old |
| | | |
| if [ ${#2} -gt 0 ] | | if [ ${#2} -gt 0 ] |
Line 186: |
Line 188: |
| <trans>Mise à jour logicielle</trans> | | <trans>Mise à jour logicielle</trans> |
| </entry> | | </entry> |
− |
| |
− | ===subversion===
| |
− | This is a test case,
| |
− |
| |
− | something is wrong with the encoding in some places, eg view .po
| |
− |
| |
− | After you have a clean english .po you can use that as a template and copy and paste the translation in, maybe do it on pootle, you get fewer errors, at least use pootle for multiline and cdata. I don't see an easier way
| |
| | | |
| ==Console== | | ==Console== |
Line 205: |
Line 200: |
| .po file names are inconsistent, SV & FR add .tmpl.po | | .po file names are inconsistent, SV & FR add .tmpl.po |
| : .tmpl.po is correct, other languages have been updated | | : .tmpl.po is correct, other languages have been updated |
− |
| |
| | | |
| | | |