Hmm, if I understand you correctly, this is most unfortunate -- though perhaps convenient for you!
It sounds as if they have mapped these glyphs to the first block in Unicode (ISO-10646), which are the same as ASCII (ISO-646). But, in fact, they are no such thing. (Well, maybe they are, since they're just a remapping of the latin characters, but they're certainly not USEFUL like that). As a consequence, you can't simultaneously display Roslien and English. Ideally, what you'd do is to remap them to the private use area, then take the existing input method, and substitute Roslien characters. Anyway, let me clarify the model a bit for you. Fonts are not the same thing as characters. Characters are abstract semantic entities. In a particular coding system, e.g. Unicode, they are mapped to code points -- those are the numbers. (And then UTF-8 is an ENCODING scheme for unicode -- yet another layer). Fonts, on the other hand, contain the graphical representations, called glyphs. Ideally, they'd map from characters to glyphs, but what they in fact map from code points to glyphs, and thus are tied to a particular coding system. But that's because there's no other machine- capable system for denoting characters. (Unicode has one, but using that would be equivalent to using the Unicode code points). Actually, what I wrote above is an over-simplification. A glyph is really the ABSTRACT thing that a font has a particular stylized graphical representation of a glyph. And there's yet another layer -- graphemes are made up of one or more glyphs. But I said I was going to clarify things for you, didn't I? OK, here's the deal. Unicode represents characters -- pretty much all of the human writing systems are incorporated at this point. You have a set of characters that aren't in Unicode -- that's where the private use area is supposed to come into play. But you have a font that accepts ASCII characters -- that is, first block of Unicode characters. It's basically a font designed to MANGLE ENGLISH into Roslien. That is, it's deliberately broken. When you type using the regular English keyboard, you're taking advantage of this breakage. You're entering Unicode -- with english content, but the font is then mis-displaying it as Roslien. Well, that's less work for you, and it allows you to play the game of taking English text and having it appear as Roslien -- and challenging yourself to decode it back into English. But that's not using Roslien characters at all! Just their glyphs, misplaced. Unless yo're making a product, or want to learn this stuff, you probably want to stop there, and say "mission accomplished". If you want to sell something on the app store, though, I'd recommend actually remapping the font, and creating an input method/keyboard for Roslien. On Feb 27, 4:07 am, Takami Labs <[email protected]> wrote: > To be more specific , this is the piece of code I use to display the > "Roslien font" on my message box: > Typeface face = Typeface.createFromAsset(getAssets(),"fonts/ > Roslien.ttf"); > messageBox.setTypeface(face); > > Thanking You, > > Regards, > Srikant Aggarwal > > On Feb 27, 4:43 pm, Takami Labs <[email protected]> wrote: > > > > > Thanks Bob and Frank for your kind reponses. > > > I have meanwhile sent a mail to the font provider , if he can provide > > me with the info regarding the font. > > 1. Whether the font use a Private Use Area > > 2. If it does than which code point points it assigns its characters > > to.. > > > As for an input method to type them.. for each English alphabet we > > have a corresponding alphabet in Roslien. I am using this property of > > the font successfully to type it through the default virtual > > keyboard, on to my Message Box(Edit Text). > > > Thanking You, > > > Regards, > > Srikant Aggarwal > > > On Feb 26, 11:26 pm, Bob Kerns <[email protected]> wrote: > > > > The Unicode Consortium has not addressed non-human languages. Not even > > > Klingon, whose script has been around for 30 years, even longer than > > > Unicode! > > > > But if you Google "unicode klingon", you can find how people have > > > addressed this for Klingon, e.g. using the Private Use area. > > > > I'd also look around for a tool to examine the content of a .TTF file, > > > and identify what code points it assigns its characters to. If it does > > > NOT use a Private Use area, I'd remap it so it did so. Otherwise, it > > > will conflict with other characters. On the other hand, you'll also > > > need an input method to type them! > > > > On Feb 25, 12:37 am, Takami Labs <[email protected]> wrote: > > > > > Hi, > > > > > I have an assignment to be completed. > > > > The assignment needs sms texting service facility in Roslien Font (for > > > > each English alphabet we have a corresponding alphabet in Roslien, > > > > something like Wingdings) for Android platform. > > > > On going through the posts available on different forums in internet, > > > > I observed that in order to send a different language text, I need to > > > > send the sms as a unicode string. > > > > The problem is, I have no clue on how to obtain the unicode string > > > > for a completely new font , Roslien. > > > > I have a " .ttf " file for the font which as such which contains the > > > > alphabets in the language. > > > > > Please help me , how do I obtain unicode string for the particular > > > > font. > > > > > Thanking You, > > > > > Regards, > > > > Srikant Aggarwal > > > > Android Developer -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
