-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change from pidgin-TeX to UTF-8 #1364
Comments
Hmmm, we already have some As for BCP codes you are aware of the discussions in #160 and #961 and also #1362. At the moment everything we do in |
I'd say we need (as a community) to be making these kind of moves: see what we did with the kernel to shift to UTF-8 but leave a way 'out'. Really there should be very few non-UTF-8 docs nowadays, and people probably need to be told that they have to be re-encoded. BCP-47 is more tricky, but it's what we've moved to for the language-dependent code in Perhaps I should ask other team membrs to take a look too? |
I agree that UTF-8 is the way to go, but if we were to recode existing files here, old documents in BCP-47 would be great if there were an interface we as package maintainers could use. At the moment we have to piece together |
We've made a start with |
One of the goals in |
Thanks, I will once I have the time to investigate this properly. For now I can probably only give you the big picture: We need a way to interface with language switching using a fixed naming system (so either using What made #1362 difficult for us is that we're used to users saying they want a language called |
Basically \documentclass{article}
\usepackage[english]{babel}
\babelprovide{spanish} % import=es by default
\babelprovide[import=es]{medievalspanish}
\babelprovide[import=es]{classicalspanish}
\LocaleForEach{%
\getlocaleproperty\babelname{#1}{identification/name.babel}%
\message{^^J --- #1 === \babelname}}
\stop (Some locales provide several babel names. The preferred one is the first.) You may want to modify the imported file: \babelprovide[import=es,
identification/tag.bcp47 = es-x-medieval,
identification/extension.x.tag.bcp47 = medieval]
{medievalspanish} |
Would it be possible to convert the LBX files that are still in pidgin-TeX to UTF-8, and also change their name to BCP-47?
I ask because we do use the files in other suites like "text2bib", "bbl2bib", ... and have been thinking about using it "on the fly" so that when a new supported languages comes up in BibLaTeX, we automatically support it.
The change of names to BCP-47 would help us (easierly) identify families of laguages and support them appropriately, which is one of the reasons for BCP-47 existence.
I can do the work of the conversion of the files myself, especially if we have a suite of tests for before/after the change, but I do not understand how the files are called by biblatex.
The text was updated successfully, but these errors were encountered: