Xailer & OZ Software

David,
> I'm having problem to compile (cap3.jpg) the sample in DBFData6
> (Traditional Chinese XP). No problem with English XP.
It seems there is a problem with the resource compiler, not the windows
version. What rc are you using in both cases? I've just tested it with MS
rc.exe (fails to compile it) and with Borland brc32.exe (success).
> Why some fonts are not available in Customizing Editor ? The "Fixedsys"
> font is quite difficult to read under Chinese XP for some reason. What
> is the "Fixedsys" font of XP ?
It's a fixed size font, but I'm not sure if all windows versions ship it.
You may use "courier new" as an alternative.
> I sometime read from NG that a OBJ should be placed into a project (for
> bug fix), where should it goes ? I can't find the place to put an
> 'external' obj file ?
> Is it to insert it into the project manager ? The linking process will
> incorporate this obj and thus 'take over' the buggy routine ?
Yes, simply add the .obj file to the project. However, sometimes the linker
fails to link the correct module to the executable and links the lib's one
instead of project's one. It's a linker bug, but fortunately, it happens
very seldom.
--
Regards,
Jose F. Gimenez
http://www.xailer.com

Jose F. Gimenez wrote:
> David,
>
>> I'm having problem to compile (cap3.jpg) the sample in DBFData6
>> (Traditional Chinese XP). No problem with English XP.
>
> It seems there is a problem with the resource compiler, not the windows
> version. What rc are you using in both cases? I've just tested it with MS
> rc.exe (fails to compile it) and with Borland brc32.exe (success).
>
>
I'm using the default resource compiler (???). I don't think I have
installed MS rc in the Chinese XP machine. I think it has something to
do with the character set. I'm use Chinese Big 5 in Chinese XP & ANSI in
English XP.
>> Why some fonts are not available in Customizing Editor ? The "Fixedsys"
>> font is quite difficult to read under Chinese XP for some reason. What
>> is the "Fixedsys" font of XP ?
>
> It's a fixed size font, but I'm not sure if all windows versions ship it.
> You may use "courier new" as an alternative.
>
>
Why some fonts are missing from the listbox, any idea ?
>> I sometime read from NG that a OBJ should be placed into a project (for
>> bug fix), where should it goes ? I can't find the place to put an
>> 'external' obj file ?
>> Is it to insert it into the project manager ? The linking process will
>> incorporate this obj and thus 'take over' the buggy routine ?
>
> Yes, simply add the .obj file to the project. However, sometimes the linker
> fails to link the correct module to the executable and links the lib's one
> instead of project's one. It's a linker bug, but fortunately, it happens
> very seldom.
>

Jose F. Gimenez wrote:
> David,
>
>> I'm having problem to compile (cap3.jpg) the sample in DBFData6
>> (Traditional Chinese XP). No problem with English XP.
>
> It seems there is a problem with the resource compiler, not the windows
> version. What rc are you using in both cases? I've just tested it with MS
> rc.exe (fails to compile it) and with Borland brc32.exe (success).
>
>
I'm using the default resource compiler (???). I don't think I have
installed MS rc in the Chinese XP machine. I think it has something to
do with the character set. I'm use Chinese Big 5 in Chinese XP & ANSI in
English XP.
>> Why some fonts are not available in Customizing Editor ? The "Fixedsys"
>> font is quite difficult to read under Chinese XP for some reason. What
>> is the "Fixedsys" font of XP ?
>
> It's a fixed size font, but I'm not sure if all windows versions ship it.
> You may use "courier new" as an alternative.
>
>
Why some fonts are missing from the listbox, any idea ?
>> I sometime read from NG that a OBJ should be placed into a project (for
>> bug fix), where should it goes ? I can't find the place to put an
>> 'external' obj file ?
>> Is it to insert it into the project manager ? The linking process will
>> incorporate this obj and thus 'take over' the buggy routine ?
>
> Yes, simply add the .obj file to the project. However, sometimes the linker
> fails to link the correct module to the executable and links the lib's one
> instead of project's one. It's a linker bug, but fortunately, it happens
> very seldom.
>

