main logo
Subject: Re: [C++] Support of all: char* path, POSIX path, FSRef, FSSpec
Author: Ruslan Zasukhin
Posted: 2002/11/28 08:59:49
 
View Entire Thread
New Search


on 11/28/02 1:11 PM, Andreas Grosam at agrosam (AT) computerworks .D.O.T ch wrote:

Hi Andreas,

> I tend to simplicity:
> Support only the POSIX path (narrow char filenames) in the interfaces.
>
> For Mac and other "exotic" OS add an addionally library, where users (we) can
> convert from FSSpec to a path. MoreFiles is OK, so you need just to refere to
> it.

I have resolve problem how to convert POSIX path on macho into FSSpec.
Yes this require POSIX path.

As far as I see, using of true native FSRef will allow end-users to have
folders with Unicode names as well as names of db files.

I think this is not big deal if we do not support that for now.

Totte, you can easy convert FSRef into FSSpec.
So I think in your app you CAN use FSRef right now, yes?

> On original UNIX, the file system does not support unicode (or UCS, ISO 10646,
> etc) for filenames (although UNIX may support several character codes in
> narrow characters and different locales). And if it is supported on a certain
> system (mostly UTF-8 only), using unicode might lead to severe problems, at
> least portability issues and "moving" databases from one system to another, or
> UNIX tools not taking care of it.
> unicode is an OS specific extension.

At least on Unix life will be easy :-)
I am not going use Unicode on Unix. I just want be friendly to MacOS X.

> Disadvantage: there might be ambiguities on the Mac (and restrictions) - but
> since the advent of MacOS X we should avoid ambiguities in volumn names and
> filenames because of the UNIX under the hat.
>
> IMO, not having UNI code and several encodings for filenames, shouldn't be an
> issue for us -- but we want it for database strings! ;)

Agree

> And, for you Ruslan, it might be an issue if you need to refere to filenames
> which are stored in meta data section of the database. Then you need to
> fiddling around with unicode and encodings and generally take care of it -
> probably in common portable source code.
> Supporting unicode might be unneccessary and exaggerated for that purpose.

--
Best regards,
Ruslan Zasukhin [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan@paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list
send a letter to valentina-on (AT) lists .D.O.T macserve.net
-------------------------------------------------------------
 
©2002 Ruslan Zasukhin
<-- Prior Message New Search Next Message -->