[MPEG-OTSPEC] Many to many substitution and localization

[William_J_G Overington]

Laurence Penney replied.
 
Thank you for replying.
 
Laurence Penney wrote as follows.
 
> However your method transforms one *glyph* sequence into another 
> *glyph* sequence, and would have the serious drawback that the text, 
> when selected by the recipient, would still yield the original 
> *characters* — something meaningless like "!313125".
 
Not exactly meaningless, the original characters would be the 
language-independent encoding of a localizable sentence, either, as in 
this example, within some of my research publications, or in an ISO 
standard document if the localizable sentences system becomes an 
international standard.
 
However, whilst recognizing that the font table for this feature would 
have a list of glyph numbers so that the rendering software could 
produce the display, the specification for the font table for this 
feature could also include a field to contain the localized text version 
of the sentence expressed as a character string, and that field could be 
accessed by the software of the rendering system if a character version 
of the displayed text is required to be exported.
 
> Going back to your goal, character sequences should be manipulated 
> outside of fonts, not within fonts.
 
A font does not contain software for a virtual machine, it contains data 
for use by software that runs outside the font.
 
My idea is a way of storing data that are localized versions of some 
particular sentences within a font. Applying that data would be carried 
out by software in the rendering system. The rendering system already 
has, in the way it can apply the liga table, software for detecting a 
specified sequence of characters in a string of text. The liga table has 
one glyph specified on the right side of the arrow in a substitution 
rule, for this idea there would be many glyphs specified on the right 
side of the arrow.
 
William Overington
Friday 27 September 2024
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20240927/cfd4d100/attachment.htm>