tl2020 pretest begin

[Norbert Preining]

Hi Ken,

> "recommended" way to look at the files, so that the desired encoding
> will be obeyed ?  And if so, do the files need some markings to say

There are a few editors (yudit eg) that try hard to guess the correct
encoding. But as I wrote, if you don't know which encoding is used, it
is a wild guess and can come up as rubbish.

> understand Norbert's comment about what people use in Japan) it is
> at least semi-legible (although in Han probably at least ugly, and

Depends. In the euenc/utf case you might end up with parts readable and
parts unreadable, a case I often see in emails I get which don't specify
the encoding. Or it might be completely unreadable besides the ascii
parts. Most encodings agree on the ascii part, so that is the only one
that comes through in most cases.

> Clearly, any change needs to be on a per-package basis, but is there
> actually an approach to changing them which will work ?

Yes, knowledge of the content and manual inspection. But nothing
automatic.

Norbert

--
PREINING Norbert                              https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13