Hello, In lot of gettext files (example subversion-1.4.0/subversion/po/fr.po) each entry seems to be preceeded with the filename and line number where the text string to be translated was found. Example: #: include/svn_error_codes.h:313 msgid "Invalid lock" msgstr "Verrou invalide"
In XLIFF file format, the trans-unit element (http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm#trans-unit) can take an attribute called extradata which seems like a good place where we can put where this string was found. It would help manage the i18m file if we can have some indication where the string was found. Example: <trans-unit id="7" extradata="/projects/symfony/project345/apps/frontend/templates/layout.php:566"> <source>Email</source> <target></target> </trans-unit> It can even have coma seperated list of places. I am not too familiar with XML. Is there a limit a value of an attribute can have? Is there a better xliff attribute to put that in? Is that what the <file> element is for? Is that info considered completly useless? Would that be too hard to implement? If the <file> element is what this is for, then it would look like: <xliff version="1.0"> <file original="/path/to/layout.php" source-language="en_US" datatype="plaintext" date="2006-10-27T03:15:49Z"> <body> <trans-unit id="1"> <source>foo</source> <target/> </trans-unit> </body> </file> <file original="/path/to/templateSuccess.php" source-language="en_US" datatype="plaintext" date="2006-10-27T03:15:49Z"> <body> <trans-unit id="1"> <source>bar</source> <target/> <context> </trans-unit> </body> </file> </xliff> Right? Or maybe you have to use the context-gruop and context with the sourcefile and linenumber attributes? As you can see, I am not familiar with xliff that much. :) Opinions? -- Christian Roy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs -~----------~----~----~----~------~----~------~--~---
