gre-ilya/fltk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tearing my hairs out about terminology in utf-8

Browse Source 
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@7429 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
This commit is contained in:
Matthias Melcher 2010-04-05 12:55:14 +00:00
parent f2fa59fd0f
commit 769ebeeba7
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
FL/Fl_Text_Buffer.H
View File

@ -34,12 +34,15 @@
#define FL_TEXT_BUFFER_H
/*
UTF-8 terminology for this file:
Suggested UTF-8 terminology for this file:
"length" is the number of characters in a string
"size" is the number of bytes
"index" is the position in a string in number of characters
"offset" is the position in a strin in bytes (and must be kept on a charater boundary)
?? "length" is the number of characters in a string
?? "size" is the number of bytes
?? "index" is the position in a string in number of characters
?? "offset" is the position in a strin in bytes (and must be kept on a charater boundary)
(there seems to be no standard in Uncode documents, howevere "length" is commonly
referencing the number of bytes. Maybe "bytes" and "glyphs" would be the most
obvious way to describe sizes?)
"character size" is the size of a UTF-8 character in bytes
"character width" is the width of a Unicode character in pixels

1
test/editor.cxx
View File

@ -784,6 +784,7 @@ Fl_Window* new_view() {
int main(int argc, char **argv) {
textbuf = new Fl_Text_Buffer;
textbuf->text("Rügenwälder Ruß.");
style_init();
Fl_Window* window = new_view();