> 2026/02/25 20:22、Jürgen Spitzmüller <[email protected]>のメール:
>
> Am Mittwoch, dem 25.02.2026 um 20:11 +0900 schrieb Yokota K.:
>> Polyglossia seems to assume fonts should be set explicitly at least
>> in global usage. Given that we adopt a policy to pick up
>> polyglossia’s default value as is, I’d like to propose to change the
>> default setting for the language package in UI to be “none” instead
>> of “default”.
>
> This will not work.
>
>> Current LyX settings force its use even when multilingual is not
>> needed.
>
> Polyglossia is not only for multilinual documents. You cannot write a
> monolingual German, French, Italian, or Spanish document without it (or
> Babel). Even English would be difficult.
I see.
>> A bad thing is it simply cannot produce a document for writers whose
>> document language uses non-Latin letters. I’m almost sure that a
>> beginner of LyX cannot resolve this by his own efforts (and please
>> imagine its consequences).
>
> For cases which use a different approach than polyglossia or babel
> (such as Japanese if I understand correctly), there would probably need
> to be a special case.
That’ll be nice. At this moment, the problem is confined to polyglossia with
XeTeX or LuaTeX.
Similar treatments should go with other languages that Latin Modern font (in
most of cases) does not cover. Qt classifies fonts by writing system here
though I’m not sure it’s complete:
https://doc.qt.io/qt-6/qfontdatabase.html#WritingSystem-enum
> But what if I use German passages in a Japanese document? This even
> happens if I load the Japanese User Guide in a German l7n (due to info
> insets being localized to German then).
In that case, we can simply use polyglossia. It actually works fine, just
lacking an appropriate default font settings in use with XeTeX and LuaTeX.
Koji
--
lyx-devel mailing list
[email protected]
https://lists.lyx.org/mailman/listinfo/lyx-devel
