I tried doing a simple commit through my wrapper library for Mercurial, using the simple text of Unicode:æøåÆØÅ
as my commit message. This is written to a text file and given to Mercurial with the appropriate parameter:
hg commit --logfile FILE
If I subsequently look at the repository with TortoiseHg, the characters are reproduced correctly. On the Console, they are mangled:
[C:\Temp] :hg log changeset: 0:6a0911410128 tag: tip user: Lasse V. Karlsen date: Wed Dec 01 21:48:54 2010 +0100 summary: Unicode:æøåÆØÅ
If I redirect the output of hg log
to a file, and open it up, æøåÆØÅ
is reproduced correctly.
So, my question is this:
- Can I ask
hg
to write the log to a file directly, or do I have to redirect standard output? - Will this cause problems with python encoding for console, ie. some characters will make
hg
crash instead of just mangling the output? - Is there a known supported encoding for the commit messages that I should adhere to?
Or is it just this simple:
- Mercurial doesn't care, it takes the contents of the file I give it, whatever the content, and stores that as the commit message. When producing the log, it will just dump it back to the console falling prey to whatever limitations the Python console output library has in this regard?
C:\Temp
). @Lasse: what console are you using? (Your prompt isn't the default Command Prompt prompt.) – Eurhythmics