Ben Combee wrote: > >> I have got to figure out why the Japanese is crashing....my >> workaround..... >> the .r file contains text escaped....e.g. "\001\002\003", etc. >> If I take the english .r file and replace all the english "English" with >> the japanese "Japense" then >> the compile is fine. However, I cannot maintain this this way! There are >> too many label and field position changes >> that must be made because of the japense text is different length than >> the english. And, every time I make a rcp change, >> I must go through this long arduous task of replacing all English text >> with Japanese text in the .r file. > > > The PalmRez post-linker is entirely controlled by PalmSource, not > Metrowerks. I wish I could help you determine the crash, but we don't > have the source for this postlinker and don't have a way to debug > crashes in it. > > At this point, I'd start by taking the output .r file that crashes > PalmRez after being compiled by Rez and commenting out resources in > it. Try to find if one particular form or other resource is the > problem form. Perhaps its a PilRC problem, but its more likely a > transliteration issue. > > If its just a character set issue, then you might be able to alter the > source of the PilRC plugin for codewarrior to output characters in a > better format. I don't know if that code's been tested for anything > other than English text -- I know I've not used it for anything but > Latin languages.
I've used the PilRC output ( .r ) files for Korean, Chinese, English, Japanese...the ONLY one I have a problem with is the Japanese one. And, this is because for ALL other languages I use the "English" linker (with the invalid character warning...i.e. all warnings...turned OFF). The Japanese one...trying to use the Japanse linker because of a "Menu Option Too Wide" error I get without the Japanese Linker. This is because the Japanse is Double byte...I think I will eventually run into the problem with Korean and Chinese, but their translation haven't had a Menu Too Wide error yet. So, I'll continue with the English linker. I REALLY REALLY wish the menu too wide wasn't an error...just make that thing a warning and let us ignore it if we wish. BTW...all "double byte awareness" options are turned on in the compiler options. Do you think anyone from PalmSource reads or monitors this newsgroup...is would hope so! I suspected all along that this was a PalmSource problem. I HAVE commented out ALL resources when I link and they ALL cause the crash problem. To eliminate the crash, I take the escaped text "\123\456x[\012" and put in the SJIS text. I hade to have to get into the plugin source or the PilRC source. I nare have the time to do that! Nor do I know where to start looking. So...this should be something PalmSource fixes....Why do you suppose they have a "Palm OS for Japan" linker....(e.g. Japanese Support). I bet it's to manage double byte and fix the "Menu Option Too Wide problems...)...but, if the thing is going to crash because it can't handle escaped bytecode, then, this is a big oversight by PalmSource and they need to fix. Oh...how about just putting in an option to "turn off menu too wide error and stop checking for "invalid" characters...and let us programmers do our job!" Then I'll use the "English" linker! -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
