On 27/02/2013 10:38 PM, Cha, Hojeong wrote: > Hello everyone, > > I think many developers have an interest in learning Rust via tutorial. > But the current tutorial is written in English, so it precludes many > potential developers which English is not his/her native language. > > So I thought that it would be beneficial to internationalize Rust > documents, or at least have a base-level work for internationalization.
Great! I'm sorry we've been negligent on this front so far; it's simply a matter of lack of available effort / small size of team. We'll absolutely work on improving our i18n/l10n support. We should probably build a gettext-like syntax extension into the compiler (to mimic the _(...) macro) and start moving our strings into .po files too. > There would be many ways that such internationalization can be done, and > I tried to find the tool which is familiar to the developers and able to > update documents whenever the original document had changed; "gettext" > came into my mind, so I lightly prototyped it (in my native tongue, Korean): > > https://gist.github.com/karipe/330d1ce1f0dbbf67abf0#file-tutorial_ko-md > > I would like to hear your opinions about this way of internationalization. Interesting. I am not familiar enough with the mechanisms mozilla generally uses for doc-translation vs. other strings (messages in programs etc.) but I will look into it and follow up. Suggestions welcome from anyone who's been on a translation team. I know we do use .po files and gettext for quite a lot of such things, and operate a pootle server for coordinating several teams. -Graydon _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
