<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>Another question on PO and XLIFF</TITLE> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2800.1498" name=GENERATOR></HEAD> <BODY> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>Hi Yves,</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>I think that what makes sense is to provide the string and let the editor decide how that is presented to the user (i.e. line wrapped).</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>Therefore, the following string:</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>Line 1\n line 2\nLine3.\n</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>is the one that makes sense.</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>The only drawback is that you don't have the convenience of round-trip testing of filters (mentioned by Rodolfo I believe) because the </FONT></SPAN><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>cosmetic line wrap in the PO source is gone forever.  </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>I think that since there is no functional effect at all, maybe it does not make sense to try to keep it, as it is only used for the "elegance" of being able to re-instating the original source bit per bit, so probably its practical application is a mirage, and on the other hand, normalizing the string to its one-line form per the representation guide, has some benefits for the tools who have to process them, and will avoid mix-ups with spaces in tag boundaries (as you can see in Rodofo's examples).</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>Please keep in mind that XML is to a large extent a free flow format and tools tend to make assupmtions in that sense, so if we avoid (unnecessary) line-oriented restrictions by design (ie forced by the representation guide), probably the implementations will simply work better.</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>However, just let me add that I think that C escape characters should be somehow tagged, at least by default. It helps many tools downstream (such as spellcheckers in XLIFF-aware tools, etc) make assumptions on what is text and what is code more easily.</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>Regards,</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2>Josep.</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005></SPAN><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=185230516-02052005></SPAN><SPAN class=185230516-02052005></SPAN><SPAN class=185230516-02052005></SPAN><SPAN class=185230516-02052005></SPAN><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN><SPAN class=185230516-02052005></SPAN><SPAN class=185230516-02052005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><FONT face=Arial color=#0000ff size=2></FONT><FONT face=Arial color=#0000ff size=2></FONT><FONT face=Arial color=#0000ff size=2></FONT><BR> <DIV class=OutlookMessageHeader lang=es dir=ltr align=left> <HR tabIndex=-1> <FONT face=Tahoma size=2><B>De:</B> xliff-tools-bounces@lists.freedesktop.org [mailto:xliff-tools-bounces@lists.freedesktop.org] <B>En nombre de </B>Yves Savourel<BR><B>Enviado el:</B> lunes, 02 de mayo de 2005 14:55<BR><B>Para:</B> xliff-tools@lists.freedesktop.org<BR><B>Asunto:</B> [xliff-tools] Another question on PO and XLIFF<BR></FONT><BR></DIV> <DIV></DIV> <P><FONT face="Courier New" size=2>Hi,</FONT> </P> <P><FONT face="Courier New" size=2>I have a new question on XLIFF representation of PO.</FONT> <BR><FONT face="Courier New" size=2>The guide (</FONT><A href="http://xliff-tools.freedesktop.org/wiki/Projects_2fXliffPoGuideDraft2"><U><FONT face="Courier New" color=#0000ff size=2>http://xliff-tools.freedesktop.org/wiki/Projects_2fXliffPoGuideDraft2</FONT></U></A><FONT face="Courier New" size=2>) does not seem to say anything about multi-line entries. </FONT></P> <P><FONT face="Courier New" size=2>msgid ""</FONT> <BR><FONT face="Courier New" size=2>"Line 1\n line 2\n"</FONT> <BR><FONT face="Courier New" size=2>"Line 3.\n"</FONT> </P> <P><FONT face="Courier New" size=2>How this should be represented?</FONT> </P> <P><FONT face="Courier New" size=2><trans-unit xml:space="preserve"></FONT> </P> <P><FONT face="Courier New" size=2>Line 1\n line 2\n</FONT> <BR><FONT face="Courier New" size=2>Line 3.\n</trans-unit></FONT> </P> <P><FONT face="Courier New" size=2>Or </FONT></P> <P><FONT face="Courier New" size=2><trans-unit xml:space="preserve"></FONT> <BR><FONT face="Courier New" size=2>Line 1\n</FONT> <BR><FONT face="Courier New" size=2> line 2\n</FONT> <BR><FONT face="Courier New" size=2>Line 3.\n</FONT> <BR><FONT face="Courier New" size=2></trans-unit></FONT> </P> <P><FONT face="Courier New" size=2>Or</FONT> </P> <P><FONT face="Courier New" size=2><trans-unit xml:space="preserve"></FONT> <BR><FONT face="Courier New" size=2>Line 1</FONT> <BR><FONT face="Courier New" size=2> line 2</FONT> <BR><FONT face="Courier New" size=2>Line 3.</FONT> <BR><FONT face="Courier New" size=2></trans-unit></FONT> </P> <P><FONT face="Courier New" size=2>?</FONT> </P> <P><FONT face="Courier New" size=2>The third seems more logical to me, but it could cause issues too, for example if the line-breaks are not \n but \r or \r\n (if the PO file is used for a non-Unix application) how would we know which type of line-break notation to put ack when merging.</FONT></P> <P><FONT face="Courier New" size=2>Anyhow, a section on this topic would be good to have in the Guide.</FONT> </P> <P><FONT face="Courier New" size=2>Cheers,</FONT> <BR><FONT face="Courier New" size=2>-yves</FONT> </P></BODY></HTML>