Re: Examples of translated RFCs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At 09:33 06/12/2005, Harald Tveit Alvestrand wrote:
Check this site out:
<http://rfc-jp.nic.ad.jp/>

I *think* it has at least a handful of RFCs translated into Japanese, but my Japanese skills aren't great enough to know if I found the ones that are there.

There's also <http://www.rfc-editor.org/language.html>, with links to Spanish and French translation indexes.

Others will have to say if the result has been useful to someone or not; if I read the tea leaves correctly, none have translated more than 100 RFCs.

Harald,
there is not a big need of translating RFC from English to other languages at the present time, people interested in RFC having some English, except for teaching purposes. As using the smallest charset RFC have limited translation problems (except when being political and an English term meeting cultural context translation problems). Also, RFCs describe the ASCII English Internet and many times need to be in English. The W3C document http://www.w3.org/International/questions/qa-i18n and ICANN efforts in the IDN area show the Internet community current low level of analysis in term of multilingualisation/multiculturalisation. The pending response to my IESG appeal will say how/where the IESG wants to see this analysis and support be carried.

So , IMHO, the IETF urgency is today the other way around: incorporating into RFC standards, practices or tables authoritatively written or thought in another language than English, or in English using normative non-ASCII art drafts or using term in a meaning foreign to the IETF.

This way we see the language is not the main issue of the current debate. The issue is the authoritative quote in community A a community B's, or of a searcher C's, normative document - while community A presents its documents in a different way - whithout affecting its normative capacity. This problem occurs when referencing in an RFC an ISO document as normative. The first issues being to write its URL properly if it includes non-ASCII characters, to properly name the authors and the references, to properly quote its copyright mentions and not to violate any law.
jfc



_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]