> Don't know about the Novell stuff, but I've run into filename parsing
> problems before with x-plat stuff. The solution was to do a search and
> replace in the file names for the "bad" chars, and replace them with
> "tags".
> Then, in the methods that needed paths, there would be a quick
> conversion of
> the file name "asked" for... as in, if you have a menu item that calls
> mGetFile("espa�ol.swa"), mGetFile would first turn "espa�ol.swa" into
> "espa_n1_ol.swa", then go hunting the file.
>
Thanks, Kurt. I've proposed a similar solution in case Novell can't be
fixed. It would be even easier in my case, because we always identify
the Spanish with an "_s" at the end. For example, surrounded_e.mov and
rode�_s.mov.
I can pretty easily just change that to rodeo_s.mov, and do a file name
conversion on the fly. The conversion is necessary because we have the
glossary in a database, and we're building the file name from the
glossary word.
You're right--there are only a handful of accented characters in
Spanish. I can use offset() to check for those characters, and do a
quick replacement.
The coding isn't that tough--I could do it in an afternoon, probably.
The problem is, QA would want to do another round, checking each
activity in each story. Six grades, six themes per grade, 3-4 stories
per theme, 3 activities per story--that's about 350 movies, and probably
5,000 audio files. They'll be testing for a month. I know--our QA
department is incredibly anal. I guess that's their job.
So, I'm looking for the "safe" fix--i.e., a way to get Windows and
Novell to talk the same language, without reinstalling. There's got to
be a way. Or not--maybe that's why Novell has been steadily losing
market share.
I'll let you know what I find out.
Cordially,
Kerry Thompson
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]