Thread: [Tuxpaint-i18n] Fwd: Tux Paint 'Text' tool Input Method support - can you help!?
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
From: Bill K. <nb...@so...> - 2007-05-07 15:05:09
|
I recently sent private email messages to some of Tux Paint's translators, asking for help with the new Input Method feature. Mark K. Kim, who developed the code behind the new feature sent a follow-up message that I felt was important to have documented somewhere. At the very least, archived on these lists seemed like a good idea. :^) (Thanks, Mark!) ----- Forwarded message from "Mark K. Kim" ----- Date: Sun, 6 May 2007 19:42:28 -0700 From: "Mark K. Kim" Subject: Re: Tux Paint 'Text' tool Input Method support - can you help!? This is how to implement the IM in Tux Paint for most languages: 1. Find the Unicode values for your Native Language: http://www.unicode.org/charts/ 2. Determine the English alphabet sequence(s) that will generate the unicodes in step #1. 3. Make a *.im file using the information from step #1 and #2. 4. Update im.c with the support for your language. Step #4 may not be your expertise, in which case one of the coders can help you. For most languages, I'm guessing there is a one-keystroke-to-one- unicode-character correlation. Hebrew, for example, is one such language. These should be pretty straight-forward to code. Some languages, however, require several keystrokes to be typed to output a single unicode chracter, such as Japanese and Korean. These require a bit more understanding of the language. Due to the complexity, such languages require someone who can program and know the language to program correctly. Those I can't help you with, unfortunately. On Sun, May 06, 2007 at 07:12:07AM -0700, Bill Kendrick wrote: > (PS to Mark - what kind of considerations should there be for this? > For example, how does one decide which is/are the best key(s) to use > for cycling through the modes, for a particular locale?) Whoever that is coding the IM for the Language in question should know the answer to that, but here are the details for completeness: Mode for switching between English and the Native Language (and any mode within the Native Language, if any) depends on the convention of the Native Language's keyboard layout. Here's even more details: Some language may not even have such concept as different modes. Many European keyboards, for example, are similar enough to the English keyboard that they simply do not have modes. If there is any key "missing" on their keyboard, they simply can't use it. (They could copy&paste or such to "type" them, however.) They have "extra" keys they need for their Native Language, however. But languages like Korean and Japanese can't simply have their Native Alphabets on their keyboards. They need some sort of English-esque keys for programming in C and typing commands onto the commandline. Unfortunately there aren't enough keys on a keyboard to accomodate all of the Native Alphabets as well as the English Alphabets. So they have a key to switch between the two languages. For both Korean and Japanese, their native keyboards have a dedicated key to switch between their Native Language and English. For a Korean-American like myself who wants to type Korean on the American keyboard lacking a dedicated Korean/English mode-switching key, we use the Right-Alt key as the Korean/English mode-switching key. So the Right-Alt key is used as the Korean/English mode-switching key on keyboards without a dedicated Korean/English mode-switching key. This is purely a convention set by the Korean community. Anyone who is implementing IM for Tux Paint for their Native Language should do the same and use whatever convention used by their Native Community for the mode-switching key. Hope that helps, -Mark ----- End forwarded message ----- -- -bill! bi...@ne... http://www.newbreedsoftware.com/ |
From: Ed M. <ed...@ro...> - 2007-05-12 17:37:12
|
Well, this sounds like an interesting project to me!? I'm willing to volunteer to try to implement perhaps Thai input as a first project, if someone hasn't done that already. (I'm not a Thai native speaker by any means, but I do have some Thai friends that I will recruit! :-)) --- Bill Kendrick <nb...@so...> wrote: > > I recently sent private email messages to some of > Tux Paint's translators, > asking for help with the new Input Method feature. > Mark K. Kim, who developed > the code behind the new feature sent a follow-up > message that I felt was > important to have documented somewhere. At the very > least, archived on these > lists seemed like a good idea. :^) > > (Thanks, Mark!) > > ----- Forwarded message from "Mark K. Kim" ----- > > Date: Sun, 6 May 2007 19:42:28 -0700 > From: "Mark K. Kim" > Subject: Re: Tux Paint 'Text' tool Input Method > support - can you help!? > > This is how to implement the IM in Tux Paint for > most languages: > > 1. Find the Unicode values for your Native > Language: > > http://www.unicode.org/charts/ > > 2. Determine the English alphabet sequence(s) that > will generate the > unicodes in step #1. > > 3. Make a *.im file using the information from > step #1 and #2. > > 4. Update im.c with the support for your language. > > Step #4 may not be your expertise, in which case one > of the coders can > help you. > > For most languages, I'm guessing there is a > one-keystroke-to-one- > unicode-character correlation. Hebrew, for example, > is one such > language. These should be pretty straight-forward > to code. > > Some languages, however, require several keystrokes > to be typed to > output a single unicode chracter, such as Japanese > and Korean. These > require a bit more understanding of the language. > Due to the > complexity, such languages require someone who can > program and know the > language to program correctly. Those I can't help > you with, > unfortunately. > > On Sun, May 06, 2007 at 07:12:07AM -0700, Bill > Kendrick wrote: > > (PS to Mark - what kind of considerations should > there be for this? > > For example, how does one decide which is/are the > best key(s) to use > > for cycling through the modes, for a particular > locale?) > > Whoever that is coding the IM for the Language in > question should know > the answer to that, but here are the details for > completeness: > > Mode for switching between English and the Native > Language (and any mode > within the Native Language, if any) depends on the > convention of the > Native Language's keyboard layout. Here's even more > details: > > Some language may not even have such concept as > different modes. Many > European keyboards, for example, are similar enough > to the English > keyboard that they simply do not have modes. If > there is any key > "missing" on their keyboard, they simply can't use > it. (They could > copy&paste or such to "type" them, however.) They > have "extra" keys > they need for their Native Language, however. > > But languages like Korean and Japanese can't simply > have their Native > Alphabets on their keyboards. They need some sort > of English-esque keys > for programming in C and typing commands onto the > commandline. > Unfortunately there aren't enough keys on a keyboard > to accomodate all > of the Native Alphabets as well as the English > Alphabets. So they have > a key to switch between the two languages. > > For both Korean and Japanese, their native keyboards > have a dedicated > key to switch between their Native Language and > English. For a > Korean-American like myself who wants to type Korean > on the American > keyboard lacking a dedicated Korean/English > mode-switching key, we use > the Right-Alt key as the Korean/English > mode-switching key. > > So the Right-Alt key is used as the Korean/English > mode-switching key on > keyboards without a dedicated Korean/English > mode-switching key. This > is purely a convention set by the Korean community. > Anyone who is > implementing IM for Tux Paint for their Native > Language should do the > same and use whatever convention used by their > Native Community for the > mode-switching key. > > Hope that helps, > > -Mark > > > ----- End forwarded message ----- > > -- > -bill! > bi...@ne... > http://www.newbreedsoftware.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 > express and take > control of your XML. No limits. Just data. Click to > get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Tuxpaint-i18n mailing list > Tux...@li... > https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Bill K. <nb...@so...> - 2007-05-13 02:02:33
|
On Sat, May 12, 2007 at 10:37:05AM -0700, Ed Montgomery wrote: > Well, this sounds like an interesting project to me!? > I'm willing to volunteer to try to implement perhaps > Thai input as a first project, if someone hasn't done > that already. (I'm not a Thai native speaker by any > means, but I do have some Thai friends that I will > recruit! :-)) Noone has stepped forward and offered Thai input method support yet, so go for it! Thanks :) -bill! |
From: Ed M. <ed...@ro...> - 2007-07-08 02:52:37
Attachments:
th.im
|
I've completed and attached a (tentative) th.im file for inputting Thai characters. I've yet to have a native Thai person take a look at it, and I have not started to modify the im.c file yet (I need a faster computer...I dread compiling ;-)). However, if there are any adventurous souls out there who would like to try it, please let me know how it goes. :-) ____________________________________________________________________________________ No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. http://mobile.yahoo.com/mail |
From: Bill K. <nb...@so...> - 2007-07-08 07:16:55
|
On Sat, Jul 07, 2007 at 07:52:28PM -0700, Ed Montgomery wrote: > > I've completed and attached a (tentative) th.im file > for inputting Thai characters. I've yet to have a > native Thai person take a look at it, and I have not > started to modify the im.c file yet (I need a faster > computer...I dread compiling ;-)). Well, the nice thing about im.c being its own C file is that you can do something like this: [edit src/im.c] make sudo make install-bin tuxpaint --lang thai and repeate as necessary. The first 'make' should only re-compile the im.c file (the only one that changed), and re-link. The second 'make' only hits the 'install-bin' target, so you don't end up re-copying all of Tux Paint's image files, sound files, fonts, etc. Just one file: the 'tuxpaint executable. > However, if there are any adventurous souls out there who would like to > try it, please let me know how it goes. :-) I'll throw what you've sent into CVS for 0.9.18. Thanks :) -- -bill! bi...@ne... http://www.newbreedsoftware.com/ |
From: Bill K. <nb...@so...> - 2007-07-08 07:28:05
|
On Sat, Jul 07, 2007 at 07:52:28PM -0700, Ed Montgomery wrote: > > I've completed and attached a (tentative) th.im file > for inputting Thai characters. I've yet to have a > native Thai person take a look at it, and I have not > started to modify the im.c file yet (I need a faster > computer...I dread compiling ;-)). However, if there > are any adventurous souls out there who would like to > try it, please let me know how it goes. :-) I've updated Makefile-i18n and src/im.c. I merely based the Thai IM handling on the Japanese code. It may be totally wrong. :( If you (or someone who knows Thai) can grab Tux Paint out of CVS, they can test it. Thanks! :) http://www.tuxpaint.org/download/source/cvs/ -- -bill! bi...@ne... http://www.newbreedsoftware.com/ |
From: Mark K. K. <mkk...@gm...> - 2007-07-09 02:40:03
|
On Sun, Jul 08, 2007 at 12:16:52AM -0700, Bill Kendrick wrote: > On Sat, Jul 07, 2007 at 07:52:28PM -0700, Ed Montgomery wrote: > > > > I've completed and attached a (tentative) th.im file > > for inputting Thai characters. I've yet to have a > > native Thai person take a look at it, and I have not > > started to modify the im.c file yet (I need a faster > > computer...I dread compiling ;-)). > > Well, the nice thing about im.c being its own C file is that you can do > something like this: > > [edit src/im.c] > make > sudo make install-bin > tuxpaint --lang thai Also need to edit Makefile-i18n to take th.im into consideration under the uninstall-i18n and install-im targets, and run `sudo make install-im` right after `sudo make install-bin`. -Mark |
From: Mark K. K. <mkk...@gm...> - 2007-07-09 02:43:15
|
On Sun, Jul 08, 2007 at 12:28:06AM -0700, Bill Kendrick wrote: > On Sat, Jul 07, 2007 at 07:52:28PM -0700, Ed Montgomery wrote: > > > > I've completed and attached a (tentative) th.im file > > for inputting Thai characters. I've yet to have a > > native Thai person take a look at it, and I have not > > started to modify the im.c file yet (I need a faster > > computer...I dread compiling ;-)). However, if there > > are any adventurous souls out there who would like to > > try it, please let me know how it goes. :-) > > I've updated Makefile-i18n and src/im.c. I merely based the Thai IM handling > on the Japanese code. It may be totally wrong. :( Japanese code is the good code to start with even if it ends up needing tweaks later. =) -Mark |
From: Bill K. <nb...@so...> - 2007-07-09 06:37:41
|
On Sun, Jul 08, 2007 at 07:43:17PM -0700, Mark K. Kim wrote: > Japanese code is the good code to start with even if it ends up needing > tweaks later. =) Glad to hear it. It certainly did _something_, but not knowing Thai or how one expects to input Thai onto a keyboard, for all I know it could be gibberish, or curses against your grandparents. :^/ -- -bill! bi...@ne... http://www.newbreedsoftware.com/ |
From: Ed M. <ed...@ro...> - 2007-07-09 22:50:55
|
Ok, I decided I might as well join the party, especially since I am an instigator...:-) Trials-and-tribulations-to-date: (Or confessions of a Tuxpaint addict): 1. Downloaded 0.9.17 source code tarball. Unzipped, Untarred. No problem. 2. Attempted make. After several attempts, gleaned from several pages of errors/warnings that several dev libraries were missing. Downloaded and installed said libraries. 3. Make. No problem. Make install. No problem. No errors or warnings. A shiny, new tuxpaint executable appears! Hurray! Glory be! Celebrations and drinks all around! :-) 4. $./tuxpaint --lang=japanese Program loads and executes flawlessly. Menus are in Japanese, but I could not find any way to input Japanese characters. What am I missing? Once I figure this out, then I can go on to testing the Thai input. ____________________________________________________________________________________Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/ |
From: Bill K. <nb...@so...> - 2007-07-09 23:33:26
|
On Mon, Jul 09, 2007 at 03:50:51PM -0700, Ed Montgomery wrote: > 1. Downloaded 0.9.17 source code tarball. Unzipped, > Untarred. No problem. You'll want to download the Tux Paint 'going to be 0.9.18 or maybe even 1.0' source code from SourceForge CVS. The CVS page on the TP website explains it in detail: http://www.tuxpaint.org/download/source/cvs/ > 2. Attempted make. After several attempts, gleaned > from several pages of errors/warnings that several dev > libraries were missing. Downloaded and installed said > libraries. Yeah, I throw the warnings up, but the compiler seems to chug ahead despite my "#error"s. Glad you noticed them. :) <snip> > 4. $./tuxpaint --lang=japanese > Program loads and executes flawlessly. Menus are in > Japanese, but I could not find any way to input > Japanese characters. What am I missing? Once I > figure this out, then I can go on to testing the Thai > input. Click Text tool. Click on the canvas (to get a blinking insertion cursor) Press the right [Alt] key. Type some text. Note that not all fonts include Japanese characters. While the broken text is up and the cursor is still blinking (don't press [Enter] or [Tab] -- the text'll look like squares, usually) click the fonts at the right until you find one with Japanese glyphs. And again, Tux Paint in CVS already has Thai support. You'll just need to screw around with the code in "src/im.c" to get it working, assuming it's not already. :) Thanks and good luck! :) -- -bill! bi...@ne... http://www.newbreedsoftware.com/ |
From: Ed M. <ed...@ro...> - 2007-07-10 13:20:06
|
> You'll want to download the Tux Paint 'going to be > 0.9.18 or maybe even 1.0' > source code from SourceForge CVS. The CVS page on > the TP website explains > it in detail: > > http://www.tuxpaint.org/download/source/cvs/ > > Ok, will look into that tomorrow. > Yeah, I throw the warnings up, but the compiler > seems to chug ahead > despite my "#error"s. Glad you noticed them. :) > Compilers...linkers...gotta luv 'em :-) (I wonder what would have happened if the 'verbose' switch was one...or is it by default? :-)) > > <snip> > > 4. $./tuxpaint --lang=japanese > > Program loads and executes flawlessly. Menus are > in > > Japanese, but I could not find any way to input > > Japanese characters. What am I missing? Once I > > figure this out, then I can go on to testing the > Thai > > input. > > Click Text tool. > Click on the canvas (to get a blinking insertion > cursor) > Press the right [Alt] key. > Type some text. > > Note that not all fonts include Japanese characters. > While the broken text is up and the cursor is still > blinking > (don't press [Enter] or [Tab] -- the text'll look > like squares, usually) > click the fonts at the right until you find one with > Japanese glyphs. > I tried every font and no squares, no luck, and pressed right hand alt key a couple of times with each. Now, this may have something to do with what I am using. I'm in Kyoto, Japan at the moment (for the summer studying Japanese in between bouts of compiling tuxpaint, etc. ;-)), so I'm using my Acer portable, which has a key labelled 'Alt Gr'. Don't know what the 'Gr' refers to. So, if perhaps Mr. Kim could suggest which font he is using for testing, that would save me some time guessing (or, come to think of it, what is the default font that is being used to display the hiragana on the menus/icons?) Any assistance/prognostications/incantations/guesses/wild guesses/outlandish, twisted, secret keycodes/fonts, etc. greatly appreciated! :-) ____________________________________________________________________________________ Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. http://new.toolbar.yahoo.com/toolbar/features/mail/index.php |
From: Ed M. <ed...@ro...> - 2007-07-10 23:25:27
|
Hmmm...did get hiragana and katakana working on TP, but Korean just showed boxes everywhere, including menus, etc. However, Thai menus worked, but I assume I'll need the latest source from CVS to attempt Thai input. I would imagine installing the Korean font will correct the boxes problem for Korean. So, all in all, just ignore me while I fiddle...:-) ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC |
From: Ed M. <ed...@ro...> - 2007-07-11 13:50:07
Attachments:
thaiinput.png
|
Good news! :-) (Although some tweaking is still required.) Have attached a screenshot of Thai input working! :-) Taken using Garuda(Bold) font, and also works with FreeSerif(Medium) font, under Kubuntu, etc. However, (there's always a 'however' isn't there? :-)) Take a look at the following copied from my terminal for compiling/testing/etc. Compiling and linking did not seem to give any error, but on execution of the binary, it could not find the th.im file in the /usr/local/share/tuxpaint/im directory. Once I copied the file from the src directory where it compiled to the local/share directory, then it loaded, executed and operated as expected. me@me-one:~/Desktop/tuxpaintstuff/tuxpaint-0.9.17$ tuxpaint --lang=thai path: No such file or directory Unable to load /usr/local/share/tuxpaint/im/th.im, defaulting to im_event_c open /dev/sequencer: No such file or directory me@me-one:~/Desktop/tuxpaintstuff/tuxpaint-0.9.17$ ls /usr/local/share/tuxpaint/im ja.im ko.im me@me-one:~/Desktop/tuxpaintstuff/tuxpaint-0.9.17$ cd im me@me-one:~/Desktop/tuxpaintstuff/tuxpaint-0.9.17/im$ ls ja.im ko.im th.im me@me-one:~/Desktop/tuxpaintstuff/tuxpaint-0.9.17/im$ cp th.im /usr/local/share/tuxpaint/im cp: cannot create regular file `/usr/local/share/tuxpaint/im/th.im': Permission denied me@me-one:~/Desktop/tuxpaintstuff/tuxpaint-0.9.17/im$ sudo xterm exme@me-one:~/Desktop/tuxpaintstuff/tuxpaint-0.9.17/im$ me@me-one:~/Desktop/tuxpaintstuff/tuxpaint-0.9.17/im$ tuxpaint --lang=thai open /dev/sequencer: No such file or directory ____________________________________________________________________________________ Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. http://videogames.yahoo.com/platform?platform=120121 |
From: Bill K. <nb...@so...> - 2007-07-12 20:00:46
|
On Wed, Jul 11, 2007 at 06:50:02AM -0700, Ed Montgomery wrote: > Good news! :-) (Although some tweaking is still > required.) > > Have attached a screenshot of Thai input working! :-) > Taken using Garuda(Bold) font, and also works with > FreeSerif(Medium) font, under Kubuntu, etc. Glad to hear! > Take a look at the following copied from my terminal > for compiling/testing/etc. Compiling and linking did > not seem to give any error, but on execution of the > binary, it could not find the th.im file in the > /usr/local/share/tuxpaint/im directory. Once I copied > the file from the src directory where it compiled to > the local/share directory, then it loaded, executed > and operated as expected. Did you do a "sudo make install"? It should have installed th.im for you (the 'install' target depends on the 'install-im' target, which does the actual copying of those files). PS - As you probably saw, I'm converting Tux Paint to use SDL_Pango instead of SDL_TTF. The former is an SDL wrapper around the Pango rendering library (discussed on Wikipedia here: http://en.wikipedia.org/wiki/Pango and lives here: http://www.pango.org/ ). The former is a simple wrapper around FreeType2 (and lives here: http://www.libsdl.org/projects/SDL_ttf/ ), and doesn't do the more complex internationalization stuff. (Hence broken Arabic translations, for example.) I'm curious to see how Thai stands up to the new SDL_Pango stuff. I'm guessing if it rendered ok before, it should continue to render ok with Pango. -- -bill! bi...@ne... http://www.newbreedsoftware.com/ |
From: Ed M. <ed...@ro...> - 2007-07-14 14:12:07
|
Hmmm...already had libpango-1.0, etc. installed, but I assume they were not being used. Googled SDL_Pango, and found this, for example: http://sdlpango.sourceforge.net/ So, could you give us a head's up when you have switched the code? :-) > > PS - As you probably saw, I'm converting Tux Paint > to use SDL_Pango > instead of SDL_TTF. > > The former is an SDL wrapper around the Pango > rendering library > (discussed on Wikipedia here: > http://en.wikipedia.org/wiki/Pango and > lives here: http://www.pango.org/ ). The former is > a simple wrapper > around FreeType2 (and lives here: > http://www.libsdl.org/projects/SDL_ttf/ ), > and doesn't do the more complex internationalization > stuff. (Hence broken > Arabic translations, for example.) > > I'm curious to see how Thai stands up to the new > SDL_Pango stuff. > I'm guessing if it rendered ok before, it should > continue to render ok > with Pango. > > -- > -bill! > bi...@ne... > http://www.newbreedsoftware.com/ > ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html |
From: Bill K. <nb...@so...> - 2007-07-14 18:01:21
|
On Sat, Jul 14, 2007 at 06:29:08AM -0700, Ed Montgomery wrote: > Hmmm...already had libpango-1.0, etc. installed, but I > assume they were not being used. Googled SDL_Pango, > and found this, for example: > http://sdlpango.sourceforge.net/ > > So, could you give us a head's up when you have > switched the code? :-) The code in CVS has been switched, though it doesn't work completely. It now requires SDL_Pango, and any dependencies it depends on (e.g,, pango, which in turn depends on cairo and other stuff). If you're using Ubuntu Fiesty, like I am, it's merely a matter of: $ sudo aptitude install libsdl-pango-dev and you should be able to compile Tux Paint from CVS that uses the new code. $ cd WHERVER_TUXPAINT_IS $ make clean $ cvs update -dPC $ make $ sudo make install -bill! bi...@ne... http://www.newbreedsoftware.com/ |
From: Bill K. <nb...@so...> - 2007-07-12 20:03:27
|
On Wed, Jul 11, 2007 at 06:50:02AM -0700, Ed Montgomery wrote: > Good news! :-) (Although some tweaking is still > required.) And cool, btw :) -bill! bi...@ne... http://www.newbreedsoftware.com/ |
From: Ed M. <ed...@ro...> - 2007-07-14 14:27:43
|
Downloaded, compiled and installed SDL_Pango. Started new directory with new copy of source. Recompiled, etc. Japanese works, apparently, but Thai does not. Will not switch from English to Thai, Right Alt key has no effect. And I also see the following error in both situations (both working and non-working Thai versions): one:~/tuxpaintexperiments/tuxpaint-0.9.17$ ./tuxpaint --lang thai open /dev/sequencer: No such file or directory ____________________________________________________________________________________ Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/ |
From: Bill K. <nb...@so...> - 2007-07-09 06:36:56
|
On Sun, Jul 08, 2007 at 07:40:05PM -0700, Mark K. Kim wrote: > Also need to edit Makefile-i18n to take th.im into consideration under > the uninstall-i18n and install-im targets, and run `sudo make > install-im` right after `sudo make install-bin`. > I already edited the Makefile-i18n. I think "make install-im" would only need to be done if the "th.im" file actually got edited. I was going under the assumption that the process would be: 1. Download latest Tux Paint from CVS 2. make [everything] 3. make install [everything] 4. test Thai Input Method 5. tweak src/im.c's Thai-related code 6. make [only im.c gets compiled, since only it got edited] 7. make install-bin [since only im.c was edited, and hence only tuxpaint executable changed] 8. goto step 4 -- -bill! bi...@ne... http://www.newbreedsoftware.com/ |
From: Mark K. K. <mkk...@gm...> - 2007-07-09 09:59:22
|
On Sun, Jul 08, 2007 at 11:36:55PM -0700, Bill Kendrick wrote: > I was going under the assumption that the process would be: > > 1. Download latest Tux Paint from CVS > 2. make [everything] > 3. make install [everything] > 4. test Thai Input Method > 5. tweak src/im.c's Thai-related code > 6. make [only im.c gets compiled, since only it got edited] > 7. make install-bin [since only im.c was edited, and hence only > tuxpaint executable changed] > 8. goto step 4 Oh, I see. I concur. -Mark |