French spaces

Fragment of a discussion from Support
Jump to navigation Jump to search
Edited by 2 users.
Last edit: 06:23, 13 November 2019

Oh wow, new personal attacks, did you run out of arguments?

I'm sorry but your sources are completely off-topic and your walls of text where you state your personal opinions as facts are not backed with any proof.

You fail to see the reality where your thin spaces are not compatible everywhere and that we must use non-breaking spaces for the time being. Translations must be accessible to everyone, no matter what their browser/device is.

And they ARE accessible to anyone. "Accessibility" is absolutely not a concern even on your sample image for your device. These are still spaces semantically with just "instructions" for prefered rendering, and they are just hints that renderers will adapt according to the device (even yours) and its capabilities. In your case, the Apple fonts you use already embed their wider gaps for punctuation, and so that font (built for UI) does not need to increase it more. Apple uses AAT rules in these legacy fonts. For newer fonts (including the new one that replaced the former legacy non-Unicode font "Helvetica Neue" or the even former font "Helvetica" for old MacOS and never used on any iPhone/iPad/iWear), Apple maps the NNSP (which is mapped since long in Times which is the default for the web in serif style (remember that serif is the default web style in all browsers, Mediawiki changes it to use a sans-serif if possible, and on MacOSX/iOS this uses the legacy UI font; newer OSes will use better fonts, no longer needing proprietary AAT and based only on standard OpenType features, and these fonts map the NNBSP beczause they don't "tweak" the punctuations as Apple did in its legacy fonts not built for Unicode and using Mac-specific mappings for encodings without full Unicode support
Apple however has tuned its renderer to use fallback fonts, that are NOT modifiable at all, so that all spaces are rendered internally according to the first font: all legacy mappings in legacy fonts will discard any other fallback, because these fonts were specially tuned in their metrics and AAT positioning rules to insert the extra gap contextually: Apple voluntarily dropped any insertion of NNBSP or THINSP, or HAIRSP and other thin space, tuning it for its own proprietary UI; iof you use any browser and use the default settings with just language settings and no prefered font choice, Apple uses its system UI font, mappings, and AAT rules directly; it never requires any additional mapping; if you set your browser to use alter nate fonts for wider language coverage, Apple OSes will honior your request, and will render the NNBSP that are mapped in these fonts like Times, and now can also infer synthetize all missing mappings for whitespaces without EVER rendering a "missing glyph" box like it did in very old MacOS with 32-bit Motorola 68K, but never on any iOS or MacOSX device; these old MacOS are not even usable today with any modern browser capable of using any Mediawiki site, and if they still run, it is for geeks capable to tweak the fonts and setup many complex workarounds to bypass the limitations, or that also accept the total lack of support needed for modern accesssiblity features: these old Mac for example cannot work with Braille readers, and any way they no longer have any supported web browser, so their users must have found a way to run some severay tweaked and simplified version of Unix/Linux but also without any support). Verdy p (talk) 23:23, 12 November 2019 (UTC)
Thibaut (talk)22:33, 12 November 2019