[SOLVED] UTF8Encode(String(Chr(i)))

[WickedDum]

Huh???   

This code doesn't work.  The upper 128 are continuously displayed in boxes.  I even added LazUTF8 to the Uses section.  There was no difference exhibited.

Is it FPC?  Lazarus?  Or, probably, me?

Code: Pascal  [Select][+][-]

1.    for i := 0 to 255 do
2.    { To display the 'extended' characters in Lazarus you will need explicitly to
3.    convert the char to UTF8. }
4.      ListBox1.Items.Add( 'Ascii ' + IntToStr(i) + ' = ' + UTF8Encode(String(Chr(i)))  );
5.  

I have read more than several articles on ASCII, EBCDIC, UNICODE, UTF8, UTF16, etc.  I have not found a resolution nor an avenue to pursue.

All suggestions/comments accepted!  Thanks!!

[lainz]

Code: Pascal  [Select][+][-]

1. implementation
2. uses
3.   LazUTF8;
4.  
5. {$R *.lfm}
6.  
7. { TForm1 }
8.  
9. procedure TForm1.FormCreate(Sender: TObject);
10. var
11.   i: integer;
12. begin
13.   for i:=0 to 255 do
14.     ListBox1.Items.Add(UnicodeToUTF8(i));
15. end;

[Phil]

What codepage do you assume the upper chars are from?

If Latin-1, try using the LConvEncoding unit's CP1252ToUTF8 function instead of UTF8Encode.

[WickedDum]

Thanks!

lainz:  It still does not display 127 to 160.  Any thoughts as to why?  Or, how to get the full display?

Phil:  I have no idea what the codepage is.  How do figure it out? 

Looking forward to hearing from you both again!!  And, anyone else?

Thanks!

[JuhaManninen]

What are your 'extended' characters? What exactly are you trying to do?

[wp]

I have no idea what the codepage is.  How do figure it out?

Read this: https://en.wikipedia.org/wiki/Windows_code_page.

I assume that your are on Windows. Then the function WinCPToUTF8() (in unit LazUTF8) converts a characters from the codepage used by your current Windows settings to UTF8 used by Lazarus:

Code: Pascal  [Select][+][-]

1. uses
2.   LazUTF8;
3.  
4. { TForm1 }
5.  
6. procedure TForm1.FormCreate(Sender: TObject);
7. var
8.   i: Integer;
9. begin
10.   for i := 0 to 255 do
11.     ListBox1.Items.Add('Ascii ' + IntToStr(i) + ' = ' + WinCPToUTF8(String(Chr(i)))  );
12. end;

[Josh]

Hi
If your displaying this on a form etc; does the font you are using have these characters defined?

[lainz]

lainz:  It still does not display 127 to 160.  Any thoughts as to why?  Or, how to get the full display?

In my Windows it displays all of them.

[WickedDum]

Thank you for all of your input!!  I haven't done so much research and studying since I left college!

What are your 'extended' characters? What exactly are you trying to do?

I am trying to display a complete list of the ASCII 255 characters.

I have no idea what the codepage is.  How do figure it out?

Read this: https://en.wikipedia.org/wiki/Windows_code_page.

Now that I know what a codepage is, how do I
1- determine the codepage that my version of Windows is using?
2- assign a specific codepage for a particular project?
And, do all (American) English Windows versions use 1252?

Hi.  If your displaying this on a form etc; does the font you are using have these characters defined?

I am using the standard Lazarus configuration.  I reviewed all of the configuration options and did not see where the font is set.  Where do I find the font setting?


A synopsis (for future reference):
UTF8Encode does not display all of characters.  128-on are boxes.  The 'normal' 0,1, 9, 10, 13, and 28-31 are not displayed.
UnicodeToUTF8  A large chunk (128-160) is missing, as well as the 'normal' 0,1, 9, 10, 13, and 28-31.
WinCPToUTF8 and CP1252ToUTF8, in addition to the 'normal' non-displayed characters, do not display 129, 141, 143-144, and 160.

Thank you all for your assistance!!!

[JuhaManninen]

I still didn't understand what your ultimate goal is with those extended ANSI characters.
You may be solving a problem that does not exist. If you don't even know what a codepage is then you probably don't need them. Just use Unicode everywhere. If some of your input/output really uses the codepages then convert data for reading/writing, otherwise use Unicode everywhere.
Everything becomes easier. No explicit conversion functions are needed.
You didn't mention you Lazarus version. Use the latest 1.6 + FPC 3.0.

UnicodeToUTF8  A large chunk (128-160) is missing, as well as the 'normal' 0,1, 9, 10, 13, and 28-31.

Did you check what those U+... codes are? Please learn Unicode, it is important now and in the future. We are finally getting rid of the horrors of old codepages.

[WickedDum]

JuhaManninen:  My ultimate goal is to display the character set.  That's all.  I am taking a refresher course and the lesson was a FOR loop - I know FOR loops...  The lesson FOR ME is continued familiarity of GUI coding.  (I haven't programmed since TP5.  )  The ListBox1.Items.Add(...) is something I have never done before.  And then I noticed the whole table wasn't being displayed.  To me, that is totally unsatisfactory.

Using Unicode everywhere would be great...but it didn't show me the most complete table.  Therefore, it is not the best solution.

My specifics are in my signature.  I am using the latest versions.

What do you mean by 'U+' codes?

And, could you assist with these questions, too:
Now that I know what a codepage is, how do I
1- determine the codepage that my version of Windows is using?
2- assign a specific codepage for a particular project?
And, do all (American) English Windows versions use 1252?

Thanks!

[lainz]

What it display? Log it into a memo and Copy to the clipboard. Then show us.

This is how need to look:
http://www.utf8-chartable.de/unicode-utf8-table.pl?unicodeinhtml=dec

This is how look in my PC, with the code I provided to you:

Code: Pascal  [Select][+][-]

1. 
   
2. 
3. 
4. 
5. 
6. 
7. 
8. 
9.        
10.  
11.  
12.  
13. 
14.  
15.  
16. 
17. 
18. 
19. 
20. 
21. 
22. 
23. 
24. 
25. 
26. 
27. 
28. 
29. 
30. 
31. 
32. 
33. 
34.  
35. !
36. "
37. #
38. $
39. %
40. &
41. '
42. (
43. )
44. *
45. +
46. ,
47. -
48. .
49. /
50. 0
51. 1
52. 2
53. 3
54. 4
55. 5
56. 6
57. 7
58. 8
59. 9
60. :
61. ;
62. <
63. =
64. >
65. ?
66. @
67. A
68. B
69. C
70. D
71. E
72. F
73. G
74. H
75. I
76. J
77. K
78. L
79. M
80. N
81. O
82. P
83. Q
84. R
85. S
86. T
87. U
88. V
89. W
90. X
91. Y
92. Z
93. [
94. \
95. ]
96. ^
97. _
98. `
99. a
100. b
101. c
102. d
103. e
104. f
105. g
106. h
107. i
108. j
109. k
110. l
111. m
112. n
113. o
114. p
115. q
116. r
117. s
118. t
119. u
120. v
121. w
122. x
123. y
124. z
125. {
126. |
127. }
128. ~
129. 
130. €
131. 
132. ‚
133. ƒ
134. „
135. …
136. †
137. ‡
138. ˆ
139. ‰
140. Š
141. ‹
142. Œ
143. 
144. Ž
145. 
146. 
147. ‘
148. ’
149. “
150. ”
151. •
152. –
153. —
154. ˜
155. ™
156. š
157. ›
158. œ
159. 
160. ž
161. Ÿ
162.  
163. ¡
164. ¢
165. £
166. ¤
167. ¥
168. ¦
169. §
170. ¨
171. ©
172. ª
173. «
174. ¬
175. ­
176. ®
177. ¯
178. °
179. ±
180. ²
181. ³
182. ´
183. µ
184. ¶
185. ·
186. ¸
187. ¹
188. º
189. »
190. ¼
191. ½
192. ¾
193. ¿
194. À
195. Á
196. Â
197. Ã
198. Ä
199. Å
200. Æ
201. Ç
202. È
203. É
204. Ê
205. Ë
206. Ì
207. Í
208. Î
209. Ï
210. Ð
211. Ñ
212. Ò
213. Ó
214. Ô
215. Õ
216. Ö
217. ×
218. Ø
219. Ù
220. Ú
221. Û
222. Ü
223. Ý
224. Þ
225. ß
226. à
227. á
228. â
229. ã
230. ä
231. å
232. æ
233. ç
234. è
235. é
236. ê
237. ë
238. ì
239. í
240. î
241. ï
242. ð
243. ñ
244. ò
245. ó
246. ô
247. õ
248. ö
249. ÷
250. ø
251. ù
252. ú
253. û
254. ü
255. ý
256. þ
257. ÿ
258.  

[JuhaManninen]

JuhaManninen:  My ultimate goal is to display the character set.

Mighty goal! There are well over 100000 characters in Unicode.
However a FOR loop practice can use any subset of them. For example:

Code: Pascal  [Select][+][-]

1. for i := $2100 to $2A00 do
2.   ListBox1.Items.Add(UnicodeToUTF8(i));

Using Unicode everywhere would be great...but it didn't show me the most complete table.  Therefore, it is not the best solution.

Well, you have a lot to learn...  As you can see here U+0080 .. U+00A0 (128-160) are not printable. They don't show.
 https://en.wikibooks.org/wiki/Unicode/Character_reference/0000-0FFF

What do you mean by 'U+' codes?

They are the Unicode definitions of codepoints, as opposed to encoded values of codepoints.
Learn more:
 https://en.wikipedia.org/wiki/Unicode

For the rest of your questions: Forget Windows codepages, use Unicode.

[WickedDum]

lainz:  If I knew how to log it into a memo, I would...    That's why I'm going through this course...

JuhaManninen:  As for FOR exercises, I don't have a problem with the constructs, just the displaying of the results.

Here is a sample of an ASCII chart.  This is all I am/was trying to achieve.

[lainz]

lainz:  If I knew how to log it into a memo, I would...    That's why I'm going through this course...

JuhaManninen:  As for FOR exercises, I don't have a problem with the constructs, just the displaying of the results.

Here is a sample of an ASCII chart.  This is all I am/was trying to achieve.

Loging on a memo is the same as this

Code: Pascal  [Select][+][-]

1. uses
2.   LazUTF8;
3.  
4. { TForm1 }
5.  
6. procedure TForm1.FormCreate(Sender: TObject);
7. var
8.   i: Integer;
9. begin
10.   for i := 0 to 255 do
11.     ListBox1.Items.Add('Ascii ' + IntToStr(i) + ' = ' + WinCPToUTF8(String(Chr(i)))  );
12. end;

But instead of putting a ListBox in the form you can put a Memo control and that's all, change ListBox1 by Memo1

Code: Pascal  [Select][+][-]

1. uses
2.   LazUTF8;
3.  
4. { TForm1 }
5.  
6. procedure TForm1.FormCreate(Sender: TObject);
7. var
8.   i: Integer;
9. begin
10.   for i := 0 to 255 do
11.     Memo1.Items.Add('Ascii ' + IntToStr(i) + ' = ' + WinCPToUTF8(String(Chr(i)))  );
12. end;

But as JuhaManninen said, you will get the same as I get, the characters you say are missing are control characters that are not visible, these don't have a glyph to render them on the screen.