<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
On Thu, 2005-04-14 at 09:56 +1000, Asgeir Frimannsson wrote:<BR>
<BR>
Hi,<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Please speak up if you're against changing the guide to use a similar approach </FONT>
<FONT COLOR="#000000">to the the one described below, as if not I will update the guide to reflect </FONT>
<FONT COLOR="#000000">these changes over the weekend.</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
I'm not against your approach, but I think it is also not totally correct. If you want to put something in the <source> element, it must be the content of the header present in the POT file. That's the real source. <BR>
<BR>
Having the original header in the source will introduce garbage in TM systems. When <source> is empty and <target> has text, there is data for only one language and TM systems discard the entry. But if there is an old version of the header in <source> and a newer version in the <target> then there will be data for two languages and garbage will be stored. I say garbage because source language would normally be set to en-US, while <source> data corresponds to something else.<BR>
<BR>
I can modify the reference implementation to match this new approach easily, but please define it tomorrow at the latest. <BR>
<BR>
We, at Heartsome, are planning to release a new version of our tools on Sunday. This means that we are almost in code freeze now. I want to include the new PO converter in this release and I would like this version to be compliant with Representation Guide.<BR>
<BR>
Regards,<BR>
Rodolfo<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Rodolfo M. Raya <<A HREF="mailto:rodolfo@heartsome.net">rodolfo@heartsome.net</A>><BR>
Heartsome Holdings Pte Ltd
</TD>
</TR>
</TABLE>
</BODY>
</HTML>