Unicode support across consoles

[ocean314]

Hello. There is the problem with cirillyc unicode. How to solve it? Thanks!

[mariashinoto]

This seems to be a problem with jrnl saving text written in the terminal directly as ASCII.

I have the same problem with German and Japanese -- turns out to be garble.

Wish this could be fixed. For the time being, I work with an external editor, I took nano for convenience because it keeps the utf8 encoding intact.

[ocean314]

Right. Works with vim.

[maebert]

Which terminal / emulator and OS are you using, @ocean314?

[ocean314]

@maebert , It was Gnome Terminal under Fedora.

[ArneBachmann]

Set the console encoding to UTF-8, configure the .jrnl_config to UTF-8 and it should work, right?
Unter Windows, I was able to operate jrnl using UTF-8 by setting the code page to 65001

[gatezh]

@ArneBachmann how to configure .jrnl_config?

[ArneBachmann]

My bad, there is no need to configure the encoding in the .jrnl_config, just make sure that your console has the right encoding defined.

On the GitHub page the first link goes to the documentation. Under advanced usage it is explained how to configure the configuration file, and where it is stored.

On Windows you have to take further measures to make the console unicode aware (change to cp65001 in the registry), and then tweak Python to recognize the encoding (add 'cp65001': 'utf_8', to Lib/encoding/aliases.py).

Here is my config file:

{
  "journals": {
    "default": "D:\\Arne\\docs\\work\\information\\journal.txt"
  },
  "editor": "C:\\Program Files\\Sublime Text 3\\sublime_text.exe",
  "encrypt": false,
  "default_hour": 8,
  "default_minute": 0,
  "timeformat": "%Y%m%d-%H%M%S",
  "tagsymbols": "@",
  "highlight": true,
  "linewrap": false
}

I converted four years worth of tiddly wiki contents to jrnl (due to banning Firefox at my workplace) and had to make sure that the encoding of the journal.txt file is in UTF-8, but after that everything works together fine.

[wren]

@ArneBachmann Thank you for reporting back with your findings! We need to update the docs with your info.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.