Thread: [Tuxpaint-devel] Input Methods not working!?
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
From: Bill K. <nb...@so...> - 2009-05-29 06:37:03
|
I'm trying to use the Input Methods with the Text tool in Tux Paint, and it only seems to be doing anything (i.e., switching methods and recognizing sequences) in the Traditional Chinese locale. (And for ZH_TW, it seems none of the fonts that SDL_Pango is providing to me include Chinese characters, but I'm going to check if any of the ttf-* packages that libpango1.0-common suggests in Ubuntu will help this issue.) Any ideas on why the IM stuff seems to just not work for the other locales!? I'd consider this a showstopper. :( Thanks! -- -bill! Sent from my computer |
From: Song H. <son...@gm...> - 2009-05-29 14:04:50
|
Hi Bill, ZH_TW should be work, You can try to typing "5j/1" it's "中",and typing "jp61" is "文". Only two fonts can display chinese, must select right fonts. like below image. Sincerely, song. 2009/5/29 Bill Kendrick <nb...@so...> > > I'm trying to use the Input Methods with the Text tool in Tux Paint, > and it only seems to be doing anything (i.e., switching methods and > recognizing sequences) in the Traditional Chinese locale. > > (And for ZH_TW, it seems none of the fonts that SDL_Pango is providing to > me include Chinese characters, but I'm going to check if any of the ttf-* > packages that libpango1.0-common suggests in Ubuntu will help this issue.) > > Any ideas on why the IM stuff seems to just not work for the other > locales!? > I'd consider this a showstopper. :( > > Thanks! > > -- > -bill! > Sent from my computer > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Tuxpaint-devel mailing list > Tux...@li... > https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel > |
From: Bill K. <nb...@so...> - 2009-05-29 18:41:57
|
On Fri, May 29, 2009 at 09:37:29PM +0800, Song Huang wrote: > Hi Bill, > > ZH_TW should be work, You can try to typing "5j/1" it's "CURCUR"!Aand > typing "jp61" is "CURaa". Er yeah, I guess I hadn't tried ALL the fonts. Sorry, it was late at night ;) > Only two fonts can display chinese, must select right fonts. like below > image. That brings up a question -- should we try to be 'smart' about which fonts are available when you switch to certain Input Methods? (And if the font you have selected is incompatible, switch to one of the compatible ones. Oh, and if NONE of the fonts are compatible, for some reason, don't let the user switch to that Input Method...?) -bill! |
From: Mark K. K. <mkk...@gm...> - 2009-05-29 22:55:35
|
On Fri, May 29, 2009 at 11:41:51AM -0700, Bill Kendrick wrote: > That brings up a question -- should we try to be 'smart' about which > fonts are available when you switch to certain Input Methods? What I did with Korean is to translate the text on the font buttons to include a Korean character. So instead of showing "Aa", it shows "A<KoreanCharacter>" so it's relatively obviously which fonts are Korean-capable. It takes a minimal effort, but it could be friendlier. -Mark |
From: Song H. <son...@gm...> - 2009-05-30 01:19:26
|
Hi Mark, It's a really good idea, I made a replica of your way. ^_^ Sincerely, song. 2009/5/30 Mark K. Kim <mkk...@gm...> > On Fri, May 29, 2009 at 11:41:51AM -0700, Bill Kendrick wrote: > > > That brings up a question -- should we try to be 'smart' about which > > fonts are available when you switch to certain Input Methods? > > What I did with Korean is to translate the text on the font buttons to > include a Korean character. So instead of showing "Aa", it shows > "A<KoreanCharacter>" so it's relatively obviously which fonts are > Korean-capable. > > It takes a minimal effort, but it could be friendlier. > > -Mark > > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Tuxpaint-devel mailing list > Tux...@li... > https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel > |
From: Bill K. <nb...@so...> - 2009-05-29 23:38:05
|
On Fri, May 29, 2009 at 03:27:09PM -0700, Mark K. Kim wrote: > On Fri, May 29, 2009 at 11:41:51AM -0700, Bill Kendrick wrote: > > > That brings up a question -- should we try to be 'smart' about which > > fonts are available when you switch to certain Input Methods? > > What I did with Korean is to translate the text on the font buttons to > include a Korean character. So instead of showing "Aa", it shows > "A<KoreanCharacter>" so it's relatively obviously which fonts are > Korean-capable. > > It takes a minimal effort, but it could be friendlier. Ah, this affects fonts when they're loaded initially, right? So it's just a matter of localizers tweaking their POs. No... does Korean IM work for you, in CVS? If not, any ideas what broke? If it does, any ideas why it's not working _for me_? :) Thx! Have a nice weekend! -bill! |
From: Mark K. K. <mkk...@gm...> - 2009-05-31 14:55:04
|
On Fri, May 29, 2009 at 04:37:59PM -0700, Bill Kendrick wrote: > does Korean IM work for you, in CVS? Korean IM works fine, built fresh from this morning's CVS. > If it does, any ideas why it's not working _for me_? :) Beats me. What are the symptoms and how are you building it? -Mark |
From: Bill K. <nb...@so...> - 2009-06-01 02:40:36
|
On Sun, May 31, 2009 at 06:41:32AM -0700, Mark K. Kim wrote: > > Beats me. What are the symptoms and how are you building it? I just started adding some code to filter out locale-specific fonts when you're not in that locale (to avoid the Tibetan font from appearing and confusing people, though I did just get a report that it's "the coolest looking thing ever" :) ) I realize now that Tux Paint was being too liberal in allowing locales to be used when not installed. That is, I can ask Tux Paint to run in Japanese, and the UI is in Japanese, but get_current_language() was always returning the internal (enum value) representing "en". :^/ So I just edited my /var/lib/locales/supported.d/local to include all of the locales codes we have listed in src/i18n.c. (A bunch aren't recognized by Ubuntu, such as "twi_GH" or "zam", though.) I had just happened to have zh_TW in there already. *Siiigh* Sorry :( -bill! |
From: Song H. <son...@gm...> - 2009-06-01 03:26:39
|
Hi, Zh_TW for a problem I have is that many homophone of zh_TW, And now I only appended serial number in zh_tw.im for homophone. I want to display all homophone to pick one, How I should make it ? Sincerely, song. 2009/6/1 Bill Kendrick <nb...@so...> > On Sun, May 31, 2009 at 06:41:32AM -0700, Mark K. Kim wrote: > > > > Beats me. What are the symptoms and how are you building it? > > I just started adding some code to filter out locale-specific fonts > when you're not in that locale (to avoid the Tibetan font from appearing > and confusing people, though I did just get a report that it's > "the coolest looking thing ever" :) ) > > I realize now that Tux Paint was being too liberal in allowing locales > to be used when not installed. That is, I can ask Tux Paint to run in > Japanese, and the UI is in Japanese, but get_current_language() was > always returning the internal (enum value) representing "en". :^/ > > So I just edited my /var/lib/locales/supported.d/local to include > all of the locales codes we have listed in src/i18n.c. > (A bunch aren't recognized by Ubuntu, such as "twi_GH" or "zam", though.) > > I had just happened to have zh_TW in there already. *Siiigh* Sorry :( > > -bill! > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Tuxpaint-devel mailing list > Tux...@li... > https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel > |
From: Mark K. K. <mkk...@gm...> - 2009-06-01 21:27:34
|
On Mon, Jun 01, 2009 at 11:26:37AM +0800, Song Huang wrote: > Zh_TW for a problem I have is that many homophone of zh_TW, > And now I only appended serial number in [1]zh_tw.im for homophone. > > I want to display all homophone to pick one, How I should make it ? You can display the options in the text area next to Tux. The mechanism is already available in the existing im.c. For example: im->tip_text = "(1) A, (2) B, (3) C ..."; The difficult part will be building the text. You'll need add the code to scan the state machine (CHARMAP cm) to see what the available codes are, and build a text from it dynamically. -Mark |
From: Bill K. <nb...@so...> - 2009-06-10 19:45:41
|
On Mon, Jun 01, 2009 at 02:27:28PM -0700, Mark K. Kim wrote: > > I want to display all homophone to pick one, How I should make it ? > > You can display the options in the text area next to Tux. The mechanism > is already available in the existing im.c. For example: > > im->tip_text = "(1) A, (2) B, (3) C ..."; > > The difficult part will be building the text. You'll need add the code > to scan the state machine (CHARMAP cm) to see what the available codes > are, and build a text from it dynamically. I'm finally looking back at this, and understanding the question, and Mark's answer. :) This isn't a bad idea. So typing "to" would cause the Tux tips to say: "(1) to (2) too (3) two". Typing "to1" would cause "to" to appear in the Text tool. Typing "to3" would caue "two", etc. (Using lame english examples here :) ) -bill! |
From: Mark K. K. <mkk...@gm...> - 2009-06-12 01:12:39
|
On Wed, Jun 10, 2009 at 12:45:38PM -0700, Bill Kendrick wrote: > I'm finally looking back at this, and understanding the question, and > Mark's answer. :) I actually thought about this exact difficulty with implementing Chinese input method when I initially implemented the IM so it wasn't hard to answer it... =) > This isn't a bad idea. So typing "to" would cause the Tux tips > to say: "(1) to (2) too (3) two". Typing "to1" would cause "to" > to appear in the Text tool. Typing "to3" would caue "two", etc. Yep. Or entering "free" would cause Tux tips to say: (1) Free as in beer (2) Free as in speech =) -Mark |