Changes between Initial Version and Version 10 of Ticket #18608


Ignore:
Timestamp:
2020-01-27T14:32:55+01:00 (6 years ago)
Author:
gaben
Comment:

Replying to stoecker:

So I assume output was broken before r10899 for standard Windows.

I just tested the behaviour in a virtual machine with

  • an official Windows 10 1909 x64 (Hungarian) ISO
  • with JDK 1.8.241 (x64) and JDK 11.0.6 (x64)
  • in PowerShell and cmd

and I can say this is a regression. It's broken since r10899.

Updated the steps.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #18608

    • Property Keywords windows console encoding added
    • Property Cc Don-vip added

  • Ticket #18608 – Description

    initial v10  
    11==== What steps will reproduce the problem?
    2 1. Use Windows, set lang to Hungarian (maybe you can skip this step)
    3 2. Set command line encoding from default to UTF-8 (maybe you can skip this step)
    4 3. Set JOSM language to Hungarian
    5 4. Start JOSM from command line (cmd or powershell, doesn't matter):
     21. Use Windows, set lang to Hungarian
     32. Set JOSM language to Hungarian
     43. Start JOSM from command line (cmd or powershell, doesn't matter):
    65`java -jar "josm-snapshot-15752.jar"`
    76
    … …  
    3029
    3130
     31==== Please provide any additional information below. Attach a screenshot if possible.
     32
    3233For example, the first entry is
    3334`2020-01-23 17:28:11.200 INFO: Naplˇzßsi szint: INFO (INFO, 800)`
    … …  
    3536`2020-01-23 17:28:11.200 INFO: Naplózási szint: INFO (INFO, 800)`
    3637
    37 Older JOSM versions work fine. I checked r10526 and it printed readable characters. If I remember correctly I switched the terminal encoding from Windows default to UTF-8 a while ago, but I'm not sure.
    38 
    39 
    40 ==== Please provide any additional information below. Attach a screenshot if possible.
     38Older JOSM versions work fine. I checked r10526 and it printed readable characters.
    4139
    4240{{{