Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEGREE SIGN character in projinfo output is incorrectly displayed on MS Windows console #1828

Closed
agiudiceandrea opened this issue Jan 7, 2020 · 2 comments
Milestone

Comments

@agiudiceandrea
Copy link

@agiudiceandrea agiudiceandrea commented Jan 7, 2020

On MS Windows 7 64 bit localized in Italian, the output of projinfo (6.2.1) tool can contain the DEGREE SIGN character (U+00B0 | ° | \xc2\xb0) that is incorrectly displayed in the command prompt console, e.g. the OSGeo4W Shell:

image

The default console codepage is 850 | ibm850 | OEM Multilingual Latin 1; Western European (DOS)

Is it possible to properly encode/decode the DEGREE SIGN character in the string "Operation n°" or to avoid the use of such character (e.g. using "Operation n.")?
I would also add a space at the end of the string to separate it from the number that follows.

The problem also occurs changing the codepage to 65001 | utf-8 | Unicode (UTF-8) when the font used in the shell is non TrueType (the default font is Raster type).

PROJ/src/apps/projinfo.cpp

Lines 689 to 692 in 529eb50

std::cout << "Operation n"
"\xC2\xB0"
<< (i + 1) << ":" << std::endl
<< std::endl;

@mwtoews
Copy link
Member

@mwtoews mwtoews commented Jan 7, 2020

There are many ways to represent this symbol, see https://en.wikipedia.org/wiki/Numero_sign

Normally in English, it's just the two ASCII characters, with an optional fullstop: No.

@kbevers
Copy link
Member

@kbevers kbevers commented Jan 7, 2020

Going with a plain ASCII representation like "No." would be the simplest fix to this. I have been annoyed by this as well when using projinfo on Windows.

rouault added a commit that referenced this issue Jan 7, 2020
projinfo: use No. abbreviation instead of UTF-8 character (fixes #1828)
@kbevers kbevers added this to the 7.0.0 milestone Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants