Juan Manuel Macías <maciasch...@posteo.net> writes: > [...] I am very interested in all possible improvements in babel so that > it integrates as best as possible with automatically generated files. > Among them are the possibility of using BCP47 codes or using a language > (at least basically) without the need for a prior declaration. These are > things already done, but there are others that can still be improved.
Do I understand correctly that babel, in future, may be able to auto-detect more languages without explicitly declaring them? > [...] any suggestion for improvement is very welcome [...] This is a bit too out of context. Improvement of what? > Among the things I agree on is name issue. I am unifying the dice in the > CLDR as much as possible, and already, in fact, it is very advanced: > > https://latex3.github.io/babel/guides/locale-naming.html AFAIU, the relevant quote is They are taken from the CLDR. Wherever the CLDR doesn’t provide a name (eg, “Medieval Latin”), the pattern followed in practice for other names is applied, namely, use the ‘natural’ form in English: medievallatin. They should be preferably based on the description field in the IANA registry (eg, polytonicgreek), although some simplifications can be necessary, because some names are “too” descriptive. See also the templates for about 500 locales already available. As a secondary source, Glottolog is used, too. (Wikipedia articles can be taken as a complementary but unreliable source, and its information must be verified; on the other hand, internal data, like this one, is useful for both names and tags.) I am not very sure about "some simplifications" referring to IANA. I guess it is referring to language names in https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry like "Puter idiom of Romansh". >From Org perspective, verbosity is not a primary concern as long as we provide #+language: completion support. Probably, we should favor names that are more likely known (or can be easily found) by the language users. IANA and https://glottolog.org/ look like good sources we can link to. We can also provide multiple language name variants though I don't see a need to bother unless we get user requests to do such thing. > The ini files contain information that is not actually used by babel, > but that could be useful in other packages or even external > applications. One of them is the name of the language in English and in > the vernacular form, as they are in the Unicode CLDR. As I explain in > the link I gave you, the purpose is that the babel name is based on the > CLDR name with mechanical changes. Anyway, CLDR names are also included > in the ini files, to establish correspondences more easily. Are the "verbose" language names (name.english) changed to "simplify" them? Or is it only done for name.babel? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>