[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff-comment] Storing plural forms with XLIFF
Hi Jan-Arve, > Thank you for your response. Yes, I can see that > they use the group method. > Does anybody know the rationale for them using a > <group restype="x-gettext-plurals"> and > not <alt-trans> units? I would think <alt-trans> role is different, mostly it's used to store pre-translation for a given <trans-unit>. So if you were using it for the PO plural forms you would have no way to store possible translation candidate. In fact, my previous example was incorrect: you probably would not get a target text in <target state='new'>, you would expect the source text there or nothing, and possible translation in <alt-trans>. Something like: <group restype="x-gettext-plurals"> <trans-unit id="1[0]" xml:space="preserve"> <source xml:lang='en'>%n files</source> <target xml:lang='pl' state="new">%n files</target> <alt-trans quality-match='100%'> <target xml:lang='pl'>%n plik</target> <alt-trans> <alt-trans quality-match='100%'> <target xml:lang='pl'>%n pliki</target> <alt-trans> </trans-unit> <trans-unit id="1[1]" xml:space="preserve"> <source xml:lang='en'>%n files</source> <target xml:lang='pl' state="new">%n files</target> <alt-trans quality-match='100%'> <target xml:lang='pl'>%n plik</target> <alt-trans> <alt-trans quality-match='100%'> <target xml:lang='pl'>%n pliki</target> <alt-trans> </trans-unit> ...Etc... Hope it helps. -yves
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]