2

I'm trying to create a glossary in some LaTeX variant, and I want to insert etymologies like this:

دَفْتَر • (daftar) m (plural دَفَاتِر‎ (dafātir)): From Middle Persian dptl (daftar), from Aramaic דפתרא‎ / ܕܦܬܪܐ‎, from Ancient Greek διφθέρα (diphthéra).

The raw text looks fine in my browser, and in Gedit, and in my terminal. The fonts are all there. However, when I try to follow various instructions to typeset languages in LaTeX I run into problems. I should use XeTeX, which is OK, but then I have to run a bunch of commands like \newfontfamily and \setotherlanguage and then wrap "language-switching" commands like \textgreek and \texthebrew and \textarabic around every language transition. I can't even find a \textaramaic command, does the script have a different name?

I'm not very concerned about appearances, I just want something that prints a formatted glossary where the various words in each language are legible. Is there no "plug-and-play" method for handling multilingual Unicode text in TeX-derived typesetting languages?

Maybe the best solution would be to output HTML and print from the browser? I guess the other alternative is to use Perl to insert TeX markup around each detected language, using a bunch of regular expressions: qr/\p{Arabic}/. But that seems cumbersome...

  • 3
    it is possible to get an approximation to automatic direction detection so if you have a font that covers all the scripts you need you can avoid any markup at the language switches if you do not need language specific hyphenation – David Carlisle Sep 6 '18 at 20:30
  • 2
    although I'd have thought you wanted markup here to give more flexibility in layout choices, eg \newcommand\fromgreek[1]{from Ancient Greek \textgreek{#1}} would allow markup like \fromgreek{διφθέρα} in your entries. – David Carlisle Sep 6 '18 at 20:34
  • How do I "get an approximation to automatic direction detection"? That is what is missing from Davislor's answer, I tried ucharclasses and it works but typesets each Arabic word RTL but consecutive words are LTR. This is something that Firefox and Gedit get right without any help (e.g. they don't need Unicode bidi markers to correctly render sequences of RTL words). – Metamorphic Sep 7 '18 at 19:22
  • actually the approximation for xetex may not be that close , see for example tex.stackexchange.com/questions/403075/… browsers are of course far more modern architecture and using (typically) an off the shelf c++ bidi library fits them well, for tex, even xetex it's harder to fit in to the model and never been that high priority as you normally need to switch other things, fonts, hyphenation, ... as well as direction so "just" referencing a bidi algorithm would be hard to do but probably not that useful in many cases. – David Carlisle Sep 7 '18 at 20:18
3

Updated Answer

As of TeX Live 2020, babel is able to select the correct language automatically based on the script you use in the source, with a command such as

\babelprovide[import, onchar=ids fonts]{greek}

If you then select a \babelfont for Greek, it will also select that font with an appropriate Script= and Language= option, e.g.

\babelfont{rm}[Ligatures=Common]{CMU Serif}

Unfortunately, ucharclasses is broken in current versions of XeLaTeX and never worked with other engines at all.

Original Answer

The package ucharclasses gives a way to do something like that. If you give it a command such as

\usepackage{fontspec}

\defaultfontfeatures{Scale=MatchUppercase, Ligatures=TeX}

\newfontfamily{\defaultfont}{Latin Modern Roman}[Scale=1.0, Ligatures={Common, TeX}]
\newfontfamily{\malayalamfont}{Arial Unicode MS}

\usepackage[Malayalam]{ucharclasses}

\setDefaultTransitions{\defaultfont}{}
\setTransitionTo{Malayalam}{\malayalamfont}

you can then simply start typing in Malayalam. (If your font contains OpenType Script and Language support, you probably want to turn that on as well.) Here is the documentation.

This can’t work in absolutely every case because the same Unicode codepoints might mean something different in different languages, such as Bulgarian and Russian or Japanese and traditional Chinese. You don’t get the same hyphenation support you would from Polyglossia or Babel, and so on. I personally prefer the semantic markup. But, you can come as close as most documents will need.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.