David,
> I'm using the default resource compiler (???). I don't think I have
> installed MS rc in the Chinese XP machine. I think it has something to do
> with the character set. I'm use Chinese Big 5 in Chinese XP & ANSI in
> English XP.
It's rather strange. I tried setting "Chinese Big 5" in the IDE, and it
compiles fine. Of course, I can't see the correct spanish characters, but it
compiles without error. In fact, the selected charset has no effect over the
compilation process.
Please, if possible, send me a sample .rc file with strings in Chinese. Just
to test here the opposite.
> Why some fonts are missing from the listbox, any idea ?
Only 'fixed space' fonts are shown.
--
Regards,
Jose F. Gimenez
http://www.xailer.com

David,
> I'm using the default resource compiler (???). I don't think I have
> installed MS rc in the Chinese XP machine. I think it has something to do
> with the character set. I'm use Chinese Big 5 in Chinese XP & ANSI in
> English XP.
It's rather strange. I tried setting "Chinese Big 5" in the IDE, and it
compiles fine. Of course, I can't see the correct spanish characters, but it
compiles without error. In fact, the selected charset has no effect over the
compilation process.
Please, if possible, send me a sample .rc file with strings in Chinese. Just
to test here the opposite.
> Why some fonts are missing from the listbox, any idea ?
Only 'fixed space' fonts are shown.
--
Regards,
Jose F. Gimenez
http://www.xailer.com

Jose F. Gimenez wrote:
> David,
>
>> I'm using the default resource compiler (???). I don't think I have
>> installed MS rc in the Chinese XP machine. I think it has something to do
>> with the character set. I'm use Chinese Big 5 in Chinese XP & ANSI in
>> English XP.
>
> It's rather strange. I tried setting "Chinese Big 5" in the IDE, and it
> compiles fine. Of course, I can't see the correct spanish characters, but it
> compiles without error. In fact, the selected charset has no effect over the
> compilation process.
>
> Please, if possible, send me a sample .rc file with strings in Chinese. Just
> to test here the opposite.
The spanish.rc (in Richedit application) is from the sample. I did not
change anything. Chinese XP re-interrupt the spanish character and
treated them as double byte Chinese character (ie two letters will be
presented as one Chinese character).
Can I use English O/S to compile the rc file ? Does Xailer compiles the
rc everytime no matter the rc was changed or not ?
>
>
>> Why some fonts are missing from the listbox, any idea ?
>
> Only 'fixed space' fonts are shown.
>
>

Jose F. Gimenez wrote:
> David,
>
>> I'm using the default resource compiler (???). I don't think I have
>> installed MS rc in the Chinese XP machine. I think it has something to do
>> with the character set. I'm use Chinese Big 5 in Chinese XP & ANSI in
>> English XP.
>
> It's rather strange. I tried setting "Chinese Big 5" in the IDE, and it
> compiles fine. Of course, I can't see the correct spanish characters, but it
> compiles without error. In fact, the selected charset has no effect over the
> compilation process.
>
> Please, if possible, send me a sample .rc file with strings in Chinese. Just
> to test here the opposite.
The spanish.rc (in Richedit application) is from the sample. I did not
change anything. Chinese XP re-interrupt the spanish character and
treated them as double byte Chinese character (ie two letters will be
presented as one Chinese character).
Can I use English O/S to compile the rc file ? Does Xailer compiles the
rc everytime no matter the rc was changed or not ?
>
>
>> Why some fonts are missing from the listbox, any idea ?
>
> Only 'fixed space' fonts are shown.
>
>

David,
I've just found it!
The problem is at line 20. Simply change the two instances of " into '.
Attached is the file already fixed. Please, test it and tell me if it works
fine.
--
Regards,
Jose F. Gimenez
http://www.xailer.com


Attached files spanish.zip (2.9 KB)Â

David,
I've just found it!
The problem is at line 20. Simply change the two instances of " into '.
Attached is the file already fixed. Please, test it and tell me if it works
fine.
--
Regards,
Jose F. Gimenez
http://www.xailer.com


