Op Do, 2010-02-25 om 11:13 -0600 skryf Laurent Marchal: > Hello all, Hallo Laurent
> I am using pootle to translate XLIFF files generated from > java.properties files. I looked at the documentation, but I can't find > the answer to my problem. The tool that I use to export .properties > files into XLIFF, generates a simple XLIFF format like this (here > without header) > > </trans-unit> > <trans-unit id="LoginDialog_LoginMessage" xml:space="preserve"> > <source xml:lang="en">Please login.</source> > <target xml:lang="fr">Veuiller vous identifier</target> > </trans-unit> > <trans-unit id="LoginDialog_LoginTitle" xml:space="preserve"> > <source xml:lang="en">Login</source> > <target xml:lang="fr">Identification</target> > </trans-unit> > > > My problem is that pootle mark the all the translated French strings as > Fuzzy when I import this file. So the translators can not just translate > the untranslated string, because they have to view also the fuzzy > strings when they click on "quick translate". Pootle interprets the "approved" attribute to decide if an XLIFF unit is presented in the user interface as fuzzy or not. The default value of the attribute is "no", and nothing is specified in your file. This is in effect why they are shown as fuzzy. Which tool are you using to create the XLIFF files? Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/hunspell-osx-106 ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
