Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Unicode applet #28

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments
Closed

Unicode applet #28

openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments

Comments

@openstreetmap-trac
Copy link

Reporter: steve[at]fractalus.com
[Submitted to the original trac issue database at 8.11am, Friday, 11th November 2005]

make sure unicode works in the applet

@openstreetmap-trac
Copy link
Author

Author: erik[at]tiq.com
[Added to the original trac issue at 2.20pm, Monday, 30th January 2006]

This is the code that used in the Processing example "Examples/data/CharactersStrings". I don't have all the code.

void keyPressed()
{
    if(key!=CODED)
       println("Key:"+ key);
    else
       println("Shift, alt or direction keys");
   

 } 

@openstreetmap-trac
Copy link
Author

Author: thomas[at]walraet.com
[Added to the original trac issue at 11.44pm, Tuesday, 4th July 2006]

The applet is in Java. All strings are handled in unicode internaly. All you have to do is to be sure to use the right encoding when you convert from/to stream data.

Actually, the applet use the plateform default character encoding. This is flowed :

  • It should send UTF-8, has stated in the XML header it send.
  • It should read ISO-8859-1 since this is what the server actually send (until Unicode API #29 is fixed)

A patch to fix this has been send to the dev ML. http://lists.openstreetmap.org/pipermail/dev/2006-June/001383.html

If you want to have a "full UTF-8" applet, just replace ISO-8859-1 by UTF-8 in this patch. But if you do this, it won't work normaly until #29 is fixed.

@openstreetmap-trac
Copy link
Author

Author: writetodan[at]yahoo.com
[Added to the original trac issue at 8.58pm, Wednesday, 14th March 2007]

fix deployed to www

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant