It's better to use "en-US", to better distinguish from others and to avoid mistakes. We should always follow the pattern "xx-YY".
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
