Cross Platform Font Layout - current workarounds

Sean Cole (Pi) sean at
Tue Aug 25 19:24:11 EDT 2020


thanks for the response although only partially addressing the issue. That
article (the first one to come up on a google search, so well done on your
'research') is aimed at web layout in a browser. NOTHING to do with desktop
platform rendering which is a wholly different subject. And the writers
'hack' is not universal and only works based on that particular font. A
very makeshift workaround (which is what we are incumbent on because of all
the bugs (below) not yet ironed out - AFTER MANY YEARS!)

Heres a far more relevant article by, yep, Adobe. Look at the OpenType
fonts section. The fonts I use are ALWAYS otf. Without fail. As Adobe says,
"OpenType fonts use a single font file for both Windows and Macintosh
computers, so you can move files from one platform to another without
worrying about font substitution and other problems that cause text to
reflow". They are platform agnostic. There are some caveats, for sure, but
within the constraints of LC with its own engine, these won't apply. An OTF
installed on ANY platform (other than a browser) will render identically
with regards size, shape, height, line height, kerning and so on. There's
no variance. It's pure mathematics. That's the point! (

Spelling it out to you, here are all of the related bug reports. Confirmed
bug reports. Confirmed they are bugs. Bugs that Can and Should be fixed. It
won't take 10s of 1000s of $ as whatshisface Gaskin made it seem. I have
and DO code workarounds for it all the sodding time. But CODE
ONCE!!!!!!!!!!!!!!!!!!!! Pfft, CODE ONCE. I AM SICK OF ALL THIS BS BEING
THROWN BACK AT ME as if it's me that caused the issue. SERIOUSLY!!!!!! YOU
all MAKE ME WILD with all your apologist brushing off and glossing over.
MAKE IT FLIPPIN WORK!!!! (sideways related) (Related and listed by
none other than Whatshisface Gaskin himself!)

Plus all of the 'Duplicate' references therein.

If you are changing font or having to use different font between system I
can FULLY understand why they would appear different. Even something like
Arial in one system is bound to not be exactly the same font in both
systems. I totally accept that fact and have to deal with it accordingly.

BUT if the font is a custom, professionally made font or even a freebie
crap font, installed on both systems they should appear the same size (the
point size is not some arbitrary number) with the same fixed line height
and formattedHeight (again, not arbitrary) with identical baselines
calculated in exactly the same way. It's basic maths. It's an engine fault,
not a system one. It requires a teeny bit of scientific testing with some
custom fonts between platforms.


Based on the above reports and others like them, it's evident I'm not
making this up, or being precious or getting worked up over NOTHING! We
should get what we pay for and what LC advertise on their virtual box
(landing page).   *I* didn't say it's CODE ONCE.    *THEY* put it like
that! If it's not something LC can live up to they should change it. You
can barely code once anything in lc that is cross-platform. Seriously,
prove me wrong! But don't demonise me. I wasn't the one to make the claim.
I'm pointing out how false it is and trying to get things working as they
should. And certainly don't try to pull the wool over my eyes with
incredibly badly thought out reasoning. I'm done with people fobbing me

Sean Cole
*Pi Digital *

On Tue, 25 Aug 2020 at 19:51, Mark Waddingham via use-livecode <
use-livecode at> wrote:

> On 2020-08-24 21:49, Sean Cole (Pi) via use-livecode wrote:
> > My client provided the font they needed in line with their tv show
> > brand.
> > They need the app to work both PC and Mac. It seems I have to manually
> > go
> > through each field, button and widget and make sure they are laid out
> > properly. The left, right, center alignments don't always match and the
> > vertical position certainly never matches.
> >
> >
> I suspect the main issue with vertical alignment here is to do with the
> font.
> This very readable article contains the relevant information here as
> well as how the problem can be resolved:
> <
> >
> TL;DR; version - the custom font probably does not have the correct
> settings/tables for use in programs which use the system text engines on
> *both* Mac and Windows.
> FWIW, LiveCode fields try to match the way the running platform displays
> text in OS editable fields.
> Specifically, text in a field on macOS will look almost the same as that
> in TextEdit; and text in a field on Windows will look almost the same as
> that in WordPad (DPI differences taken into account - LC assumes 72dpi,
> Win assumes 96dpi).
> Unfortunately this means you do need to do some work (i.e. scripting) if
> you want to use LiveCode fields in more 'graphical' situations - e.g. as
> the labels on custom buttons.
> Warmest Regards,
> Mark.
> P.S. It is perfectly possible that fettling with the metrics detailed in
> the article above would mean you could achieve identical vertical layout
> on macOS and Windows but it isn't something I have actually tried.
> --
> Mark Waddingham ~ mark at ~
> LiveCode: Everyone can create app
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the use-livecode mailing list