Can not use `cut -c` (`--characters`) with UTF-8?2019 Community Moderator ElectionA command to print only last 3 characters of a stringHow to do a regex search in a UTF-16LE file while in a UTF-8 locale?Some UTF-8 characters not being recognized by grep or sedProcess a file that starts with a BOM (FF FE)support for utf-8 encoding with lprConverting documents to text with UTF-8 encodingFile weird character encodingLMDE2 / MATE locale charset inconsistencyfold and text columnsprintf: multibyte charactersRemoving characters with sed

Should I outline or discovery write my stories?

Why electric field inside a cavity of a non-conducting sphere not zero?

Why is it that I can sometimes guess the next note?

Which one is correct as adjective “protruding” or “protruded”?

Is it possible to put a rectangle as background in the author section?

250 Floor Tower

What should you do if you miss a job interview (deliberately)?

How to explain what's wrong with this application of the chain rule?

What is this cable/device?

Creepy dinosaur pc game identification

How do you make your own symbol when Detexify fails?

Strong empirical falsification of quantum mechanics based on vacuum energy density

Why did the EU agree to delay the Brexit deadline?

Loading commands from file

Does a 'pending' US visa application constitute a denial?

copy and scale one figure (wheel)

Redundant comparison & "if" before assignment

What does routing an IP address mean?

How do I find all files that end with a dot

What is Cash Advance APR?

Offered money to buy a house, seller is asking for more to cover gap between their listing and mortgage owed

Is it possible to have a strip of cold climate in the middle of a planet?

How to implement a feedback to keep the DC gain at zero for this conceptual passive filter?

What if a revenant (monster) gains fire resistance?



Can not use `cut -c` (`--characters`) with UTF-8?



2019 Community Moderator ElectionA command to print only last 3 characters of a stringHow to do a regex search in a UTF-16LE file while in a UTF-8 locale?Some UTF-8 characters not being recognized by grep or sedProcess a file that starts with a BOM (FF FE)support for utf-8 encoding with lprConverting documents to text with UTF-8 encodingFile weird character encodingLMDE2 / MATE locale charset inconsistencyfold and text columnsprintf: multibyte charactersRemoving characters with sed










12















The command cut has an option -c to work on characters, instead of bytes with the option -b. But that does not seem to work, in en_US.UTF-8 locale:



The second byte gives the second ASCII character (which is encoded just the same in UTF-8):



$ printf 'ABC' | cut -b 2 
B


but does not give the second of three greek non-ASCII characters in UTF-8 locale:



$ printf 'αβγ' | cut -b 2 



That's alright - it's the second byte.

So we look at the second character instead:



$ printf 'αβγ' | cut -c 2 



That looks broken.

With some experiments, it turns out that the range 3-4 shows the second character:



$ printf 'αβγ' | cut -c 3-4
β


But that's just the same as the bytes 3 to 4:



$ printf 'αβγ' | cut -b 3-4
β


So the -c does not more than the -b for UTF-8.



I'd expect the locale setup is not right for UTF-8, but in comparison, wc works as expected;

It is often used to count bytes, with option -c (--bytes).
(Note the confusing option names.)



$ printf 'αβγ' | wc -c
6


But it can also count characters with option -m (--chars), which just works:



$ printf 'αβγ' | wc -m
3


So my configuration seems to be ok - but something is special about cut.



Maybe it does not support UTF-8 at all? But it does seem to support multi-byte characters, otherwise it would not need to support -b and -c.



So, what's wrong? And why?






The locale setup looks right for utf8, as far as I can tell:



$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


The input, byte by byte:



$ printf 'αβγ' | hd 
00000000 ce b1 ce b2 ce b3 |......|
00000006









share|improve this question






















  • Interesting! It looks like -c is using the same code as -b. Did you have a look at the source code? Maybe you can find a hint what -c is actually meant for.

    – michas
    Oct 23 '14 at 6:11















12















The command cut has an option -c to work on characters, instead of bytes with the option -b. But that does not seem to work, in en_US.UTF-8 locale:



The second byte gives the second ASCII character (which is encoded just the same in UTF-8):



$ printf 'ABC' | cut -b 2 
B


but does not give the second of three greek non-ASCII characters in UTF-8 locale:



$ printf 'αβγ' | cut -b 2 



That's alright - it's the second byte.

So we look at the second character instead:



