Closed ericwinger closed 1 year ago
Dolphin 7.1.9 supports unicode characters better. Here is what happens now in Jadeite.
Change (Added bullet point to method):
Changes browser now shows:
Going to assign to @LisaAlmarode for further testing in the ported code.
This issue is confusing since a bullet is not always a bullet, and it can be hard to know what you are really working with using a GUI.
If you paste a bullet into the UI, it's confusing since dophin sort of supports the 1252 code page which re-uses ascii 149 for unicode 2020. This would have worked in the older dolphin codebase and is presumably what the customer is using and seeing?
Note that an actual bullet with unicode 2022 (decimal 8226), can't be pasted in, but code can be generated using:
RowanSample4Test rwCompileMethod:'test5
" comment ',
(String with: (Character withValue: 8226)),
' end comment"
^4'
category: 'tests'
This gets warnings everywhere, which is correct, and appears to be handled correctly.
It's not entirely clear what the customer is doing or what Eric is doing...
@LisaAlmarode The entire issue needs to be visited thoroughly, especially STON replication of unicode strings. However, for now, is the issue to make the Changes Browser handle the bullet?
... it make sense to handle the Unicode characters using RSR ... I think Kurt has tests cases for passing Unicode characters/strings around, so he might be solving the problem in Dolphin as well ... I can check with Kurt if you want...
@ericwinger's comments, I believe, are related to bullet 149, the codepage 1252 bullet. not the real unicode bullet 2022. Handling of bullet 149 and other code page characters is really bad now and that should be looked at.
I think we've cleaned up unicode strings from rowan pretty well and that may not be an issue any more. The customer appears to have actual bullet 2022 in their code.
Changes seems to be looking okay as of 3.2.12
When doing a
changes
command from the changes browser, the customer had a unicode character in the comment field. Until unicode is fully supported by Jadeite in #307, we need to handle this more gracefully. Attaching a stack and customer-generated screen shots. Looks like the problem is in our STON implementation.From customer:
Customer screen shots: