At 14:08 Uhr +0200 28.03.2000, Andreas Lehmann wrote:
>What are we doing wrong here? Is there any known solution for this?
First: Look at the console with ls or (preferred) echo * if the umlauts are okay on
disk when created with windows.
Second, look at your AppleVolumes.*
# volume format:
# path [name] [casefold=x] [codepage=y] [options=z,l,j] \
# [access=a,@b,c,d] [dbpath=path] [password=p]
#
#
# casefold options:
# tolower -> lowercases names in both directions
# toupper -> uppercases names in both directions
# xlatelower -> client sees lowercase, server sees uppercase
# xlateupper -> client sees uppercase, server sees lowercase
#
# access format:
# user1,@group,user2 -> restricts volume to listed users/groups
#
# miscellaneous options
# prodos -> make compatible with appleII clients.
# crlf -> enable crlf translation for TEXT files.
# noadouble -> don't create .AppleDouble unless a resource
# fork needs to be created.
#
# codepage=filename -> load filename from nls directory.
# dbpath=path -> store the database stuff in the following path.
# password=password -> set a volume password (8 characters max)
#
I used maccode.iso8859-1 as codepage and since then all is okay.
:wq! PoC
