[opensuse-support] Does NFS allow different encodings to be used on server/client side?
Hello. While I use iso-8859-1 in my systems, my friend uses utf-8. This is actually no big issue when using rsync (as it can convert filenames on the fly), but now I wanted to use KODI on my FireTV stick. KODI appears to use only UTF8 when using its built-in nfs-client, or it has a bug and ignores the configured character set. Anyway, Kodi does not show German Umlauts therefore. Can I configure the kernel-nfs on my server to do something similar to rsync by using "--iconv=iso-8859-1,utf-8"? So my server-side encoding is translated to UTF8 only for this FireTV stick? I had a look into the man pages, but I could not find anything about that. I also googled and figured out that some nfs servers allow that, others don't, ... Would be great if this is possible on openSUSE. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 18/01/2019 10.00, Rainer Hantsch wrote:
Hello. While I use iso-8859-1 in my systems, my friend uses utf-8.
This is actually no big issue when using rsync (as it can convert filenames on the fly), but now I wanted to use KODI on my FireTV stick. KODI appears to use only UTF8 when using its built-in nfs-client, or it has a bug and ignores the configured character set.
Anyway, Kodi does not show German Umlauts therefore.
Can I configure the kernel-nfs on my server to do something similar to rsync by using "--iconv=iso-8859-1,utf-8"? So my server-side encoding is translated to UTF8 only for this FireTV stick?
I had a look into the man pages, but I could not find anything about that. I also googled and figured out that some nfs servers allow that, others don't, ...
Would be great if this is possible on openSUSE.
I don't think so. "Converting" the name of a file means altering it on disk. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am Freitag, 18. Jan 2019, 10:36:12 schrieb Carlos E. R.:
On 18/01/2019 10.00, Rainer Hantsch wrote:
Hello. While I use iso-8859-1 in my systems, my friend uses utf-8.
This is actually no big issue when using rsync (as it can convert filenames on the fly), but now I wanted to use KODI on my FireTV stick. KODI appears to use only UTF8 when using its built-in nfs-client, or it has a bug and ignores the configured character set.
Anyway, Kodi does not show German Umlauts therefore.
Can I configure the kernel-nfs on my server to do something similar to rsync by using "--iconv=iso-8859-1,utf-8"? So my server-side encoding is translated to UTF8 only for this FireTV stick?
I had a look into the man pages, but I could not find anything about that. I also googled and figured out that some nfs servers allow that, others don't, ...
Would be great if this is possible on openSUSE.
I don't think so. "Converting" the name of a file means altering it on disk.
Then I did wrongly explain, sorry for that. Server side: The server is using globally(!) ISO-8859-1 (or iso-8859-15 ?) as encoding. This means that filenames (not the content) are alsostored in this encoding. This is fine for me, usually this encoding is more than sufficient for my needs. So what I am talking about is: When I know that one particular device expects UTF8, I want to assign parameters to his exports entry, so that my nfs server translates the filenames from 8859-1/15 -> UTF8 before transmitting them. And vice versa. Samba can do that, so possibly nfs can do that, too? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Fri, Jan 18, 2019 at 2:11 PM Rainer Hantsch <office@hantsch.co.at> wrote:
When I know that one particular device expects UTF8, I want to assign parameters to his exports entry, so that my nfs server translates the filenames from 8859-1/15 -> UTF8 before transmitting them. And vice versa.
Samba can do that, so possibly nfs can do that, too?
No. https://bugzilla.redhat.com/show_bug.cgi?id=529844 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 18/01/2019 12.11, Rainer Hantsch wrote:
Am Freitag, 18. Jan 2019, 10:36:12 schrieb Carlos E. R.:
On 18/01/2019 10.00, Rainer Hantsch wrote:
Hello. While I use iso-8859-1 in my systems, my friend uses utf-8.
This is actually no big issue when using rsync (as it can convert filenames on the fly), but now I wanted to use KODI on my FireTV stick. KODI appears to use only UTF8 when using its built-in nfs-client, or it has a bug and ignores the configured character set.
Anyway, Kodi does not show German Umlauts therefore.
Can I configure the kernel-nfs on my server to do something similar to rsync by using "--iconv=iso-8859-1,utf-8"? So my server-side encoding is translated to UTF8 only for this FireTV stick?
I had a look into the man pages, but I could not find anything about that. I also googled and figured out that some nfs servers allow that, others don't, ...
Would be great if this is possible on openSUSE.
I don't think so. "Converting" the name of a file means altering it on disk.
Then I did wrongly explain, sorry for that.
Server side: The server is using globally(!) ISO-8859-1 (or iso-8859-15 ?) as encoding. This means that filenames (not the content) are alsostored in this encoding. This is fine for me, usually this encoding is more than sufficient for my needs.
So what I am talking about is: When I know that one particular device expects UTF8, I want to assign parameters to his exports entry, so that my nfs server translates the filenames from 8859-1/15 -> UTF8 before transmitting them. And vice versa.
Samba can do that, so possibly nfs can do that, too?
But samba was designed for Windows, where this happens often. NFS was designed for Linux, and AFAIK, it expects UTF8 only. I could be mistaken, though. However, googling suggests I may be mistaken. <https://unix.stackexchange.com/questions/105223/how-to-mount-an-ntfs-drive-as-utf8-over-nfs> See answer #4. http://tools.ietf.org/html/rfc5661#section-14.4 however, <https://www.tldp.org/HOWTO/Indic-Fonts-HOWTO/locale.html> «The other filesystems (nfs, smbfs, ncpfs, hpfs, etc.) don't convert filenames; therefore they support Unicode file names in UTF-8 encoding only if the other operating system supports them. Please note that to enable a mount option for all future remounts, you add it to the fourth column of the corresponding /etc/fstab line.» <https://www.tldp.org/HOWTO/Unicode-HOWTO-3.html> has the same paragraph. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Fri, 18 Jan 2019 10:00:06 +0100 Rainer Hantsch <office@hantsch.co.at> wrote:
Hello. While I use iso-8859-1 in my systems, my friend uses utf-8.
Actually, not just your friend but most people in the world. I would suggest you consider converting your systems to utf-8.
This is actually no big issue when using rsync (as it can convert filenames on the fly), but now I wanted to use KODI on my FireTV stick. KODI appears to use only UTF8 when using its built-in nfs-client, or it has a bug and ignores the configured character set.
Anyway, Kodi does not show German Umlauts therefore.
Can I configure the kernel-nfs on my server to do something similar to rsync by using "--iconv=iso-8859-1,utf-8"? So my server-side encoding is translated to UTF8 only for this FireTV stick?
You could create a new directory to serve your media to kodi. Only use a utf-8 environment when creating entries in it. Fill it with hard links to your existing media files. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 18/01/2019 11.16, Dave Howorth wrote:
On Fri, 18 Jan 2019 10:00:06 +0100 Rainer Hantsch <office@hantsch.co.at> wrote:
Hello. While I use iso-8859-1 in my systems, my friend uses utf-8.
Actually, not just your friend but most people in the world.
I would suggest you consider converting your systems to utf-8.
Except on Windows :-) For instance, I use some video recording software designed primarily for windows. Apparently, the names of the videos are set by the broadcaster, and while they display correctly in Kodi, they don't on Linux. Another example: when I edit TomTom POIs using website <https://tomtom.gps-data-team.com/poi/poi_edit_online.php>, the names display correctly in FF in Linux, but don't on the TomTom (which is said to use Linux inside, but...).
This is actually no big issue when using rsync (as it can convert filenames on the fly), but now I wanted to use KODI on my FireTV stick. KODI appears to use only UTF8 when using its built-in nfs-client, or it has a bug and ignores the configured character set.
Anyway, Kodi does not show German Umlauts therefore.
Can I configure the kernel-nfs on my server to do something similar to rsync by using "--iconv=iso-8859-1,utf-8"? So my server-side encoding is translated to UTF8 only for this FireTV stick?
You could create a new directory to serve your media to kodi. Only use a utf-8 environment when creating entries in it. Fill it with hard links to your existing media files.
Doesn't work when trying to move, copy, delete movies. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Fri, 18 Jan 2019 12:48:53 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 18/01/2019 11.16, Dave Howorth wrote:
On Fri, 18 Jan 2019 10:00:06 +0100 Rainer Hantsch <office@hantsch.co.at> wrote:
Hello. While I use iso-8859-1 in my systems, my friend uses utf-8.
Actually, not just your friend but most people in the world.
I would suggest you consider converting your systems to utf-8.
Except on Windows :-)
Eh, 'Microsoft was one of the first companies to implement Unicode' https://en.wikipedia.org/wiki/Unicode_in_Microsoft_Windows
For instance, I use some video recording software designed primarily for windows. Apparently, the names of the videos are set by the broadcaster, and while they display correctly in Kodi, they don't on Linux.
Broadcast character sets are a nightmare, they have their own character sets defined in the DVB standards not the usual suspects, and then they sometimes transmit 'broken' strings, where the source of the text might be some old windows system, transferred by some ignorant old system to the transmitter and wrongly labelled. Most TV text systems simply delete any bad characters when preparing them for display so punters don't see rubbish on screen. Kodi is one such.
Another example: when I edit TomTom POIs using website <https://tomtom.gps-data-team.com/poi/poi_edit_online.php>, the names display correctly in FF in Linux, but don't on the TomTom (which is said to use Linux inside, but...).
Old linux systems used to use iso-8859-*
This is actually no big issue when using rsync (as it can convert filenames on the fly), but now I wanted to use KODI on my FireTV stick. KODI appears to use only UTF8 when using its built-in nfs-client, or it has a bug and ignores the configured character set.
Anyway, Kodi does not show German Umlauts therefore.
Can I configure the kernel-nfs on my server to do something similar to rsync by using "--iconv=iso-8859-1,utf-8"? So my server-side encoding is translated to UTF8 only for this FireTV stick?
You could create a new directory to serve your media to kodi. Only use a utf-8 environment when creating entries in it. Fill it with hard links to your existing media files.
Doesn't work when trying to move, copy, delete movies.
You'll have to explain why not. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 18/01/2019 13.15, Dave Howorth wrote:
On Fri, 18 Jan 2019 12:48:53 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 18/01/2019 11.16, Dave Howorth wrote:
On Fri, 18 Jan 2019 10:00:06 +0100 Rainer Hantsch <office@hantsch.co.at> wrote:
Hello. While I use iso-8859-1 in my systems, my friend uses utf-8.
Actually, not just your friend but most people in the world.
I would suggest you consider converting your systems to utf-8.
Except on Windows :-)
Eh, 'Microsoft was one of the first companies to implement Unicode' https://en.wikipedia.org/wiki/Unicode_in_Microsoft_Windows
Isn't it UTF-16?
For instance, I use some video recording software designed primarily for windows. Apparently, the names of the videos are set by the broadcaster, and while they display correctly in Kodi, they don't on Linux.
Broadcast character sets are a nightmare, they have their own character sets defined in the DVB standards not the usual suspects, and then they sometimes transmit 'broken' strings, where the source of the text might be some old windows system, transferred by some ignorant old system to the transmitter and wrongly labelled. Most TV text systems simply delete any bad characters when preparing them for display so punters don't see rubbish on screen. Kodi is one such.
Argh. Yes, your explanation fits the symptoms.
Another example: when I edit TomTom POIs using website <https://tomtom.gps-data-team.com/poi/poi_edit_online.php>, the names display correctly in FF in Linux, but don't on the TomTom (which is said to use Linux inside, but...).
Old linux systems used to use iso-8859-*
Yep. I have no idea what Linux they use now. It is a modern TomTom, but I see no way to look inside - years ago it was possible. I will try to edit them using FF inside Windows on a virtual machine.
This is actually no big issue when using rsync (as it can convert filenames on the fly), but now I wanted to use KODI on my FireTV stick. KODI appears to use only UTF8 when using its built-in nfs-client, or it has a bug and ignores the configured character set.
Anyway, Kodi does not show German Umlauts therefore.
Can I configure the kernel-nfs on my server to do something similar to rsync by using "--iconv=iso-8859-1,utf-8"? So my server-side encoding is translated to UTF8 only for this FireTV stick?
You could create a new directory to serve your media to kodi. Only use a utf-8 environment when creating entries in it. Fill it with hard links to your existing media files.
Doesn't work when trying to move, copy, delete movies.
You'll have to explain why not.
Well, the operation would be done on the symlinks, the file would still be there and no disk space saved. I would have to repeat the delete operation on the "actual" file. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Fri, 18 Jan 2019 13:27:56 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 18/01/2019 13.15, Dave Howorth wrote:
On Fri, 18 Jan 2019 12:48:53 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 18/01/2019 11.16, Dave Howorth wrote:
On Fri, 18 Jan 2019 10:00:06 +0100 Rainer Hantsch <office@hantsch.co.at> wrote:
Hello. While I use iso-8859-1 in my systems, my friend uses utf-8.
Actually, not just your friend but most people in the world.
I would suggest you consider converting your systems to utf-8.
Except on Windows :-)
Eh, 'Microsoft was one of the first companies to implement Unicode' https://en.wikipedia.org/wiki/Unicode_in_Microsoft_Windows
Isn't it UTF-16?
For instance, I use some video recording software designed primarily for windows. Apparently, the names of the videos are set by the broadcaster, and while they display correctly in Kodi, they don't on Linux.
Broadcast character sets are a nightmare, they have their own character sets defined in the DVB standards not the usual suspects, and then they sometimes transmit 'broken' strings, where the source of the text might be some old windows system, transferred by some ignorant old system to the transmitter and wrongly labelled. Most TV text systems simply delete any bad characters when preparing them for display so punters don't see rubbish on screen. Kodi is one such.
Argh.
Yes, your explanation fits the symptoms.
Another example: when I edit TomTom POIs using website <https://tomtom.gps-data-team.com/poi/poi_edit_online.php>, the names display correctly in FF in Linux, but don't on the TomTom (which is said to use Linux inside, but...).
Old linux systems used to use iso-8859-*
Yep.
I have no idea what Linux they use now. It is a modern TomTom, but I see no way to look inside - years ago it was possible.
I will try to edit them using FF inside Windows on a virtual machine.
This is actually no big issue when using rsync (as it can convert filenames on the fly), but now I wanted to use KODI on my FireTV stick. KODI appears to use only UTF8 when using its built-in nfs-client, or it has a bug and ignores the configured character set.
Anyway, Kodi does not show German Umlauts therefore.
Can I configure the kernel-nfs on my server to do something similar to rsync by using "--iconv=iso-8859-1,utf-8"? So my server-side encoding is translated to UTF8 only for this FireTV stick?
You could create a new directory to serve your media to kodi. Only use a utf-8 environment when creating entries in it. Fill it with hard links to your existing media files.
Doesn't work when trying to move, copy, delete movies.
You'll have to explain why not.
Well, the operation would be done on the symlinks, the file would still be there and no disk space saved. I would have to repeat the delete operation on the "actual" file.
I was thinking of hard links rather than symlinks. Saving disk space is not an objective is it? I agree that deletions would not unlink the original entry. If that was an issue then I would revert to my original suggestion - change the entire system to Unicode (i.e. delete the original directory). -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 18/01/2019 15.27, Dave Howorth wrote:
On Fri, 18 Jan 2019 13:27:56 +0100 "Carlos E. R." <> wrote:
You could create a new directory to serve your media to kodi. Only use a utf-8 environment when creating entries in it. Fill it with hard links to your existing media files.
Doesn't work when trying to move, copy, delete movies.
You'll have to explain why not.
Well, the operation would be done on the symlinks, the file would still be there and no disk space saved. I would have to repeat the delete operation on the "actual" file.
I was thinking of hard links rather than symlinks. Saving disk space is not an objective is it? I agree that deletions would not unlink the original entry. If that was an issue then I would revert to my original suggestion - change the entire system to Unicode (i.e. delete the original directory).
I prefer living with it. Too much hassle. Kodi displays them correct, it is the file browsers when I want to organize the disk who don't, and then I have to work on the real files, not links. Yes, disk space is an objective when organizing the disk(s). So I admit there is no solution, and live with it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (4)
-
Andrei Borzenkov -
Carlos E. R. -
Dave Howorth -
Rainer Hantsch