As seen in a recent controversial node [PT_BR] Escrever em Português no Perlmonks, an important question was raised. The support for i18n (internationalization) in the Perl Monks site.
The support for i18n inside the web application is important to allow people only reading posts in languages each monk can read, and giving the opportunity to post multilingual nodes (like, one textarea for each language) Using special tags to say which part of the node is in which language.
In an attempt to summarize the suggestions in that node and start a more productive discussion (considering i18n would be good for the perl monks site), I'd like to state some goals we could achieve to make this community more inclusive.
Update: Changing some things following suggestions
- Translation of the perl monks site engine (which would be as simple as bring low benefits).
Including the configuration of which language a monk can read (and stablish priorities), and which language a monk can write. Obtain the preferred languages from the monk's user agent and consider his priorities.
- Allowing multi-lingual posts, allowing a monk to submit a node in English *and* in Portuguese, for instance, at the time of the writing. Using tags to specify which parts are in which language.
- Showing only the parts of a node the monk can read, using the language with the highest priority to choose the translation, like the readmore tag, the parts in languages
other than the highest priority one that the monk can't read would be hidden by default.
When a node (that a monk is able to read) doesn't have a translation for a language that the monk can write, give the opportunity for him to translate that (like the "Offer your reply", something like "Offer your translation")
Give some type of bonus to a monk which translates a lot of nodes (to help more nodes to be translated) and for monks who writes in several languages at once.
I think this could create a more inclusive environment without creating noise with nodes that people just can't understand.
As I don't know the perlmonks source code, I don't know how hard it is to do this changes, and I'd like to know at first stage to hear what the other monks have to say about this idea.
daniel
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.