On Feb 20, 2006, at 5:19 PM, bulia byak wrote:
On 2/20/06, Jon A. Cruz <jon@...18...> wrote:
For that entry problem, go ahead and file a bug report that Inkscape's input does not allow private use area characters to be entered. That, at least, can be fixed in Inkscape's code.
Maybe it can, but it's not the right way to do it. We use a library function to check whether a character is printable, so the right way is to raise this issue with the library maintainers.
No,
I actually checked into this. The library is doing the right thing.
In and of itself, any private use character could be printable or non- printable, and is not covered by the specs or such functions.
If our application can deal with the Private Use Area (which I've verified we do), all we need to do is check for it. g_unichar_validate () then g_unichar_type(..) == G_UNICODE_PRIVATE_USE will take care of things the right way.
Aside from other issues, this makes Inkscape's input behavior consistent with other systems, including the built-in OS X method. (Tricky to find, but easy to use once it's checked). Of course, this led me to wonder if we might want to warn upon insertion of a Private Use Area character.
I'm attaching a quick sample that shows the use of two private area characters (the second being the Apple glyph). This is happy-happy for me here in Inkscape and FireFox.
oops. Forgot the file
On Feb 20, 2006, at 5:58 PM, Jon A. Cruz wrote:
On Feb 20, 2006, at 5:19 PM, bulia byak wrote:
On 2/20/06, Jon A. Cruz <jon@...18...> wrote:
For that entry problem, go ahead and file a bug report that Inkscape's input does not allow private use area characters to be entered. That, at least, can be fixed in Inkscape's code.
Maybe it can, but it's not the right way to do it. We use a library function to check whether a character is printable, so the right way is to raise this issue with the library maintainers.
No,
I actually checked into this. The library is doing the right thing.
In and of itself, any private use character could be printable or non-printable, and is not covered by the specs or such functions.
If our application can deal with the Private Use Area (which I've verified we do), all we need to do is check for it. g_unichar_validate() then g_unichar_type(..) == G_UNICODE_PRIVATE_USE will take care of things the right way.
Aside from other issues, this makes Inkscape's input behavior consistent with other systems, including the built-in OS X method. (Tricky to find, but easy to use once it's checked). Of course, this led me to wonder if we might want to warn upon insertion of a Private Use Area character.
I'm attaching a quick sample that shows the use of two private area characters (the second being the Apple glyph). This is happy-happy for me here in Inkscape and FireFox.
participants (2)
-
Jon A. Cruz -
Jon A.Cruz