I have a question regarding the behaviour and usage of the "unicode" attribute in the <glyph> element. The spec says the following....
"One or more Unicode characters indicating the sequence of Unicode characters which corresponds to this glyph. If a character is provided, then this glyph corresponds to the given Unicode character. If multiple characters are provided, then this glyph corresponds to the given sequence of Unicode characters. One use of a sequence of characters is ligatures. For example, if unicode="ffl"
, then the given glyph will be used to render the sequence of characters "f", "f", and "l". When determining the glyph(s) to draw a given character sequence, the 'font'
element is searched from its first 'glyph'
element to its last in logical order to see if the upcoming sequence of Unicode characters to be rendered matches the sequence of Unicode characters specified in
attribute for the given 'glyph'
element. The first successful match is used. Thus, the "ffl" ligature needs to be defined in the font before the "f" glyph; otherwise, the "ffl" will never be selected. "
First question, Does this statement stand same for mobile SVG? The reason, i think storing the upcoming sequence of characters dyanamically would cosume substantial processing time and code complexity?
Having said this, wouldn't it be just enough to perform/support just one-to-one matching of character(s) and glyph(s) simply ignoring the multiple character representation within the unicode attributes. Is there a possibility that we may miss the ligature "ffl" altogether or would we still be able to render the liagture using the individual glyph-unicode attributes "f", "f", and "l". Please keep in mind, this question regards to SVGT implementation.
Any reply, comments, or help would be appreciated.
Thanks in advance,