Attached files spanish.zip (2.9 KB)Â

Jose F. Gimenez wrote:
> David,
>
> I've just found it!
>
> The problem is at line 20. Simply change the two instances of " into '.
> Attached is the file already fixed. Please, test it and tell me if it works
> fine.
>
>
Perfect ! Can you tell me what happened ? How this type of error be
corrected ?
Thank you very much.
David

Jose F. Gimenez wrote:
> David,
>
> I've just found it!
>
> The problem is at line 20. Simply change the two instances of " into '.
> Attached is the file already fixed. Please, test it and tell me if it works
> fine.
>
>
Perfect ! Can you tell me what happened ? How this type of error be
corrected ?
Thank you very much.
David

David,
> Perfect ! Can you tell me what happened ? How this type of error be
> corrected ?
The problem is that the resource compiler uses the computer language to
process the strings. In Chinesse Big 5, some characters are built using 2
bytes, unlike the latin charset (as spanish) where all characters are 1 byte
length.
In that file, at line 20, there was a string like this:
".... esta"...."
That is, we were using the char sequence " to include the 'double cuote'
character in the string. But, in fact, the 'a' character just before that
sequence was an 'a acute', and caused that the pair a was interpreted as a
chinesse character, leaving the 'double cuote' char alone, which closed the
string. So, the string was compiled like (the X char means a chinesse char):
"...estX"..."
As you can see, this string is not correct.
--
Regards,
Jose F. Gimenez
http://www.xailer.com

David,
> Perfect ! Can you tell me what happened ? How this type of error be
> corrected ?
The problem is that the resource compiler uses the computer language to
process the strings. In Chinesse Big 5, some characters are built using 2
bytes, unlike the latin charset (as spanish) where all characters are 1 byte
length.
In that file, at line 20, there was a string like this:
".... esta"...."
That is, we were using the char sequence " to include the 'double cuote'
character in the string. But, in fact, the 'a' character just before that
sequence was an 'a acute', and caused that the pair a was interpreted as a
chinesse character, leaving the 'double cuote' char alone, which closed the
string. So, the string was compiled like (the X char means a chinesse char):
"...estX"..."
As you can see, this string is not correct.
--
Regards,
Jose F. Gimenez
http://www.xailer.com

Jose F. Gimenez wrote:
> David,
>
>> Perfect ! Can you tell me what happened ? How this type of error be
>> corrected ?
>
> The problem is that the resource compiler uses the computer language to
> process the strings. In Chinesse Big 5, some characters are built using 2
> bytes, unlike the latin charset (as spanish) where all characters are 1 byte
> length.
>
> In that file, at line 20, there was a string like this:
>
> ".... esta"...."
>
> That is, we were using the char sequence " to include the 'double cuote'
> character in the string. But, in fact, the 'a' character just before that
> sequence was an 'a acute', and caused that the pair a was interpreted as a
> chinesse character, leaving the 'double cuote' char alone, which closed the
> string. So, the string was compiled like (the X char means a chinesse char):
>
> "...estX"..."
>
> As you can see, this string is not correct.
>
I see, thank you.
David

Jose F. Gimenez wrote:
> David,
>
>> Perfect ! Can you tell me what happened ? How this type of error be
>> corrected ?
>
> The problem is that the resource compiler uses the computer language to
> process the strings. In Chinesse Big 5, some characters are built using 2
> bytes, unlike the latin charset (as spanish) where all characters are 1 byte
> length.
>
> In that file, at line 20, there was a string like this:
>
> ".... esta"...."
>
> That is, we were using the char sequence " to include the 'double cuote'
> character in the string. But, in fact, the 'a' character just before that
> sequence was an 'a acute', and caused that the pair a was interpreted as a
> chinesse character, leaving the 'double cuote' char alone, which closed the
> string. So, the string was compiled like (the X char means a chinesse char):
>
> "...estX"..."
>
> As you can see, this string is not correct.
>
I see, thank you.
David