I have not gotten any workarounds to my previously-posted file name bug, and 
wanted to let everyone know that I have entered it into the bug system as 
#6394.  As the candidates are saying in Pennsylvania USA: I would appreciate 
your vote.  This is an absolute deal-breaker for me.

SOAPBOX:  I cannot possibly believe that others on this list have not been 
stopped in their tracks by this apparent failure within the Rev engine.  What I 
am trying to do is not so far out of the mainstream, is it?  But my only 
solution while staying within the Revolution environment is to establish system 
requirements with customers that say, "All your files and folders must contain 
only low-ASCII characters". Fine for systems governed by Western European 
character sets, but a show stopper for Czech, Polish, and (it seems) many other 
charsets in the world.

Tell me it ain't so, Joe.

What a shame.

Here is the body of the report for additional detail.

++++++++++++++++++++++++++++++++++++++++++++++++

How to Reproduce
===================
Name a dummy file čů.txt  In case this does not render correctly in the QC 
Center system, those first two characters in the example name are
č : small c with caron
ů : small u with ring above

Then in Rev, use the answer file line below to point to this new file.

  answer file "The prompt..."
  answer (there is a file it)
  put it

The second will return false.  The 'put' will put cu.txt (unaccented c and u), 
which explains why line 2 returns false.  Rev flattens many high-ASCII 
characters to their unaccented equivalents.

in addition, the following

  answer file "The prompt..."
  answer the shortFilePath of it

returns empty.


Why This is a Blocker
====================
I am writing a reporting application that hinges on Rev's ability to faithfully 
read file names.  This bug prevents me from even addressing such files, even if 
the 'offending' character occurs in the long path name.

It stops me cold.  I must hire a specialist to write an external in C or I must 
move to another SDE entirely.  Therefore, this is for me a blocker and I am 
rating it as such.

This is (I believe) similar to enhancement request 674.



_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to