[MPEG-OTSPEC] Many to many substitution and localization

[William_J_G Overington]

A correction, a suggestion, and a question please.
 
Previously, I wrote as follows.
 
quote
 
For example, please consider that a sequence !983 in a document is 
replaced by its localization into a language chosen by the person 
reading the text.
 
For example, for localization into Welsh.
 
sub !983 -> D i o l c h space a m space y m w e l d period ;
 
Yet maybe the following method of expressing such a rule could be 
allowed for convenience, to become encoded exactly the same as the above 
within the font.
 
sub !983 -> #Diolch_am_ymweld. ;
 
end quote
 
I expressed the left side of the substitution rules incorrectly.
 
The corrected versions of the substitution rules are as follows.
 
sub exclam nine eight three -> D i o l c h space a m space y m w e l d 
period ;
 
sub exclam nine eight three -> #Diolch_am_ymweld. ;
 
----
 
I am thinking that this suggested new facility could possibly be 
produced by adapting a copy of the liga table, changing the name and 
having four integers for each substitution rule.
 
The four integers being as follows.
 
startOfThisGlyphIndexSequence: integer;
 
endOfThisGlyphIndexSequence: integer;
 
startOfThisCharacterString: integer;
 
endOfThisCharacterString: integer;
 
These would point to locations within two arrays, each defined just once 
for the whole font.
 
allOfTheGlyphIndexSequences: array of integer;
 
allOfTheCharacterStrings: array of char;
 
The allOfTheGlyphIndexSequences array is so that displays of the 
localized text can be produced, both on screen and in exported printed 
documents.
 
The inclusion of the allOfTheCharacterStrings array is so that if the 
localized text in electronic character form is desired then the 
rendering system could produce it from the content of the original 
document and some of the content of the allOfTheCharacterStrings array.
 
----
 
What needs to be done, by me or by others, for the suggestion in this 
thread to become formally considered for inclusion in the standard 
please?
 
William Overington
 
Monday 30 September 2024
 
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20240930/b2366670/attachment.htm>