From: Aaron V. <gru...@gm...> - 2011-09-20 18:15:48
|
I guess I'll leave it to Markus since he's volunteering. But out of curiosity, it's preferred to use new values 0, 1, ... instead of making them equal to the kCGEncodingMacRoman, kCGEncodingFontSpecific values? --Aaron On Tue, Sep 20, 2011 at 2:32 AM, Panayotis Katsaloulis <pan...@pa...> wrote: > > On 20 Σεπ 2011, at 8:45 π.μ., Aaron VonderHaar wrote: > >> Oh, thanks for catching that! I had put it off since I didn't quite >> have time to figure out how the other kCG* constants were implemented, >> and apparently forgot to come back to it. >> > > This is how they are usually implemented: > > > @XMLVMSkeletonOnly > public final class CGTextEncoding { > > public static final int FontSpecific = 0; > public static final int MacRoman = 1; > > private CGTextEncoding() { > } > } > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > |