Adding Languages to Writer's Character, Font Menu

[Eike Rathke]

Hi Khaled,

On Monday, 2015-06-29 20:40:46 +0200, Khaled Hosny wrote:

> > > The script is generally implicit in the text.
> > 
> > You want to rely on automatic detection of scripts depending on the
> > language chosen? Do you plan to implement that? However, even then the
> > resulting tag would include the script code if it wasn't the default
> > script of the language.
> 
> Almost every character in Unicode has a script property, the exceptions
> is characters that has Inherit (unusually combining marks) or Common
> (punctuation mostly), put there is a simple and pretty reliable way to
> resolve the script of those characters from the context.
> 
> We already handle this at the text shaping level in VCL for platforms
> where HarfBuzz is used.

I think we talk about two different things here. My view is from correct
language tag attribution that we need anyway, for document storage and
spell-checkers and locale dependent representation. When I mention
"language tag" I'm always talking about BCP 47 language tags. You, and
possibly Richard, have the runtime view and what could be automatically
detected. So, even if detected automatically we'll have to assign
a language tag that for the non-default script of a language includes
the ISO 15924 script code.

We could of course come up with a huge table of all scripts and possible
languages associated with each and present things entirely different in
the UI. But, for MSO interoperability and ODF conformance we'll have to
stick with the (to me) unfortunate and arbitrary "Western"/CTL/CJK
classification in which we'll have to squeeze all language tags. The
correct route to go is probably to assign known scripts to these
classes, whether detected automatically or not, and distribute language
tags according to their (implied or not) script over those classes.

  Eike

-- 
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GPG key "ID" 0x65632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A
Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/
Care about Free Software, support the FSFE https://fsfe.org/support/?erack
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/libreoffice/attachments/20150630/97697632/attachment.sig>