Joined: 7 Nov 17
I'm wondering why usernames or full names on these accounts inside Boinc cannot be written in UTF8? This should be made available because lots of users are outside the US.
Tomi Räsänen -> Tomi Rsnen
Help desk expert
Joined: 29 Aug 05
What I can find in the source code is that both the web site and BOINC Manager are already UTF-8 enabled, and have been since 2009.They're escaped in XML files, though.
Ref: this entry: MGR: Accept Unicode input for usernames and password in the manager now that the manager is Unicode enabled. Input will show up as UTF-8 strings in the CC and projects. Fixes #452
And this entry:
various components: fix inconsistencies in how user names and team names are represented. In particular, edit_user_info_action.php was using htmlentities() on names; this led to double-encoding.
The new rules:
1) no HTML tags allowed in either one. This is enforced silently, using strip_tags()
2) names are stored in the DB exactly as entered. They may contain chars like & and >.
They may contain non-ASCII characters (use UTF-8 if you want them displayed correctly). None of these are not escaped.
3) When the names are put in XML (e.g. in scheduler reply or db_dump output) they are XML-escaped. This escapes <, &, and non-ASCII chars
4) The client leaves them in this form, and writes them that way in GUI RPCs and init_data.xml files.
5) The parsing of GUI RPC replies and init_data.xml files XML-unescapes them.
Please do not private message me for tech support. Use the forums for that. Tech PMs will be ignored.
quote: "I'm an apostrophe, I'm just a symbol to remind you that there's more to see"
Help desk expert
Joined: 20 Nov 12
Where exactly and how are you trying to use non US-ASCII characters?
I just set my user name to "Tomi Räsänen" on a project web site and it showed correctly there and in Manager. It doesn't show correctly in Windows Command Prompt because Command Prompt doesn't support UTF-8.
Copyright © 2018 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.