$ printf 'αβγ' | cut -c 2 



That looks broken.

With some experiments, it turns out that the range 3-4 shows the second character:



$ printf 'αβγ' | cut -c 3-4
β


But that's just the same as the bytes 3 to 4:



$ printf 'αβγ' | cut -b 3-4
β


So the -c does not more than the -b for UTF-8.



I'd expect the locale setup is not right for UTF-8, but in comparison, wc works as expected;

It is often used to count bytes, with option -c (--bytes).
(Note the confusing option names.)



$ printf 'αβγ' | wc -c
6


But it can also count characters with option -m (--chars), which just works:



$ printf 'αβγ' | wc -m
3


So my configuration seems to be ok - but something is special about cut.



Maybe it does not support UTF-8 at all? But it does seem to support multi-byte characters, otherwise it would not need to support -b and -c.



So, what's wrong? And why?






The locale setup looks right for utf8, as far as I can tell:



$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


The input, byte by byte:



$ printf 'αβγ' | hd 
00000000 ce b1 ce b2 ce b3 |......|
00000006









share|improve this question






















  • Interesting! It looks like -c is using the same code as -b. Did you have a look at the source code? Maybe you can find a hint what -c is actually meant for.

    – michas
    Oct 23 '14 at 6:11













12












12








12


2






The command cut has an option -c to work on characters, instead of bytes with the option -b. But that does not seem to work, in en_US.UTF-8 locale:



The second byte gives the second ASCII character (which is encoded just the same in UTF-8):



$ printf 'ABC' | cut -b 2 
B


but does not give the second of three greek non-ASCII characters in UTF-8 locale:



$ printf 'αβγ' | cut -b 2 



That's alright - it's the second byte.

So we look at the second character instead:



$ printf 'αβγ' | cut -c 2 



That looks broken.

With some experiments, it turns out that the range 3-4 shows the second character:



$ printf 'αβγ' | cut -c 3-4
β


But that's just the same as the bytes 3 to 4:



$ printf 'αβγ' | cut -b 3-4
β


So the -c does not more than the -b for UTF-8.



I'd expect the locale setup is not right for UTF-8, but in comparison, wc works as expected;

It is often used to count bytes, with option -c (--bytes).
(Note the confusing option names.)



$ printf 'αβγ' | wc -c
6


But it can also count characters with option -m (--chars), which just works:



$ printf 'αβγ' | wc -m
3


So my configuration seems to be ok - but something is special about cut.



Maybe it does not support UTF-8 at all? But it does seem to support multi-byte characters, otherwise it would not need to support -b and -c.



So, what's wrong? And why?






The locale setup looks right for utf8, as far as I can tell:



$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


The input, byte by byte:



$ printf 'αβγ' | hd 
00000000 ce b1 ce b2 ce b3 |......|
00000006









share|improve this question














The command cut has an option -c to work on characters, instead of bytes with the option -b. But that does not seem to work, in en_US.UTF-8 locale:



The second byte gives the second ASCII character (which is encoded just the same in UTF-8):



$ printf 'ABC' | cut -b 2 
B


but does not give the second of three greek non-ASCII characters in UTF-8 locale:



$ printf 'αβγ' | cut -b 2 



That's alright - it's the second byte.

So we look at the second character instead:



$ printf 'αβγ' | cut -c 2 



That looks broken.

With some experiments, it turns out that the range 3-4 shows the second character:



$ printf 'αβγ' | cut -c 3-4
β


But that's just the same as the bytes 3 to 4:



$ printf 'αβγ' | cut -b 3-4
β


So the -c does not more than the -b for UTF-8.



I'd expect the locale setup is not right for UTF-8, but in comparison, wc works as expected;

It is often used to count bytes, with option -c (--bytes).
(Note the confusing option names.)



$ printf 'αβγ' | wc -c
6


But it can also count characters with option -m (--chars), which just works:



$ printf 'αβγ' | wc -m
3


So my configuration seems to be ok - but something is special about cut.



Maybe it does not support UTF-8 at all? But it does seem to support multi-byte characters, otherwise it would not need to support -b and -c.



So, what's wrong? And why?






The locale setup looks right for utf8, as far as I can tell:



$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


The input, byte by byte:



$ printf 'αβγ' | hd 
00000000 ce b1 ce b2 ce b3 |......|
00000006






text-processing character-encoding unicode cut






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 23 '14 at 5:56









