Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" 
for change notification.

The "SurrogatePairs" page has been changed by SimoneRondelli:
https://wiki.apache.org/xmlgraphics-fop/SurrogatePairs?action=diff&rev1=1&rev2=2

  Font <----------------------------------- + mapCodePoint(int):int
  }}}
  
- getUnicode(): is defined in CIDSet (is not a property of the Typeface class 
or one of its subclasses). I changed the firm of this method to handle int 
instead of char because it is semantically incorrect to represent unicode with 
a single UTF-16 char. As you can see from the CIDSet hierarchy the change 
affect only 3 classes.
+ `getUnicode()`: is defined in CIDSet (is not a property of the Typeface class 
or one of its subclasses). I changed the firm of this method to handle int 
instead of char because it is semantically incorrect to represent unicode with 
a single UTF-16 char. As you can see from the CIDSet hierarchy the change 
affect only 3 classes.
  
- getUnicodeFromGID(): this method is defined in CustomFont and CIDSet. It 
never get called from the MultiByteFont path, probably because getUnicode is 
used instead. That is why I'm down casting the return value from int to char in 
CIDFull and CIDSubset. Probably the best thing to do would be to get rid of 
this method or make it handle int, but again the change would affect more 
classes then the ones in the scope.
+ `getUnicodeFromGID()`: this method is defined in CustomFont and CIDSet. It 
never get called from the MultiByteFont path, probably because getUnicode is 
used instead. That is why I'm down casting the return value from int to char in 
CIDFull and CIDSubset. Probably the best thing to do would be to get rid of 
this method or make it handle int, but again the change would affect more 
classes then the ones in the scope.
  
  == Convert surrogate pairs to a single int ==
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to