[MPEG-OTSPEC] Many to many substitution and localization

[William_J_G Overington]

Simon Cozens replied.
 
Thank you for replying.
 
Simon Cozens wrote as follows.
 
> 4) Ensure that you're using the terms of the specification precisely. 
> For example, there is no such thing as a "liga table" in the 
> OFF specification, so it's hard for other people to follow what you 
> mean when you say you want to "adapt a copy" of it. To do 
> this, you may need to read, and possibly even understand, the 
> specification.
 
Yes, thank you.
 
I have now rewritten that paragraph. Here is the revised text.
 
I am thinking that this suggested new layout feature could possibly be 
produced by a person who is writing software for a fontmaking program 
adapting a copy of the software that implements the liga layout feature, 
changing the name from liga to become a presently unused four lowercase 
letter sequence, and having four integers for each substitution rule.
 
The four integers being
 
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.
 
William Overington
 
Monday 30 September 2024
  
  
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20240930/344c8421/attachment.htm>