RE: Translation of i18n articles

Hello Gunnar,

[Copying in core wg, for notification of changes.]

> Are the keywords (<meta name="keywords" content="i18n [.]">) to be
translated?
> Me thinks, search engines do not care for them anymore.

I'll leave that up to you.  Please translate the descriptions, however,
since they tend to show up in search results etc.

> In "intended audience," what does "XHTML/HTML coders (using editors or
> scripting)" mean? I'm not sure about the "scripting." Does "editors" refer
to web
> page editors (like M$ Frontpage), and "scripting" refers to text editors
(like
> M$ Notepad)?

'Scripting' is meant to capture pages that are automatically or
semi-automatically generated rather than just created by hand.  For example,
some pages are created from information in databases using a scripting
language like PHP.


> This might be nitpicking, but as I understand the XML specification,
section 4.1
> [http://www.w3.org/TR/xml#dt-entref] "character entity" and "character
entity
> reference" are not synonyms. 'nbsp' would be the name of an entity;
'&nbsp;'
> would be an entity reference. I translated "character entity" as
"character entity
> reference" whenever it was used in that meaning.

There isn't any sequence of words 'character entity' in the XML 1.0 spec.
Something like &nbsp; is just called an entity reference.  HTML4, however,
does call it a character entity reference.  I think you are right to call
&nbsp; a character entity reference, following the HTML4 terminology, and I
think I possibly ought to change the English to that too.  We did originally
just use 'character entity' to make it easier for laypersons to distinguish
from 'numeric character reference'. 

 (I made some quick notes on usage at http://rishida.net/blog/?page_id=147 )

I made a number of changes to the English text. I attached a copy to this
email.  If you do a diff, you should be able to spot the differences fairly
easily.


> might want to point this out in the English original article. In my
translation, I
> wrote "Position 80 (hexadezimal)".

Done. Thanks.


> I used "ISO 8859-1" instead of "ISO Latin-1" as the name of the encoding,
hope
> that's OK. ("Latin-1" would not be understood in German, anyway, I guess.)

Sure.  Whatever is best understood. Latin-1 tends to be used more in English
than the numbers for that particular code page.


> Finally, where did you get the text passage in Czech language from? My
girlfriend
> who speaks Czech and works in the event management at Daimler told me it
> could be taken from them. ;-)

That's funny.  I picked up that text many years ago, and I unfortunately no
longer remember exactly where from.

Thanks for the comments, Gunnar.  Very useful!

Best,
RI


============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)
 
http://www.w3.org/International/
http://rishida.net/blog/
http://rishida.net/

 

> -----Original Message-----
> From: gunnar.bittersmann@web.de [mailto:gunnar.bittersmann@web.de]
> Sent: 25 March 2008 02:39
> To: ishida@w3.org
> Subject: RE: Translation of i18n articles