Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#116 closed task (fixed)

foreign characters ("ausländische" Schriftzeichen)

Reported by: martin.lehnert Owned by: martin.lehnert
Priority: normal Component: General and Main Views
Version: 1.0 Keywords:
Cc:

Description

comments by JBV (Torben Brand) to alpha version:

Foreign characters. RailML requires UTF code. Do not display UTF code, example "B\351Y" but the intended value "BØY".

Attachments (2)

Umlaut-UTF8.html (434 bytes) - added by susanne.wunsch 5 years ago.
HTML file containing umlaut in UTF-8 encoding
Umlaut-Latin1.html (386 bytes) - added by susanne.wunsch 5 years ago.
HTML file containing umlaut in ISO-8859-1 encoding

Download all attachments as: .zip

Change History (8)

comment:1 Changed 5 years ago by birgit.jaekel

  • Owner changed from birgit.jaekel to vasco.kolmorgen
  • Status changed from new to assigned

Looking in the xml code one can see that the string written there reads "B\351Y". Instead, the correct representation in the UTF-8 file should be "BØY". In both cases the application shows the string as it is written in the xml file.

How to cope with this?

comment:2 Changed 5 years ago by birgit.jaekel

  • Summary changed from forain characters ("ausländische" Schriftzeichen) to foreign characters ("ausländische" Schriftzeichen)

comment:3 Changed 5 years ago by susanne.wunsch

The UTF-8 encoded XML file contains the characters "B\371y", which are shown in this way without any conversion in the background. RailVIVID works as required, it is no RailVIVID bug. The file was created with "OpenTrack (http://www.opentrack.ch)". If the export file contains not desired characters, this must be reported to OpenTrack.

Explanation:

There are two HTML files attached to the ticket, which present some possible misunderstanding for character encodings. Both files may be opened in the Web-Browser and will show the same content (despite the last line). But both files differ regarding their character encoding. That means, changing the character encoding (Firefox: View -> Character encoding -> Unicode / Western) results in wrong interpretation of the characters and wrong displaying. Looking at the source code of both files with an encoding aware text editor reveals multiple ways for saving "umlauts", that result in the same shown character. But the pure text "B\371y" will never be translated into "Bøy".

Recommendation: Use the "umlaut" directly in UTF-8.

See also http://wiki.railml.org/index.php?title=CO:attributeSyntax#Character_references for alternative character representations in case of ISO-8859 XML files. Nevertheless, ISO-8859-1 contains all characters, which are needed for "Bøy" (see attached HTML sample file).

See also https://en.wikipedia.org/wiki/Specials_(Unicode_block)#Replacement_character for any explanations regarding wrong encoding declaration (UTF-8 versus ISO-8859).

Changed 5 years ago by susanne.wunsch

HTML file containing umlaut in UTF-8 encoding

Changed 5 years ago by susanne.wunsch

HTML file containing umlaut in ISO-8859-1 encoding

comment:4 Changed 5 years ago by susanne.wunsch

  • Owner changed from vasco.kolmorgen to martin.lehnert

comment:5 Changed 5 years ago by martin.lehnert

  • Resolution set to fixed
  • Status changed from assigned to closed

issues reported to Torben (JBV) via e-mail (cc: railML-Coordinator)

comment:6 Changed 4 years ago by railML-admin

  • milestone Productive version (V1.0) deleted

Milestone deleted

Note: See TracTickets for help on using tickets.