RE: BP 24: what's all that about?

Hi Richard,

> Text surrounded by <...> is just content, not markup, so 
> I think you would handle it for translation, spell-checking etc 
> in just the same way as other content, wouldn't you? 
> ie, yes, if you wanted it not to be translated you'd need an element 
> around it to which to attach a no translate flag - just as you 
> would with any other content. 

You cannot. That is the whole problem: that "content" is not normal content, it's XML/HTML placed into an XML element. For example
we cannot add ITS/other markup in it to specify what is translatable or not: such extra markup would be in the way when using the
XML/HTML data.

You are not talking about *examples* here, but real used XML/HTML data used outside the XML document. Here the XML document is just
a temporary repository, but that is the file we have to deal with.

For example in

"<top>&lt;span class="h1"&gt;Elibur Library&lt;/span&gt; - Conversation Groups</top>"

you cannot add markup in the content of <top> because it is used as

"<span class="h1">Elibur Library</span> - Conversation Groups"

by whatever application processes the file.


> PS: We should check that we have surrounded any examples 
> in the actual BP doc with no translate flags.

Sure, if the XSLT template can manage to do this automatically. But we cannot put such markup in the source files themselves since
they are real XML files.

Cheers,
-yves

Received on Wednesday, 5 December 2007 12:35:28 UTC