In release 4.12 a line is added to the support file which allows one to enter unicode characters such as the copyright symbol, thanks to Greg Walters and its use may be seen in the example code with his tutorial.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-04-01
can't support utf-8 in release 4.12 still
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-04-01
Execution output window cannot be consistent with the system output(sys.stdout.flush()).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I really don't understand your comment about the output window. What exactly is failing? What OS are you running on?
As to the other posting, exactly what utf-8 support are you looking for?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-04-02
On windows7. The page execution output window cannot be synchronous with ‘sys.stdout.flush()’ when I running the secondApp in tutorial. As for 'utf-8' , I wish use chinese in my example. Think you!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made a change for unicode support in the Python code in 4.13; did that help meet your needs?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-06-25
I don't know what changed. It "seems" that UTF-8 coding is happening today when I don't think it was just yesterday. It's clearly showing up in the generated file header when I don't recall seeing it before. It's causing errors. Is this something I can can be turned off?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-06-25
Could you send me a copy of the files? It would really help if you included the tcl file as well as the GUI file and the Support file. Could you describe the errors?
I have not changed anythingdealing with UTF-8 since 4.13.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-06-25
Corrections: The header text about using UTF-8 is in the _support.py file The generated file DOES run without error in PAGE.
* The errors thrown happen when trying to run the generated file in Eclipse and JetBrains Pycharm
Tried, but not sure all (5) files intended are attached: .tcl, _support.py, .py and two images of output from the IDEs. Please let me know if you don't recieve all the files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-06-25
Well, I must apologize. Reading the other posts more closely, it occured to me that the copyright symbol (a UTF-8 code) might be the culprit. Sure enough.... When I delete the copyright symbol the generated file runs in the IDEs. So it's a matter of compatiblity with the IDEs. Sorry for bother.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The jpg files are there but not the python files. You can be able to send them by clicking on "rozen" above and then "send message" or to "don dot rozenberg at gmail dot com".
The jpg files suggest that you are using an earlier version of PAGE rather than 4.14 which has generates a directive for uft-8.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "PAGE - Discussion"
seems it doesn't support unicode characters
I have never worked with unicode characters in Tcl. Would welcome suggestions.
In release 4.12 a line is added to the support file which allows one to enter unicode characters such as the copyright symbol, thanks to Greg Walters and its use may be seen in the example code with his tutorial.
can't support utf-8 in release 4.12 still
Execution output window cannot be consistent with the system output(sys.stdout.flush()).
I really don't understand your comment about the output window. What exactly is failing? What OS are you running on?
As to the other posting, exactly what utf-8 support are you looking for?
On windows7. The page execution output window cannot be synchronous with ‘sys.stdout.flush()’ when I running the secondApp in tutorial. As for 'utf-8' , I wish use chinese in my example. Think you!
I made a change for unicode support in the Python code in 4.13; did that help meet your needs?
I don't know what changed. It "seems" that UTF-8 coding is happening today when I don't think it was just yesterday. It's clearly showing up in the generated file header when I don't recall seeing it before. It's causing errors. Is this something I can can be turned off?
Could you send me a copy of the files? It would really help if you included the tcl file as well as the GUI file and the Support file. Could you describe the errors?
I have not changed anythingdealing with UTF-8 since 4.13.
Corrections:
The header text about using UTF-8 is in the _support.py file
The generated file DOES run without error in PAGE.
* The errors thrown happen when trying to run the generated file in Eclipse and JetBrains Pycharm
Tried, but not sure all (5) files intended are attached: .tcl, _support.py, .py and two images of output from the IDEs. Please let me know if you don't recieve all the files.
Well, I must apologize. Reading the other posts more closely, it occured to me that the copyright symbol (a UTF-8 code) might be the culprit. Sure enough.... When I delete the copyright symbol the generated file runs in the IDEs. So it's a matter of compatiblity with the IDEs. Sorry for bother.
The jpg files are there but not the python files. You can be able to send them by clicking on "rozen" above and then "send message" or to "don dot rozenberg at gmail dot com".
The jpg files suggest that you are using an earlier version of PAGE rather than 4.14 which has generates a directive for uft-8.