Hi Xavier,
this may be related to a collection of semi-resolved/partially-fixed (engine
unicode support?..) bugs where characters outside of the standard Western
European character set are not being translated correctly. I guess it is the
same problem that prevents me from developing software in my own native
language as revolution does not understand input from my keyboard when set
to LT. These issues are fixed for some languages (it was reported for Polish
Hungarian, Czech some time ago and now it seems like it is fixed), and not
fixed for others.
See the quality reports 4677, 441, 1038, 1040, 1358. Look like a
long-standing issues with priority downgraded to minor...
All the best!
Viktoras
---Original Message---
From: [EMAIL PROTECTED]
Date: 20/06/2007 16:21:46
To: How to use Revolution
Subject: Re: the files functions doesn't work correctly
withdiacriticalcharacters
I think i found the problem:
The font (ms sans serif) of the fields in the revVariableWatcher doesn't
show the diacriticals as expected!!!
The Tahoma font works fine... well, sometimes...
set the directory to fld "path"
put the files into fld "log" -- works great at least in a tahoma field.
Which doesn't explain why the filename comparisons dont work yet but the
files functions works correctly at least!
I changed all the revVariableWatcher's field to Tahoma but the shell's
output was still unreadable!
So it's the shell! But in the shell (cmd.exe) dir displays correctly !!!
;)
Next step was to change the encoding of the shell from the standard 850
western1 codes to 1252. Because i found out
meanwhile that when piped to a file dir didn't show the text as expected
(sorry rev if i blamed this on you)!!!
And with chcp 1252 it did work as expected!
But then wabam, I can't get shell to do the right thing now!
I need to tell the shell that it needs to do first a chcp 1252 and then in
the same shell call, a dir of the folder but ...
Only the first line of the shell gets evaluated it seems! This is a
serious limitation in this case... And a speed problem since
the shell can't be done in rev but needs to be sent via a start.exe then
piped out then reinjected in rev in the right chr set...
And I thought rev was easy all over! If anyone is interested in multiline
shell calls in rev let me know, i'll make a bugzilla...
cheers
Xa
[EMAIL PROTECTED] wrote on 20/06/2007 13:42:56:
> Hi everyone,
>
> I have this file scanner that does some file listings and which needs to
> compare outputs with a shell dir.exe command (in windows 2003).
> The shell is too slow but it is the only one that shows me which files
are
> DHSM based (offline storage off the main storage).
>
> The problem i found is that the shell based dir output works correctly
but
> the runrev "the files" functions doesn't.
>
> The runrev output doesn't translate correctly the diacritical characters
> such as umlauts, or other german/french style characters.
>
> Has anyone seen this and better resolved it? Is there already a bugzilla
> for this?
>
> For the funny part, when i ask in rev if the file is there with the
> shell's file name output, rev does recognize it but i do a comparison of
> strings between
> the shell and rev's the file output, they do not match!!! Meaning that
the
> files functions is not compliant with windows?
>
> The shell's codepage is 850 in case anyone wondered. Is there anyway to
> change the codepage of rev's output?
>
> Thanks in advance for any help
>
> Regards,
> Xavier
>
>
>
> Clearstream Services S.A.
> 42 Avenue JF Kennedy, L-1855 Luxembourg
> Socit anonyme is organised with limited liability
> in the Grand Duchy of Luxembourg RC Luxembourg B 60911.
>
>
> -
> Visit us at http://www.clearstream.com
>
> IMPORTANT MESSAGE
>
> Internet communications are not secure and therefore Clearstream
> International does not accept legal responsibility for the contents
> of this message.
>
> The information contained in this e-mail is confidential and may be
> legally privileged. It is intended solely for the addressee. If you
> are not the intended recipient, any disclosure, copying,
> distribution or any action taken or omitted to be taken in reliance
> on it, is prohibited and may be unlawful. Any views expressed in
> this e-mail are those of the individual sender, except where the
> sender specifically states them to be the views of Clearstream
> International or of any of its affiliates or subsidiaries.
>
> Legally required info