You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: miki [Submitted to the original trac issue database at 10.20am, Wednesday, 17th May 2006]
Adding a property value containing danish (ae) or (aa) characters (like name=Sndergrds Alle, see coord. 55.4739687619073,8.47640550265594) results in a garbled value when uploading and re-downloading the area. After download the character including the follwing two chracters are replaced by a square. Strangely the character is left untouched.
Seen on both Windows 98 and Windows Server 2003 using java version "1.5.0_06", Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05), Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode).
Mikkel,
The text was updated successfully, but these errors were encountered:
Author: immanuel.scholz[at]gmx.de [Added to the original trac issue at 11.08am, Monday, 12th June 2006]
JOSM seem to just not output UTF-8 at the moment, although it declares it would do it. This results in the Server not be able to read in the wrong declared encoding file.
Author: memb_openstreetmap[at]mikini.dk [Added to the original trac issue at 9.44am, Tuesday, 13th June 2006]
My experience as danish user (primarily trying to input , and ) is that most of the time the server accepts the changes, but isn't able to deocode the characters correctly.
The only time I have experienced upload errors was when using (bug #227 which you have marked as duplicate of this) but then yesterday and today I suddenly got errors when trying to add ways with properties "name=Sejrvej" and "name=Tunvej" even though I've previously uploaded a lot of ways with names containing using JOSM.
I also think there's more to it than just a property issue, caus I've just been looking at my map and now I have a whole bunch of incomplete ways (ways with undefined segments).
I've had some of these before, but never associated them with JOSM and the character encoding error. But now I know that the only thing I've done since the incomplete ways came about is a single editing session with JOSM yesterday, and when experiencing the above mentioned problem I just gave up and left it for later resolving. I now see that the segments I had been adding was correctly added to the server, but the ways weren't. And suddenly completely unrelated ways had undefined segments!
PS: Shouldn't the default color of incomplete ways be different from complete ways? This would clearly show that something is wrong/not completely downloaded. I use a ligther shade blue to make them stand out.
Author: immanuel.scholz[at]gmx.de [Added to the original trac issue at 11.07pm, Friday, 30th June 2006]
The character encoding stuff is fixed in revision 103.
About Mikel's incomplete way stuff: I don't think the character encoding is the reason for the server delivering wrongly incomplete ways (or JOSM read them as such). Note also, that incomplete ways are not an error but a normal condition if you download a rectangular map and the street goes beyond the border. This is also the reason for me to choose such similar color to the original street (to not confuse and disturb the people with too much different colors).
Reporter: miki
[Submitted to the original trac issue database at 10.20am, Wednesday, 17th May 2006]
Adding a property value containing danish (ae) or (aa) characters (like name=Sndergrds Alle, see coord. 55.4739687619073,8.47640550265594) results in a garbled value when uploading and re-downloading the area. After download the character including the follwing two chracters are replaced by a square. Strangely the character is left untouched.
Seen on both Windows 98 and Windows Server 2003 using java version "1.5.0_06", Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05), Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode).
Mikkel,
The text was updated successfully, but these errors were encountered: