Mental note #2: the difference between both of Hilmar's AFM files is exactly 26 hours, up to the second.
>@@ -1,6 +1,6 @@ > StartFontMetrics 2.0 > Comment Generated by FontForge 20230101 >-Comment Creation Date: Wed Nov 26 08:23:11 2025 >+Comment Creation Date: Tue Nov 25 06:23:11 2025 > FontName bkaiu02 > FullName AR PL KaitiM Big5 02 > FamilyName AR PL KaitiM Big5 Mental note #3: the AFM uses a localised version of the "digit", i.e. a dot for Anglo-Saxon, and a comma for continental European countries. Funny, I would have guessed that the AFM format always uses locale C (and therefore a dot) and that FontForge would stick to a dot. @@ -10,8 +10,8 @@ Comment Subfont version 2025-11-25. ItalicAngle 0 IsFixedPitch true -UnderlinePosition -96,6797 -UnderlineThickness 48,8281 +UnderlinePosition -96.6797 +UnderlineThickness 48.8281 Version 2.10 EncodingScheme FontSpecific FontBBox -12425 -6536 7690 22253 I suspect a clock issue, and a locale issue. Cheers, -- Danai On Thu, 27 Nov 2025 at 15:55, Preuße, Hilmar <[email protected]> wrote: > On 11/27/2025 6:26 AM, Danai SAE-HAN (韓達耐) wrote: > > Hello, > > > Okay, mental note #1: > > With "debuild" (without parallel jobs) I am getting the same AFM font > > content with each build (and I did 3x): > > > > > Comment Generated by FontForge 20230101 > > > Comment Creation Date: Wed Nov 26 02:23:11 2025 > > > > I just inspected just the deb packages, which were in the artifact of > Salsa CI. > The files are meanwhile deleted on the server, so the test needs to be > re-enabled to get a new set. > > Hilmar > -- > sigfault > >
