It's just a pattern, so we all know that always be "xx-YY" for ALL languages and not "xx" for that one and for the other, but for another it is "xx-YY", i guess! See! To avoid more things to think about!
I've just made an admonition: "en-EN" does not exists. If we follow a pattern, it will be one less thing to be concerned about. :-) 2010/2/20 Viktor Szakáts <harbour...@syenar.hu>: >> It's better to use "en-US", to better distinguish from others and to >> avoid mistakes. We should always follow the pattern "xx-YY". > > Why not 'en-GB' then? I still don't see a good reason to > limit us to any specific dialect, moreover the more > complicated and doubtful we make it, the higher the chances > for a mistake (someone may use 'en', or 'en-GB', or just > miss the casing and there we are). Also, 'en' looks standard > and valid language code. [country ID is optional according > to RFC.] > > Brgds, > Viktor > >> >> 2010/2/20 Viktor Szakáts <harbour...@syenar.hu>: >>> Hi Daniel, >>> >>>>>> For example, suppose I want to contribute documenting the hbsqlit3 >>>>>> contrib, wich is module I'm very interested. What I'm suposed to do? >>>>>> Create a directory /harbour/doc/en-EN/contrib/hbsqlit3 and write text >>>>>> files in NF format? >>>>> >>>>> All contribs are meant to be independent from >>>>> core, so their docs should be stored in >>>>> /contrib/<name>/doc/en-EN/* >>>>> >>>> >>>> I searched for this "en-EN" locale identifier and it does not exists >>>> [1], [2] and [3]. >>>> It must be changed to "en-US". >>>> >>>> [1] http://tools.ietf.org/html/rfc5646 >>>> [2] http://www.i18nguy.com/unicode/language-identifiers.html >>>> [3] http://en.wikipedia.org/wiki/Language_code >>> >>> Or rather plain 'en'? Can you confirm, if this is >>> the valid ID for dialect-neutral English language? >>> >>> [ Unless we want to even have separate 'US' and 'GB' >>> English dialect docs, which I believe we don't. ] >>> >>> Brgds, >>> Viktor >>> >>> _______________________________________________ >>> Harbour mailing list (attachment size limit: 40KB) >>> Harbour@harbour-project.org >>> http://lists.harbour-project.org/mailman/listinfo/harbour >>> >>> >> >> >> >> -- >> Daniel Gonçalves >> Base4 Sistemas Ltda. >> [www.base4.com.br] >> [twitter.com/spanazzi] >> _______________________________________________ >> Harbour mailing list (attachment size limit: 40KB) >> Harbour@harbour-project.org >> http://lists.harbour-project.org/mailman/listinfo/harbour > > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour > > -- Daniel Gonçalves Base4 Sistemas Ltda. [www.base4.com.br] [twitter.com/spanazzi] _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
