Bekijk de volledige versie : How to use ò à è ù in terminal ?
I've not found a way to use accented characters in terminal.
If I type à echo is correct, but if I try to create a file called Città with nano, nano opens but doesn't accept any accented inside and if I try to save the file, nano is unable to do it due to strange chars in filename.
I've found an interesting therad here (http://wl500g.info/showthread.php?t=13747&highlight=lang%3D), but I'm unable to translate to english, even with Google translate.
Can someone please help me ?
Thanks
Max
add the following line to ~/.profile :
export LANG="it_IT.UTF-8"
it should help with filenames. However nano in optware is compiled without UTF-8 support. You might want to install nano from here: http://code.google.com/p/wl500g/source/browse/#svn/ipkg/optware It is UTF-8 enabled.
Thanks al37919,
this solved file creation on Asus. Now I can vi using òàèù in filenames and file content (not yet installed nano from googlecode).
Files with accented chars are now visible to vsftp and browsable from an external ftp client, but now I have a problem with ipkg installed samba2 - 2.2.12-1.
If I create a file ò.txt in WinVista and then I copy it to a shared partition, this file will appear as a folder without name in Windows browser.
The same file from Putty appear as ò.txt... :confused:
samba2 in optware is also known to be non-UTF-8 compliant. However, why not use Oleg's built-in samba2? It has corresponding patches and works with UTF-8 correctly (at least in CR9 and CR10 for sure).
P.S. smb.conf should contain:
client code page = 866 (Russian DOS codepage)
coding system = utf8
So, I might be wrong, because Oleg was not able to include all codepages inside, so you have to try if your one is in. Otherwise you might need to build your own customized firmware binary.
Tnaks again al37919,
can you confirm that built-in Samba2 works with the same features of ipkg installed ?
I installed from ipkg due to old problem with Vista.
Does it support encrypt passwords (for MacOSX access) ?
Could I use my actual smb.conf adding
client code page = 850 (EU DOS codepage)
coding system = utf8 ?
# Samba config file created using SWAT
# from 192.168.1.2 (192.168.1.2)
# Date: 2009/10/11 17:36:21
# Global parameters
[global]
netbios name = MYASUS
server string = MyAsus Samba Server
security = SHARE
encrypt passwords = Yes
log file = /opt/var/log/samba/log.%m
max log size = 50
load printers = No
dns proxy = No
guest account = root
hosts allow = 192.168.1.
[Data]
comment = MyAsus Data
path = /mnt/Data
read only = No
guest ok = Yes
[Opt]
comment = MyAsus Opt
path = /opt
read only = No
guest ok = Yes
Oleg was not able to include all codepages inside
Is there a way to check it before remove my actual Samba ?
I think 850 is available cause I can see it from the web interface.
Max
Built in samba was patched by Oleg to comply with vista, however, I haven't tested that personally. No idea about macOSX.
Here is the list of codepages built into the firmware:
> ls -1 /usr/codepages/
codepage.437
codepage.850
codepage.852
codepage.866
unicode_map.437
unicode_map.850
unicode_map.852
unicode_map.866