Beta 048: Umlaute in Target name get converted to "_" in file name

Issue #1084 wontfix
Ruediger created an issue

Hello,

I noticed that Umlaute in target name get converted into “_” in filenames.

CS
Rüdiger

Comments (6)

  1. Dale Ghent

    NINA removes extended ASCII and unicode characters from file names for various technical reasons - sometimes the underlying file system may consider them to be invalid or unknown characters, or some applications have trouble opening files that have these characters in the name. NINA runs all generated file names through a Windows facility that tells the app if any such characters exist and they are replaced with _ if so.

  2. Ruediger reporter

    Technical background is absolutely clear, but Umlaute are standard and well accepted by the filesystem. There is no need to replace them. This is over filtering.
    Second: If you parse and replace these special characters in file name during output, it would be stringent to parse the input filed “Name” accordingly and replace these characters there too. It should be identical.

  3. Dale Ghent

    Consistency is not the goal. The textual strings are adapted to the medium in which they will be used. For example, the metadata facility of the XISF format permits unicode characters to to be used, so we maintain them for XISF files. “γ Cassiopeiae” is maintained as “γ Cassiopeiae” in the metadata of that file type. However, the FITS format supports only ASCII characters, so “γ Cassiopeiae” becomes “gam Cassiopeiae” (we have a special translation table for Greek characters due to their common use in astronomical common names.) If it were a non-greek extended character, it would be replaced with a “_” placeholder.

    I understand your desire, but we have ran into too many problems between different file system capabilities as well as the capabilities of the wide range of applications that images produced by NINA are opened in. We have arrived at the current scheme as a place of stability - playing to the most common denominator in terms of character support.

  4. Log in to comment