|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
I very rarely need this to warrant using a permanent solution as shown below since for me it's only when accessing external devices. What I usually do is to just set locale when mounting through the root user which will in turn load the appropriate character tables. Also I have no idea if the following will behave properly with East-Asian characters. So take it with a (big) grain of salt.
Without further ado... /boot/loader.conf: Code:
libiconv_load="YES" Code:
kiconv_preload="YES" kiconv_local_charsets="UFT-8" kiconv_foreign_charsets="UTF-8" Try charsets other than UTF-8 too. HTH
__________________
May the source be with you! |
|
||||
Did not work. No change at all actually.
When I try to manipulate such files with MC the error message is Code:
Error: Invalid argument (22) Very few files with English titles are affected. Chinese and Japanese in titles are not a problem. Files and directories that begin with Chinese or Japanese and an occasional English title cannot be read. The experiment of changing a few titles will have to wait until I get back to work in a few days. |
|
||||
I did an experiment. I have not yet tried with English titles that the system cannot read, only Chinese.
I used Windows to change the name of four directories from 孝經 , 孫子兵法 , 易經 , 道家經典 to 1, 2, 3, 4. There was no problem copying the directories and their files to the hard-drive. I then changed the names to the Chinese ones and tried to copy them to the USB drive, but they could not be written to the device. Code:
bocere/USB/My_Transcriptions/孫子兵法: Invalid argument (22) Failed to move /home/bocere/USB/My_Transcriptions/1 as /home/bocere/USB/My_Transcriptions/孫子兵法 I changed the names of four photographs to 綿陽501, 綿陽502, 綿陽503, 綿陽504 and they also cannot be copied to the USB drive. I also noticed that the system cannot do anything with files with names like 1_一-戶.odt although that is exactly how the system sees the name, including the .odt extension. |
|
|||
For cases when mounting external devices, you should do what I mentioned in my previous post.
# mount_msdosfs -L en_US.UTF-8 -D UTF-8 ... I'm not using my computer right now, but I think it's correct. Note that this must be done as root.
__________________
May the source be with you! |
|
||||
I must have missed that part of your post.
mount_msdosfs -L en_US.UTF-8 -D UTF-8 works for most of the files. Only a few songs with English titles are still invalid arguments. They are all .wav files, but most of the .wav files are fine. And one directory is still a problem: Code:
File doesn't exist, or I can't access it: /home/bocere/USB/academic/China/history/1-Ancient_China:Studies_in_Early_Civilisation The only glitch is that FreeBSD no longer displays the correct characters. For example, 婚禮 shows ups as å©ç¦®. For now I consider the problem solved, since only a very small number of files are still affected. That is an inconvenience, not a problem. Displaying unintelligible characters is a bigger inconvenience, but I know what the contents are and can work on solving it at my leisure. Thanks for the help. Last edited by sacerdos_daemonis; 27th September 2019 at 10:38 PM. |
|
|||
Quote:
This is while copying from your computer to the external device, right? That's because the colon (":") is a valid filename character for UFS2 but invalid on FAT and NTFS (outside POSIX namespace) since Windows uses it to separate the drive letter from the rest of the path. Personally, no matter the filesystem I usually automatically replace the colon with " - " (space hyphen space). IMHO it's always better, both technically and aesthetically.
__________________
May the source be with you! |
|
||||
Replacing the colons with underscores solved that problem. The two .wav files where fixed by removing commas, which is very strange. The files were originally downloaded many years ago with Windows and were fine over the years with Windows, Linux and OpenBSD, but FreeBSD and newer versions of Windows cannot read them. ????? Computers can be a pain in the arse sometimes.
|
|
|||
Quote:
If for example in Microsoft Word you save a file that has a comma in the first line, Word will use that line (including the comma) as your filename. And you may end up with filenames that are valid in Windows and NTFS/FAT32 and invalid/unreadable when moving the file to other operating systems and file systems. The same is true for many other characters (ellipsis instead of 3 dots, dash instead of hyphen, etc.) The real problem is that character encoding itself is a total mess. In the past, many DOS code pages and Windows code pages "standards" were in use. And since old habits die hard, even when Microsoft tried to impose UTF-8/16, everyone practically kept on using the system's locale default encoding.
__________________
May the source be with you! |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
NTFS on OpenBSD, "Invalid argument" | Smith | OpenBSD General | 21 | 25th August 2014 08:30 AM |
mount_cd9660 : Invalid argument .. | daemonfowl | OpenBSD General | 5 | 23rd February 2012 02:40 PM |
cat: [file]: Invalid argument | pieterverberne | OpenBSD General | 6 | 19th November 2011 02:43 PM |
mount-msdosfs /dev/dao: : Invalid argument | harold | FreeBSD General | 5 | 12th December 2010 06:59 AM |
Mount DVD - invalid argument. | maxrussell | FreeBSD General | 17 | 7th January 2009 08:46 AM |