Léopold Frey

mxj-dont-like-accents

> Did you had a loop at my other patch concerning long file names ?

> Did you had a loop at my other patch concerning long file names ?
I meant : "Did you had a look ..."
Sorry

Not yet. I am really swamped with some other stuff.

If I understand it you want the finder ID of the file.

Unfortunately that will not be happening in mxj land.

I would suggest rolling your own name convertor that

takes the absolute java path and turns it into an appropriate

path for sfplay. If there is some other problem with long filenames

On Jun 11, 2007, at 11:58 AM, Leopold Frey wrote:

>> Did you had a loop at my other patch concerning long file names ?

Not yet. I am really swamped with some other stuff.
If I understand it you want the finder ID of the file.
Unfortunately that will not be happening in mxj land.
I would suggest rolling your own name convertor that
takes the absolute java path and turns it into an appropriate
path for sfplay. If there is some other problem with long filenames
please let me know.
t

>
>> Did you had a loop at my other patch concerning long file names ?
> I meant : "Did you had a look ..."
> Sorry
>
> leo
>


On 11 Jun 2007, at 21:29, topher lafata wrote:

> it looks similar to the way DOS used to support long filenames 

> filenames could map to the same file reference.

I suspect this is the HFS -> HFS+ transition; HFS+ first appeared in 

MacOS 8.1. I guess there's some pre-HFS+ stuff still lying around in 

the Carbon API, or something. (I would certainly hope it's not 

> it looks similar to the way DOS used to support long filenames  
> where multiple
> filenames could map to the same file reference.

I suspect this is the HFS -> HFS+ transition; HFS+ first appeared in  
MacOS 8.1. I guess there's some pre-HFS+ stuff still lying around in  
the Carbon API, or something. (I would certainly hope it's not  
cropping up inside Java...)

Nick Rothwell / Cassiel.com Limited
www.cassiel.com
www.myspace.com/cassieldotcom
www.loadbang.net


Is anything happening on this? (for v 4.6.x?) Or has anyone found a workaround?

It still seems to be happening for me (Max 4.6.3 on Mac Intel) and i have a succinct patch and class that exhibits the behaviour (although my way "posts" to the message window ok, but "set"ing a message box comes out wrong).

It still seems to be happening for me  (Max 4.6.3 on Mac Intel) and i have a succinct patch and class that exhibits the behaviour (although my way "posts" to the message window ok, but "set"ing a message box comes out wrong).

(as in, "no support for accented characters in or out of mxj for Max 4.x apart from posting to the Max window" - long filename support should be in a different thread, imho)

Seems odd for such an international application...

As Topher didn't post anything new on this subject I suppose he's busy with something else.

IMHO don't expect a solution before Max 5, unless...

As Topher didn't post anything new on this subject I suppose he's busy with something else.
IMHO don't expect a solution before Max 5, unless...

Mxj don't like accents