With the last update to windows 10, the graphic ascii chart I've used for years as a quick reference is all fuzzy. Rather than try to fix the problem, I just made a quickie out of an old program to show an ascii chart in a toolwindow. Released to the public domain for all uses public and private.
All menus are in the right-click context menu. Maybe you can get some use out of it, even if it's only a laugh at my coding style :)
Fixed terminal font problem. Other minor changes
2/8/19 Fixed bug when using thin-black border
5/25/19 Added ability show image. I have often needed a way to show a frameless, resizable, topmost image, so I finally got around to adding the capability to the Ascii chart program. This version now also contains the show code pages code.
p.s. ** I've found it convenient to have the program in the context menu for the desktop. Just click on the desktop and select the program. One way to do this is to add the appropriate entries to the registry. Create a file name something.reg, and add the following lines-
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Directory\Background\shell\Ascii Chart]
[HKEY_CLASSES_ROOT\Directory\Background\shell\Ascii Chart\command]
@="F:\\Progs\\Ascii\\Ascii.exe" ( substitute in your path here!)
and run the file. Note you do this at your own risk, so don't screw it up!
5/26/19 added image types emf, wmf, and ico. fixed upper case problem with drag and drop. fixed help bug.
**Special note: This code requires uasm. Apologies.
Works fine, and there is nothing wrong with your coding style :t
I did like it, i think it's a good job. The style it's personal (at least when you work by your own and not in some team). Thanks for share. :icon14: :icon14:
Fixed terminal font auto switch to wrong font problem.
Removed superfluous push esi.
Fixed select fixed spacing font.
Other minor cleanup.
Quote from: jimg on June 18, 2017, 06:32:50 AM
Fixed terminal font auto switch to wrong font problem.
Removed superfluous push esi.
Fixed select fixed spacing font.
Other minor cleanup.
That's great, :icon14:
are you going to upload it?
I updated the one in the first post.
Hi,
Runs well with W2k and Win98.
Regards,
Steve N.
Quote from: jimg on June 18, 2017, 09:45:57 AM
I updated the one in the first post.
Problem with the vertical scrollbar hiding the a-z column persists (Win7-64). Four pixels extra would be enough:
inv CreateWindowEx, WS_EX_TOOLWINDOW or WS_EX_TOPMOST , soff("RichEdit20A"),soff("Ascii"),
WS_POPUP or WS_SIZEBOX or \
WS_VISIBLE or ES_MULTILINE or ES_NOHIDESEL or ES_WANTRETURN or\
ES_SAVESEL or WS_CLIPSIBLINGS or ES_READONLY or\
WS_HSCROLL or ES_AUTOHSCROLL or WS_VSCROLL or ES_AUTOVSCROLL,
0,0, 335, 60
4, 0, 0, hWin, NULL
Done. Thanks :)
Fixed very strange bug. When border was set to thin-black, upon restarting program, Windows does weird things. When CreateWindowEx creates a window with the style and exstyle to get a thin-black border, and then you move or resize the window it makes every other open app blink or redo their captions. The solution was to create a borderless window first, and then apply the desired border afterward using SetWindowLong for style and exstyle. This only seemed to affect the thin-black border, my favorite.
Note that this is the ASCII chart for code page 1252 (Windows Latin 1 ).
Historically, most people use to take as reference the OEM code page 437 and other ASCII charts which will be different after character 127 should explicitly mention what code page they refer to.
An even better approach is always mention to what code page the ASCII chart refers to.
Quote from: AW on March 05, 2019, 08:41:08 AM
Note that this ...
More simple, I thin
k. The program show code page setted in your machine. Just that 8)
Quote from: HSE on March 05, 2019, 09:25:51 PM
More simple, I thing. The program show code page setted in your machine. Just that 8)
On a console my machine shows 437. So, I have 2 code pages. ;)
Quote from: HSE on March 05, 2019, 09:25:51 PMThe program show code page setted in your machine. Just that 8)
There is more than one code page in your system. Check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage
Quote from: AW on March 05, 2019, 10:12:00 PM
On a console my machine shows 437. So, I have 2 code pages. ;)
:t Indeed I was thinking in "console output code page" (apparently by default "input console code page" is the same), but Jimg chart is using "system code page". In any case, usually you only access one code page.
Quote from: jj2007 on March 05, 2019, 10:22:02 PM
There is more than one code page in your system. Check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage
Yes JJ. They are "supported" code pages, not necessarily active code pages.
Quote from: HSE on March 05, 2019, 11:12:47 PM
:t Indeed I was thinking in "console output code page" (apparently by default "input console code page" is the same), but Jimg chart is using "system code page". In any case, usually you only access one code page.
I don't know about what you call "console output code page", "input console code page" and "system code page".
There are two groups of code pages in Windows systems: OEM and ANSI code pages (https://en.wikipedia.org/wiki/Windows_code_page). Why invent new names when we already have names?
Quote from: AW on March 05, 2019, 11:23:36 PM
There are two groups of code pages in Windows systems: OEM and ANSI code pages
That pages are used in different ways.
>chcp 437
Active code page: 437
>фысшшword ascii from keyboard ::)
Marketing people would say that all code pages cater to the same market. :biggrin:
I wrote some Portuguese text in Notepad++ ("Anões e cães é um caso ímpar disse o júri."), saved it with code page 860, then I went to the console:
>chcp 860
Active code page: 860
>type lol.txt
Anões e cães é um caso ímpar disse o júri.
>chcp 1252
Active code page: 1252
>type lol.txt
An"es e c,,es , um caso ¡mpar disse o j£ri.
>chcp 437
Active code page: 437
>type lol.txt
Anöes e cäes é um caso ímpar disse o júri.
Quote from: jj2007 on March 05, 2019, 10:22:02 PM
Quote from: HSE on March 05, 2019, 09:25:51 PMThe program show code page setted in your machine. Just that 8)
There is more than one code page in your system. Check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage
I have 138, obtained with TCC (ex 4DOS):
10000 (MAC - Roman)
10001 (MAC - Japanese)
10002 (MAC - Traditional Chinese Big5)
10003 (MAC - Korean)
10004 (MAC - Arabic)
10005 (MAC - Hebrew)
10006 (MAC - Greek I)
10007 (MAC - Cyrillic)
10008 (MAC - Simplified Chinese GB 2312)
10010 (MAC - Romania)
10017 (MAC - Ukraine)
10021 (MAC - Thai)
10029 (MAC - Latin II)
10079 (MAC - Icelandic)
10081 (MAC - Turkish)
10082 (MAC - Croatia)
1026 (IBM EBCDIC - Turkish (Latin-5))
1047 (IBM EBCDIC - Latin-1/Open System)
1140 (IBM EBCDIC - U.S./Canada (37 + Euro))
1141 (IBM EBCDIC - Germany (20273 + Euro))
1142 (IBM EBCDIC - Denmark/Norway (20277 + Euro))
1143 (IBM EBCDIC - Finland/Sweden (20278 + Euro))
1144 (IBM EBCDIC - Italy (20280 + Euro))
1145 (IBM EBCDIC - Latin America/Spain (20284 + Euro))
1146 (IBM EBCDIC - United Kingdom (20285 + Euro))
1148 (IBM EBCDIC - International (500 + Euro))
1149 (IBM EBCDIC - Icelandic (20871 + Euro))
1250 (ANSI - Central Europe)
1251 (ANSI - Cyrillic)
1252 (ANSI - Latin I)
1253 (ANSI - Greek)
1254 (ANSI - Turkish)
1255 (ANSI - Hebrew)
1256 (ANSI - Arabic)
1257 (ANSI - Baltic)
1258 (ANSI/OEM - Viet Nam)
1361 (Korean - Johab)
20000 (CNS - Taiwan)
20001 (TCA - Taiwan)
20002 (Eten - Taiwan)
20003 (IBM5550 - Taiwan)
20004 (TeleText - Taiwan)
20005 (Wang - Taiwan)
20105 (IA5 IRV International Alphabet No.5)
20106 (IA5 German)
20107 (IA5 Swedish)
20108 (IA5 Norwegian)
20127 (US-ASCII)
20261 (T.61)
20269 (ISO 6937 Non-Spacing Accent)
20273 (IBM EBCDIC - Germany)
20277 (IBM EBCDIC - Denmark/Norway)
20278 (IBM EBCDIC - Finland/Sweden)
20280 (IBM EBCDIC - Italy)
20284 (IBM EBCDIC - Latin America/Spain)
20285 (IBM EBCDIC - United Kingdom)
20290 (IBM EBCDIC - Japanese Katakana Extended)
20297 (IBM EBCDIC - France)
20420 (IBM EBCDIC - Arabic)
20423 (IBM EBCDIC - Greek)
20424 (IBM EBCDIC - Hebrew)
20833 (IBM EBCDIC - Korean Extended)
20838 (IBM EBCDIC - Thai)
20866 (Russian - KOI8)
20871 (IBM EBCDIC - Icelandic)
20880 (IBM EBCDIC - Cyrillic (Russian))
20905 (IBM EBCDIC - Turkish)
20924 (IBM EBCDIC - Latin-1/Open System (1047 + Euro))
20932 (JIS X 0208-1990 & 0212-1990)
20936 (Simplified Chinese GB2312)
21025 (IBM EBCDIC - Cyrillic (Serbian, Bulgarian))
21027 (Ext Alpha Lowercase)
21866 (Ukrainian - KOI8-U)
28591 (ISO 8859-1 Latin I)
28592 (ISO 8859-2 Central Europe)
28593 (ISO 8859-3 Latin 3)
28594 (ISO 8859-4 Baltic)
28595 (ISO 8859-5 Cyrillic)
28596 (ISO 8859-6 Arabic)
28597 (ISO 8859-7 Greek)
28598 (ISO 8859-8 Hebrew: Visual Ordering)
28599 (ISO 8859-9 Latin 5)
28603 (ISO 8859-13 Latin 7)
28605 (ISO 8859-15 Latin 9)
37 (IBM EBCDIC - U.S./Canada)
38598 (ISO 8859-8 Hebrew: Logical Ordering)
437 (OEM - United States)
500 (IBM EBCDIC - International)
50220 (ISO-2022 Japanese with no halfwidth Katakana)
50221 (ISO-2022 Japanese with halfwidth Katakana)
50222 (ISO-2022 Japanese JIS X 0201-1989)
50225 (ISO-2022 Korean)
50227 (ISO-2022 Simplified Chinese)
50229 (ISO-2022 Traditional Chinese)
51949 (EUC-Korean)
52936 (HZ-GB2312 Simplified Chinese)
54936 (GB18030 Simplified Chinese)
55000 (SMS GSM 7bit)
55001 (SMS GSM 7bit Spanish)
55002 (SMS GSM 7bit Portuguese)
55003 (SMS GSM 7bit Turkish)
55004 (SMS GSM 7bit Greek)
57002 (ISCII - Devanagari)
57003 (ISCII - Bengali)
57004 (ISCII - Tamil)
57005 (ISCII - Telugu)
57006 (ISCII - Assamese)
57007 (ISCII - Odia (Oriya))
57008 (ISCII - Kannada)
57009 (ISCII - Malayalam)
57010 (ISCII - Gujarati)
57011 (ISCII - Punjabi (Gurmukhi))
708 (Arabic - ASMO)
720 (Arabic - Transparent ASMO)
737 (OEM - Greek 437G)
775 (OEM - Baltic)
850 (OEM - Multilingual Latin I)
852 (OEM - Latin II)
855 (OEM - Cyrillic)
857 (OEM - Turkish)
858 (OEM - Multilingual Latin I + Euro)
860 (OEM - Portuguese)
861 (OEM - Icelandic)
862 (OEM - Hebrew)
863 (OEM - Canadian French)
864 (OEM - Arabic)
865 (OEM - Nordic)
866 (OEM - Russian)
869 (OEM - Modern Greek)
870 (IBM EBCDIC - Multilingual/ROECE (Latin-2))
874 (ANSI/OEM - Thai)
875 (IBM EBCDIC - Modern Greek)
932 (ANSI/OEM - Japanese Shift-JIS)
936 (ANSI/OEM - Simplified Chinese GBK)
949 (ANSI/OEM - Korean)
950 (ANSI/OEM - Traditional Chinese Big5)
65000 (UTF-7)
65001 (UTF-8)
include \masm32\MasmBasic\MasmBasic.inc ; download (http://masm32.com/board/index.php?topic=94.0)
Init
GetRegArray "HKLM\SYSTEM\CurrentControlSet\Control\Nls\CodePage", MyCP$(), MyData$()
For_ each esi in MyCP$(): <PrintLine esi, Tb$, MyData$(ForNextCounter)>
Inkey Str$("%i entries found", MyCP$(?))
EndOfCode
...
20261 c_20261.nls
50229 c_is2022.dll
ACP 1252
OEMCP 850
MACCP 10000
137 entries found
Added quickie code pages dump. Unfortunately printing different code pages in a rich edit changes something I haven't found (unprintable characters 129, 141, 143, and 144 have incorrect widths) so next print of ascii table does not line up. The only way I found to fix it is to close the rich edit and make a new one, but I'm still looking.
If anyone knows any other way to print characters from multiple code pages at the same time, other than with a rich edit, please let me know.
edit:
combined with original in first post.
I have often needed a way to throw up a quick image to look at while working on another program. There are many programs out there to do that, but I wanted as little impact on the screen as possible, i.e. no title, no frame, just the image, made topmost. So I added the capability to my Ascii chart program for convenience. You can load any of the normal image types that gdiplus handles, (bmp, png, tif, gif, and jpg). The program also accepts drag and drop.
Download from the first post in this thread.
added image types .emf, .emf, and .ico
other minor bug fixes
Quote from: jimg on March 08, 2019, 11:40:59 AM
If anyone knows any other way to print characters from multiple code pages at the same time, other than with a rich edit, please let me know.
Codepages are a way to squeeze a subset of characters into a 'page' of 8-bit sized values; as you've found, they're not meant to be mixed.
If only there were some way to take all of the world's characters and put them into one giant 'page' -- of course, there is. Windows uses "wide-characters" which are 16-bits each (note: this is not the same as Unicode, though it's similar), instead of trying to squeeze them into 8-bits.
So, what you need to do is convert
from each codepage
into wide-chararacters, and only actually use wide-characters for everything (you'll also need to use the ...W versions of functions, where appropriate).
Luckily, the hard part is already done for you: MultiByteToWideChar (https://docs.microsoft.com/en-gb/windows/desktop/api/stringapiset/nf-stringapiset-multibytetowidechar)
Thanks Tedd :)