New answers tagged

0

(Moved answer from May 2012 from question to here) So now I «fixed» this by re-installing the system. No idea what the problem was. To get the keyboard right everywhere (tty, KDM login screen, KDE) I had to run dpkg-reconfigure locales # Kept only (de_CH|en_US|ru_RU).UTF-8 # Selected de_CH.UTF-8 as default dpkg-...


1

Thanks for @SiyuanRen 's suggestion. convmv can deal with the mess situation keeping ascii unchanged which avoid being garbled. Command convmv -f gbk -t utf8 * works fine under this circumstance. By the way, another solution is use -o loop,utf8 while mounting image files, or just use udisksctl which can automatically deal with filename encoding. P.S. the ...


0

Unlike XML, which should contain an encoding tag that describes the original content encoding you have to get that piece of information for csv with other means. While type works pretty well on binary data, it does not work well on text data. This is due to the way the command works. see man text. Roughly: It looks at the first couple of bytes and tries to ...


0

Shell In shell you can use printf: printf "%b" '\x66\x6f\x6f' > file.bin Note: %b - Print the associated argument while interpreting backslash escapes. Perl With perl, it is even simpler: perl -e 'print pack("ccc",(0x66,0x6f,0x6f))' > file.bin Python If you've Python installed, try the following one-liner: python -c $'from struct import ...


4

The POSIX standard introduces a POSIX locale, which has the same order as the ASCII character set for characters in ASCII (POSIX Base Definitions §7.3.2). Besides that, on systems where the symbolic constant POSIX2_LOCALEDEF is defined (which shall be defined for XSI-conformant systems, and can be tested via getconf POSIX2_LOCALEDEF), the system supports ...


17

There is no specific character encoding mandated by POSIX. The only character in a fixed position is null, which must be 00. What POSIX does require is that all characters from its Portable Character Set exist. The Portable Character Set contains the printable ASCII characters, space, BEL, backspace, tab, carriage return, newline, vertical tab, form feed, ...


3

I'm sure they are just some sort of mis-encoded control characters, but I'm just trying to work out what these two characters are, ⎠is what happens when one displays the transmitted octets \xc2 \x8e decoded with Windows code page 1252. Your terminal emulator is using a single-byte character set. Decoded as UTF-8, rather, that is the SS2 control ...



Top 50 recent answers are included