my life at the moment
-
Damn! Your graphics cards seems to be broken... or is it something I just drank??? Konichiwa! :) And if the paths that I have followed/have tread against the flow/there is no need for sorrow I am coming home Return, Crüxshadows
Stefan Pedersen wrote: Your graphics cards seems to be broken Nah, my computer stayed up late last night drinking too much silicon. :) Jeremy Falcon
-
Please tell me your job isn't to WRITE that! Regards, Jeff Varszegi
Nope, just debugging it. Jeremy Falcon
-
You really know how to hurt a guy. My life at the moment is occupied with getting my language translation tool working such that it satisfies the Japanese engineers where I work. This tool is used by translators to edit the .RC files for each language that our application will support. Over the last few days, I figured out the following items:
- My application (the one being translated) is compiled for UNICODE, which is supposed to make supporting Far Eastern languages simpler.
- The resource script is compiled into UNICODE text in the .EXE/.DLL.
- My translator program is also compiled for UNICODE, thereby making translation text handling easier. So far, so good.
- .RC files must be encoded as MBCS (multibyte character set, not UNICODE)
Screeeeeechh! Bang, bang, CRUNCH! (sound of wheel cover rolling off into distance) What brain-dead son of a chihuaha and a rhesus monkey thought that one up! I have to read the text from the .RC file as MBCS, translate the relevant bits to UNICODE, let the user edit them, and then translate them from UNICODE back to MBCS just so the stupid resource compiler can turn the text back into UNICODE. By the way, did I mention that if you set the code page for the .RC file to 1200 (UNICODE), the farking IDE (.NET 2003) will no longer load the file? Grrr.
Software Zen:
delete this; -
You really know how to hurt a guy. My life at the moment is occupied with getting my language translation tool working such that it satisfies the Japanese engineers where I work. This tool is used by translators to edit the .RC files for each language that our application will support. Over the last few days, I figured out the following items:
- My application (the one being translated) is compiled for UNICODE, which is supposed to make supporting Far Eastern languages simpler.
- The resource script is compiled into UNICODE text in the .EXE/.DLL.
- My translator program is also compiled for UNICODE, thereby making translation text handling easier. So far, so good.
- .RC files must be encoded as MBCS (multibyte character set, not UNICODE)
Screeeeeechh! Bang, bang, CRUNCH! (sound of wheel cover rolling off into distance) What brain-dead son of a chihuaha and a rhesus monkey thought that one up! I have to read the text from the .RC file as MBCS, translate the relevant bits to UNICODE, let the user edit them, and then translate them from UNICODE back to MBCS just so the stupid resource compiler can turn the text back into UNICODE. By the way, did I mention that if you set the code page for the .RC file to 1200 (UNICODE), the farking IDE (.NET 2003) will no longer load the file? Grrr.
Software Zen:
delete this;Gary R. Wheeler wrote: .RC files must be encoded as MBCS (multibyte character set, not UNICODE) :wtf: That's news to me. (Un)fortunately, this app is in VB, and as my luck would have it - most VB programs don't take advantage of resource scripts. We're pulling the translations from a SQL database (the app is used over a citrix server). Gary R. Wheeler wrote: By the way, did I mention that if you set the code page for the .RC file to 1200 (UNICODE), the farking IDE (.NET 2003) will no longer load the file? LOL! That's about all I can say. So far, we've been doing all the Japanese development on a Japanese version of Windows XP with minimal problems. Of course, we're also using VB6 too. (insert sigh here) Jeremy Falcon
-
now i see why software jobs are outsourced to India rather than China.:laugh:
God is Real, unless declared Integer.
-
This was called a joke. It was meant to be funny. :| Jeremy Falcon
I think the DBMS is powerful as it supports multilingual field name in the SQL script. I think some DBMS only support English. Sonork 100.41263:Anthony_Yio Life is about experiencing ...
-
now i see why software jobs are outsourced to India rather than China.:laugh:
God is Real, unless declared Integer.
Those are Kanji(Japanese) words by the way. Sonork 100.41263:Anthony_Yio Life is about experiencing ...
-
Those are Kanji(Japanese) words by the way. Sonork 100.41263:Anthony_Yio Life is about experiencing ...
dont matter, all look the same to me. :-)
God is Real, unless declared Integer.
-
This was called a joke. It was meant to be funny. :| Jeremy Falcon
Just goes to show. Humour is sometimes wasted on the geek. hehe :~
-
This was called a joke. It was meant to be funny. :| Jeremy Falcon
It is scary... funny but scary. Give me a pivot cube set with multiple unions and joins over your one anyday, you poor bugger. regards, Paul Watson Bluegrass South Africa Christopher Duncan quoted: "...that would require my explaining Einstein's Fear of Relatives" Crikey! ain't life grand? Einstein says...
-
I sent that image around to the dev team as well as a new guy in London, I have honestly just had the following conversation on IM with him :-D (another co-worker is called Jeremy so when he saw the ~jeremy in the screenshot he thought he meant my co-worker, not you) Co-worker: whats that all about? Paul: I sent that to you Co-worker: ja and? Paul: Jeremy is learning Chinese. Microsoft is pushing for Chinese to be the preferred development language. Co-worker: what! Co-worker: really? Paul: Ask him. Co-worker: What the fuck are we going to do? None of us can speak Chinese, does this affect .NET? Paul: Konichiwa. I can speak some. Paul: Move with the times eh Co-worker: lol. Do we have to buy new software? Paul: No, Notepad supports it fine Co-worker: We use Notepad to dev!?!? Paul: :) relax... Paul: A friend sent me that SQL statement, he is working with a Chinese team and he had to debug that SQL statement. I just thought it was funny Co-worker: what a mission Paul: Indeed, but he gets free sake all day Co-worker: lol Thanks for the morning laugh Jeremy. regards, Paul Watson Bluegrass South Africa Christopher Duncan quoted: "...that would require my explaining Einstein's Fear of Relatives" Crikey! ain't life grand? Einstein says...
-
I sent that image around to the dev team as well as a new guy in London, I have honestly just had the following conversation on IM with him :-D (another co-worker is called Jeremy so when he saw the ~jeremy in the screenshot he thought he meant my co-worker, not you) Co-worker: whats that all about? Paul: I sent that to you Co-worker: ja and? Paul: Jeremy is learning Chinese. Microsoft is pushing for Chinese to be the preferred development language. Co-worker: what! Co-worker: really? Paul: Ask him. Co-worker: What the fuck are we going to do? None of us can speak Chinese, does this affect .NET? Paul: Konichiwa. I can speak some. Paul: Move with the times eh Co-worker: lol. Do we have to buy new software? Paul: No, Notepad supports it fine Co-worker: We use Notepad to dev!?!? Paul: :) relax... Paul: A friend sent me that SQL statement, he is working with a Chinese team and he had to debug that SQL statement. I just thought it was funny Co-worker: what a mission Paul: Indeed, but he gets free sake all day Co-worker: lol Thanks for the morning laugh Jeremy. regards, Paul Watson Bluegrass South Africa Christopher Duncan quoted: "...that would require my explaining Einstein's Fear of Relatives" Crikey! ain't life grand? Einstein says...
Paul Watson wrote: Thanks for the morning laugh Jeremy. Ditto, it's Wed. morning over here and I just read your post and laughed. :) Jeremy Falcon
-
Gary R. Wheeler wrote: .RC files must be encoded as MBCS (multibyte character set, not UNICODE) :wtf: That's news to me. (Un)fortunately, this app is in VB, and as my luck would have it - most VB programs don't take advantage of resource scripts. We're pulling the translations from a SQL database (the app is used over a citrix server). Gary R. Wheeler wrote: By the way, did I mention that if you set the code page for the .RC file to 1200 (UNICODE), the farking IDE (.NET 2003) will no longer load the file? LOL! That's about all I can say. So far, we've been doing all the Japanese development on a Japanese version of Windows XP with minimal problems. Of course, we're also using VB6 too. (insert sigh here) Jeremy Falcon
Jeremy Falcon wrote: That's news to me. As you know, resource scripts are essentially source files. The bulk of the file is syntactic elements that describe bits and pieces of the user interface. The language-specific text actually occupies a relatively small portion of the file. I think you could justify converting the whole mess to UNICODE, however. The syntactic elements (
DIALOG,BEGIN/END,STRINGTABLE, etc.) aren't any more difficult to parse and identify as UNICODE than they are in an ANSI character set. The screen text, however, is required to be unambiguous. The current methodology involves multiple translations between an MBCS code page and UNICODE. Each translation has the potential for data loss. For example, if a UNICODE character doesn't have a corresponding MBCS representation, you're stuck. Unless you are supporting Windows 95, UNICODE is a better way to go. It's supported natively in Windows NT/2000/XP, and with an add-on for Windows 98. Jeremy Falcon wrote: we've been doing all the Japanese development on a Japanese version of Windows XP with minimal problems Thus far I've been able to get away with using the Japanese add-on from the XP multilingual pack. It adds Japanese fonts and resources to English Windows. For a while I was switching back and forth from the Japanese UI to the English one. Recent changes in my translation app have made it easier, however. I can test most of the application (Japanese text display, file parsing and I/O) under the English UI (it displays Japanese just fine). I have to switch to the Japanese UI to test the text entry, however. Sorry to have gone on and on about this :-O. I've spent the last 8 working days on this issue, and it's rather nice to finally have it ironed out :sigh:.
Software Zen:
delete this; -
Jeremy Falcon wrote: That's news to me. As you know, resource scripts are essentially source files. The bulk of the file is syntactic elements that describe bits and pieces of the user interface. The language-specific text actually occupies a relatively small portion of the file. I think you could justify converting the whole mess to UNICODE, however. The syntactic elements (
DIALOG,BEGIN/END,STRINGTABLE, etc.) aren't any more difficult to parse and identify as UNICODE than they are in an ANSI character set. The screen text, however, is required to be unambiguous. The current methodology involves multiple translations between an MBCS code page and UNICODE. Each translation has the potential for data loss. For example, if a UNICODE character doesn't have a corresponding MBCS representation, you're stuck. Unless you are supporting Windows 95, UNICODE is a better way to go. It's supported natively in Windows NT/2000/XP, and with an add-on for Windows 98. Jeremy Falcon wrote: we've been doing all the Japanese development on a Japanese version of Windows XP with minimal problems Thus far I've been able to get away with using the Japanese add-on from the XP multilingual pack. It adds Japanese fonts and resources to English Windows. For a while I was switching back and forth from the Japanese UI to the English one. Recent changes in my translation app have made it easier, however. I can test most of the application (Japanese text display, file parsing and I/O) under the English UI (it displays Japanese just fine). I have to switch to the Japanese UI to test the text entry, however. Sorry to have gone on and on about this :-O. I've spent the last 8 working days on this issue, and it's rather nice to finally have it ironed out :sigh:.
Software Zen:
delete this;Gary R. Wheeler wrote: The screen text, however, is required to be unambiguous. You'd think everything would be Unicode for resource scripts then since MS dumped Win95. Gary R. Wheeler wrote: Sorry to have gone on and on about this . I've spent the last 8 working days on this issue, and it's rather nice to finally have it ironed out No problem, if I come across this issue in the future, I'm sure it'll help me out. :) Jeremy Falcon
