Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Unable to enter and display accented characters with Cloudron CLI

Unable to enter and display accented characters with Cloudron CLI

Scheduled Pinned Locked Moved Solved Support
cli
8 Posts 3 Posters 1.2k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • jeauJ Offline
    jeauJ Offline
    jeau
    App Dev
    wrote on last edited by girish
    #1

    I used to attribute this problem to the lack of locales in the LAMP application. They are there now.

    Accented characters are not displayed in terminal mode and I get weird characters when I edit with vim. If the accented letters are present in the file, they are displayed but as soon as I touch them it's a mess.

    In fact I think the problem is not related to the application but comes from the connection via Cloudron CLI (I use OSX).

    In ssh directly, on the same server, I don't have this problem.

    But maybe I'm wrong

    1 Reply Last reply
    0
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      Seems to work for me on linux atleast. Maybe a node.js issue on OS X? I tried all sorts of characters.

      679f3795-194a-464b-9845-ecec4951e624-image.png

      Is there an issue in the Web Terminal or just the CLI ?

      jeauJ 1 Reply Last reply
      0
      • girishG girish

        Seems to work for me on linux atleast. Maybe a node.js issue on OS X? I tried all sorts of characters.

        679f3795-194a-464b-9845-ecec4951e624-image.png

        Is there an issue in the Web Terminal or just the CLI ?

        jeauJ Offline
        jeauJ Offline
        jeau
        App Dev
        wrote on last edited by
        #3

        @girish I can do your test with cat and it works fine, but I can't enter directly any accented characters.

        Same issue with Web Terminal.
        I tested with OSX and with Linux (Debian).

        1 Reply Last reply
        0
        • girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #4

          Ah ok, I only copy/pasted the accented characters and did not type it myself. I have no clue how to do that, so maybe someone else can test this out as well.

          1 Reply Last reply
          0
          • nebulonN Away
            nebulonN Away
            nebulon
            Staff
            wrote on last edited by
            #5

            I can reproduce at least one issue, simply trying to type German umlauts already has an issue.

            nebulonN 1 Reply Last reply
            1
            • nebulonN nebulon

              I can reproduce at least one issue, simply trying to type German umlauts already has an issue.

              nebulonN Away
              nebulonN Away
              nebulon
              Staff
              wrote on last edited by
              #6

              So this happens because we set the tty to be in raw mode https://nodejs.org/api/tty.html#readstreamsetrawmodemode

              nebulonN 1 Reply Last reply
              2
              • nebulonN nebulon

                So this happens because we set the tty to be in raw mode https://nodejs.org/api/tty.html#readstreamsetrawmodemode

                nebulonN Away
                nebulonN Away
                nebulon
                Staff
                wrote on last edited by
                #7

                Turns out this has to do with the currently unset LANG environment variable. We have pushed a fix for the next patch release. Since we are not 100% aware of potential side-effects for other parts, which utilize docker's exec the cli and webterminal only will set this to a fixed C.UTF-8 value for the moment.

                jeauJ 1 Reply Last reply
                2
                • nebulonN nebulon marked this topic as a question on
                • nebulonN nebulon has marked this topic as solved on
                • nebulonN nebulon

                  Turns out this has to do with the currently unset LANG environment variable. We have pushed a fix for the next patch release. Since we are not 100% aware of potential side-effects for other parts, which utilize docker's exec the cli and webterminal only will set this to a fixed C.UTF-8 value for the moment.

                  jeauJ Offline
                  jeauJ Offline
                  jeau
                  App Dev
                  wrote on last edited by
                  #8

                  @nebulon thanks

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Bookmarks
                  • Search