Volker SiegelVolker Siegel

11.1k33261




11.1k33261












  • Interesting! It looks like -c is using the same code as -b. Did you have a look at the source code? Maybe you can find a hint what -c is actually meant for.

    – michas
    Oct 23 '14 at 6:11

















  • Interesting! It looks like -c is using the same code as -b. Did you have a look at the source code? Maybe you can find a hint what -c is actually meant for.

    – michas
    Oct 23 '14 at 6:11
















Interesting! It looks like -c is using the same code as -b. Did you have a look at the source code? Maybe you can find a hint what -c is actually meant for.

– michas
Oct 23 '14 at 6:11





Interesting! It looks like -c is using the same code as -b. Did you have a look at the source code? Maybe you can find a hint what -c is actually meant for.

– michas
Oct 23 '14 at 6:11










3 Answers
3






active

oldest

votes


















10














You haven't said which cut you're using, but since you've mentioned the GNU long option --characters I'll assume it's that one. In that case, note this passage from info coreutils 'cut invocation':




‘-c character-list’
‘--characters=character-list’


Select for printing only the characters in positions listed in character-list. The same as -b for now, but internationalization will change that.




(emphasis added)



For the moment, GNU cut always works in terms of single-byte "characters", so the behaviour you see is expected.




Supporting both the -b and -c options is required by POSIX — they weren't added to GNU cut because it had multi-byte support and they worked properly, but to avoid giving errors on POSIX-compliant input. The same -c has been done in some other cut implementations, although not FreeBSD's and OS X's at least.



This is the historic behaviour of -c. -b was newly added to take over the byte role so that -c can work with multi-byte characters. Maybe in a few years it will work as desired consistently, although progress hasn't exactly been quick (it's been over a decade already). GNU cut doesn't even implement the -n option yet, even though it is orthogonal and intended to help the transition. There are potential compatibility problems with old scripts, which may be a concern, although I don't know definitively what the reason is.






share|improve this answer




















  • 1





    good work. youll find the same kind of comments in GNU's tr docs as well. and even tar unless i misremember. i guess its a big project.

    – mikeserv
    Oct 23 '14 at 8:42











  • Is there any workaround for unicode probelm in cut? For example, where is it possible to download the sources for patched cut? Or would it be more easier to use another utility? (grep solution below does not work smoothly with ranges e.g. 5-8,44-49)

    – dma_k
    Jan 31 '18 at 0:11











  • see this 2017 article, sub-titled ”Random notes and pointers regarding the on-going effort to add multibyte and unicode support in GNU Coreutils“: crashcourse.housegordon.org/coreutils-multibyte-support.html

    – myrdd
    Dec 12 '18 at 14:29












  • you can find some alternatives to cut -c here: superuser.com/questions/506164/…

    – myrdd
    Dec 12 '18 at 14:32


















2














Since many grep implementations are multibyte-aware, you can also use grep -o to simulate some uses of cut -c.



$ echo Τηεοδ29 | grep -o '^..'
Τη
$ echo Τηεοδ29 | egrep -o '^..' | grep -o '.$'
η


Adjust the number of periods to simulate cut ranges.






