>> The idea that Knowledge Representation must occur in English means >> those that speak it poorly, and many others fail to reach the people >> who are part of the constituency and as such they fall short of the >> IETF's capabilities to deliver. They also may actually become victims
>> of the language barrier > >If we had a normative XML format, that can easily be translated into both >viewable and printable HTML, then one could imagine a project to translate >all the RFCs into many languages in conjunction with Google Translate. >This particular translation tool offers the user the possibility of >correcting an inadequate translation. The tool learns >from these corrections and therefore the translations of later RFCs >would be more accurate even before a human gets involved. The normative version needs to be in one language though, and English has historically been that language for RFCs. Note that you can always cut and paste a document, or provide a URL, to Google Translate in order to get a translation - and that doesn't require any changes to IETF process. - Wes _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