share|improve this answer
































    1














    colrm (part of util-linux, should be already installed on most distributions) seems to handle internationalization much better :



    $ echo 'αβγ' | colrm 3
    αβ
    $ echo 'αβγ' | colrm 2
    α


    Beware of the numbering : colrm N will remove columns from N, printing characters up to N-1.



    (credits)






    share|improve this answer






















      Your Answer








      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "106"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader:
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      ,
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f163721%2fcan-not-use-cut-c-characters-with-utf-8%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      10














      You haven't said which cut you're using, but since you've mentioned the GNU long option --characters I'll assume it's that one. In that case, note this passage from info coreutils 'cut invocation':




      ‘-c character-list’
      ‘--characters=character-list’


      Select for printing only the characters in positions listed in character-list. The same as -b for now, but internationalization will change that.




      (emphasis added)



      For the moment, GNU cut always works in terms of single-byte "characters", so the behaviour you see is expected.




      Supporting both the -b and -c options is required by POSIX — they weren't added to GNU cut because it had multi-byte support and they worked properly, but to avoid giving errors on POSIX-compliant input. The same -c has been done in some other cut implementations, although not FreeBSD's and OS X's at least.



      This is the historic behaviour of -c. -b was newly added to take over the byte role so that -c can work with multi-byte characters. Maybe in a few years it will work as desired consistently, although progress hasn't exactly been quick (it's been over a decade already). GNU cut doesn't even implement the -n option yet, even though it is orthogonal and intended to help the transition. There are potential compatibility problems with old scripts, which may be a concern, although I don't know definitively what the reason is.






      share|improve this answer




















      • 1





        good work. youll find the same kind of comments in GNU's tr docs as well. and even tar unless i misremember. i guess its a big project.

        – mikeserv
        Oct 23 '14 at 8:42











      • Is there any workaround for unicode probelm in cut? For example, where is it possible to download the sources for patched cut? Or would it be more easier to use another utility? (grep solution below does not work smoothly with ranges e.g. 5-8,44-49)

        – dma_k
        Jan 31 '18 at 0:11











      • see this 2017 article, sub-titled ”Random notes and pointers regarding the on-going effort to add multibyte and unicode support in GNU Coreutils“: crashcourse.housegordon.org/coreutils-multibyte-support.html

        – myrdd
        Dec 12 '18 at 14:29












      • you can find some alternatives to cut -c here: superuser.com/questions/506164/…

        – myrdd
        Dec 12 '18 at 14:32















      10














      You haven't said which cut you're using, but since you've mentioned the GNU long option --characters I'll assume it's that one. In that case, note this passage from info coreutils 'cut invocation':




      ‘-c character-list’
      ‘--characters=character-list’


      Select for printing only the characters in positions listed in character-list. The same as -b for now, but internationalization will change that.




      (emphasis added)



      For the moment, GNU cut always works in terms of single-byte "characters", so the behaviour you see is expected.




      Supporting both the -b and -c options is required by POSIX — they weren't added to GNU cut because it had multi-byte support and they worked properly, but to avoid giving errors on POSIX-compliant input. The same -c has been done in some other cut implementations, although not FreeBSD's and OS X's at least.



      This is the historic behaviour of -c. -b was newly added to take over the byte role so that -c can work with multi-byte characters. Maybe in a few years it will work as desired consistently, although progress hasn't exactly been quick (it's been over a decade already). GNU cut doesn't even implement the -n option yet, even though it is orthogonal and intended to help the transition. There are potential compatibility problems with old scripts, which may be a concern, although I don't know definitively what the reason is.






      share|improve this answer




















      • 1





        good work. youll find the same kind of comments in GNU's tr docs as well. and even tar unless i misremember. i guess its a big project.

        – mikeserv
        Oct 23 '14 at 8:42











      • Is there any workaround for unicode probelm in cut? For example, where is it possible to download the sources for patched cut? Or would it be more easier to use another utility? (grep solution below does not work smoothly with ranges e.g. 5-8,44-49)

        – dma_k
        Jan 31 '18 at 0:11











      • see this 2017 article, sub-titled ”Random notes and pointers regarding the on-going effort to add multibyte and unicode support in GNU Coreutils“: crashcourse.housegordon.org/coreutils-multibyte-support.html

        – myrdd
        Dec 12 '18 at 14:29












      • you can find some alternatives to cut -c here: superuser.com/questions/506164/…

        – myrdd
        Dec 12 '18 at 14:32













      10












      10








      10







      You haven't said which cut you're using, but since you've mentioned the GNU long option --characters I'll assume it's that one. In that case, note this passage from info coreutils 'cut invocation':




      ‘-c character-list’
      ‘--characters=character-list’


      Select for printing only the characters in positions listed in character-list. The same as -b for now, but internationalization will change that.




      (emphasis added)



      For the moment, GNU cut always works in terms of single-byte "characters", so the behaviour you see is expected.




      Supporting both the -b and -c options is required by POSIX — they weren't added to GNU cut because it had multi-byte support and they worked properly, but to avoid giving errors on POSIX-compliant input. The same -c has been done in some other cut implementations, although not FreeBSD's and OS X's at least.



      This is the historic behaviour of -c. -b was newly added to take over the byte role so that -c can work with multi-byte characters. Maybe in a few years it will work as desired consistently, although progress hasn't exactly been quick (it's been over a decade already). GNU cut doesn't even implement the -n option yet, even though it is orthogonal and intended to help the transition. There are potential compatibility problems with old scripts, which may be a concern, although I don't know definitively what the reason is.






      share|improve this answer















      You haven't said which cut you're using, but since you've mentioned the GNU long option --characters I'll assume it's that one. In that case, note this passage from info coreutils 'cut invocation':




      ‘-c character-list’
      ‘--characters=character-list’


      Select for printing only the characters in positions listed in character-list. The same as -b for now, but internationalization will change that.




      (emphasis added)



      For the moment, GNU cut always works in terms of single-byte "characters", so the behaviour you see is expected.




      Supporting both the -b and -c options is required by POSIX — they weren't added to GNU cut because it had multi-byte support and they worked properly, but to avoid giving errors on POSIX-compliant input. The same -c has been done in some other cut implementations, although not FreeBSD's and OS X's at least.



      This is the historic behaviour of -c. -b was newly added to take over the byte role so that -c can work with multi-byte characters. Maybe in a few years it will work as desired consistently, although progress hasn't exactly been quick (it's been over a decade already). GNU cut doesn't even implement the -n option yet, even though it is orthogonal and intended to help the transition. There are potential compatibility problems with old scripts, which may be a concern, although I don't know definitively what the reason is.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Oct 23 '14 at 6:28

























      answered Oct 23 '14 at 6:16









      Michael HomerMichael Homer

      50.2k8138176




      50.2k8138176







      • 1





        good work. youll find the same kind of comments in GNU's tr docs as well. and even tar unless i misremember. i guess its a big project.

        – mikeserv
        Oct 23 '14 at 8:42











      • Is there any workaround for unicode probelm in cut? For example, where is it possible to download the sources for patched cut? Or would it be more easier to use another utility? (grep solution below does not work smoothly with ranges e.g. 5-8,44-49)

        – dma_k
        Jan 31 '18 at 0:11











      • see this 2017 article, sub-titled ”Random notes and pointers regarding the on-going effort to add multibyte and unicode support in GNU Coreutils“: crashcourse.housegordon.org/coreutils-multibyte-support.html

        – myrdd
        Dec 12 '18 at 14:29












      • you can find some alternatives to cut -c here: superuser.com/questions/506164/…

        – myrdd
        Dec 12 '18 at 14:32












      • 1





        good work. youll find the same kind of comments in GNU's tr docs as well. and even tar unless i misremember. i guess its a big project.

        – mikeserv
        Oct 23 '14 at 8:42











      • Is there any workaround for unicode probelm in cut? For example, where is it possible to download the sources for patched cut? Or would it be more easier to use another utility? (grep solution below does not work smoothly with ranges e.g. 5-8,44-49)

        – dma_k
        Jan 31 '18 at 0:11











      • see this 2017 article, sub-titled ”Random notes and pointers regarding the on-going effort to add multibyte and unicode support in GNU Coreutils“: crashcourse.housegordon.org/coreutils-multibyte-support.html

        – myrdd
        Dec 12 '18 at 14:29












      • you can find some alternatives to cut -c here: superuser.com/questions/506164/…

        – myrdd
        Dec 12 '18 at 14:32







      1




      1





      good work. youll find the same kind of comments in GNU's tr docs as well. and even tar unless i misremember. i guess its a big project.

      – mikeserv
      Oct 23 '14 at 8:42





      good work. youll find the same kind of comments in GNU's tr docs as well. and even tar unless i misremember. i guess its a big project.

      – mikeserv
      Oct 23 '14 at 8:42













      Is there any workaround for unicode probelm in cut? For example, where is it possible to download the sources for patched cut? Or would it be more easier to use another utility? (grep solution below does not work smoothly with ranges e.g. 5-8,44-49)

      – dma_k
      Jan 31 '18 at 0:11





      Is there any workaround for unicode probelm in cut? For example, where is it possible to download the sources for patched cut? Or would it be more easier to use another utility? (grep solution below does not work smoothly with ranges e.g. 5-8,44-49)

      – dma_k
      Jan 31 '18 at 0:11













      see this 2017 article, sub-titled ”Random notes and pointers regarding the on-going effort to add multibyte and unicode support in GNU Coreutils“: crashcourse.housegordon.org/coreutils-multibyte-support.html

      – myrdd
      Dec 12 '18 at 14:29






      see this 2017 article, sub-titled ”Random notes and pointers regarding the on-going effort to add multibyte and unicode support in GNU Coreutils“: crashcourse.housegordon.org/coreutils-multibyte-support.html

      – myrdd
      Dec 12 '18 at 14:29














      you can find some alternatives to cut -c here: superuser.com/questions/506164/…

      – myrdd
      Dec 12 '18 at 14:32





      you can find some alternatives to cut -c here: superuser.com/questions/506164/…

      – myrdd
      Dec 12 '18 at 14:32













      2














      Since many grep implementations are multibyte-aware, you can also use grep -o to simulate some uses of cut -c.



      $ echo Τηεοδ29 | grep -o '^..'
      Τη
      $ echo Τηεοδ29 | egrep -o '^..' | grep -o '.$'
      η


      Adjust the number of periods to simulate cut ranges.






      share|improve this answer





























        2














        Since many grep implementations are multibyte-aware, you can also use grep -o to simulate some uses of cut -c.



        $ echo Τηεοδ29 | grep -o '^..'
        Τη
        $ echo Τηεοδ29 | egrep -o '^..' | grep -o '.$'
        η


        Adjust the number of periods to simulate cut ranges.






        share|improve this answer



























          2












          2








          2







          Since many grep implementations are multibyte-aware, you can also use grep -o to simulate some uses of cut -c.



          $ echo Τηεοδ29 | grep -o '^..'
          Τη
          $ echo Τηεοδ29 | egrep -o '^..' | grep -o '.$'
          η


          Adjust the number of periods to simulate cut ranges.






          share|improve this answer















          Since many grep implementations are multibyte-aware, you can also use grep -o to simulate some uses of cut -c.



          $ echo Τηεοδ29 | grep -o '^..'
          Τη
          $ echo Τηεοδ29 | egrep -o '^..' | grep -o '.$'
          η


          Adjust the number of periods to simulate cut ranges.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Aug 20 '16 at 14:57

























          answered Aug 20 '16 at 14:48









          Royce WilliamsRoyce Williams

          735618




          735618





















              1














              colrm (part of util-linux, should be already installed on most distributions) seems to handle internationalization much better :



              $ echo 'αβγ' | colrm 3
              αβ
              $ echo 'αβγ' | colrm 2
              α


              Beware of the numbering : colrm N will remove columns from N, printing characters up to N-1.



              (credits)






              share|improve this answer



























                1














                colrm (part of util-linux, should be already installed on most distributions) seems to handle internationalization much better :



                $ echo 'αβγ' | colrm 3
                αβ
                $ echo 'αβγ' | colrm 2
                α


                Beware of the numbering : colrm N will remove columns from N, printing characters up to N-1.



                (credits)






                share|improve this answer

























                  1












                  1








                  1







                  colrm (part of util-linux, should be already installed on most distributions) seems to handle internationalization much better :



                  $ echo 'αβγ' | colrm 3
                  αβ
                  $ echo 'αβγ' | colrm 2
                  α


                  Beware of the numbering : colrm N will remove columns from N, printing characters up to N-1.



                  (credits)






                  share|improve this answer













                  colrm (part of util-linux, should be already installed on most distributions) seems to handle internationalization much better :



                  $ echo 'αβγ' | colrm 3
                  αβ
                  $ echo 'αβγ' | colrm 2
                  α


                  Beware of the numbering : colrm N will remove columns from N, printing characters up to N-1.



                  (credits)







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered yesterday









                  Skippy le Grand GourouSkippy le Grand Gourou

                  1,1121122




                  1,1121122



























                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f163721%2fcan-not-use-cut-c-characters-with-utf-8%23new-answer', 'question_page');

                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      getting Checkpoint VPN SSL Network Extender working in the command lineHow to connect to CheckPoint VPN on Ubuntu 18.04LTS?Will the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayVPN SSL Network Extender in FirefoxLinux Checkpoint SNX tool configuration issuesCheck Point - Connect under Linux - snx + OTPSNX VPN Ububuntu 18.XXUsing Checkpoint VPN SSL Network Extender CLI with certificateVPN with network manager (nm-applet) is not workingWill the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayImport VPN config files to NetworkManager from command lineTrouble connecting to VPN using network-manager, while command line worksStart a VPN connection with PPTP protocol on command linestarting a docker service daemon breaks the vpn networkCan't connect to vpn with Network-managerVPN SSL Network Extender in FirefoxUsing Checkpoint VPN SSL Network Extender CLI with certificate

                      대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495

                      Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition