fullwidht apostrophe – Window fails to load

[bwbohl]

When a fullwidth Apostrophe »'« (U+FF07) is part of the value being evaluated as window title the resource . fails to load

[peterstadler]

can you elaborate a little bit, please? Which XQuery(?) function fails?

[bwbohl]

Apparently this is quite old and probably also connected to #337

By the time I reported these content windows in the Edirom Online GUI failed to load contents and loaded as empty blank windows. All this was because the window title had some unexpected character, e.g. apostrophe (tick) or newline character. Probably normalizing space or even the proper serialization of requests might fix those issues.

[peterstadler]

I could not reproduce the issue. Adding a ＇ to a titlePart did not break the display.

The MEI code used

<mei xmlns="http://www.music-encoding.org/ns/mei" xmlns:xlink="http://www.w3.org/1999/xlink" meiversion="5.0" xml:id="edirom_source_obert-weberianaI-24">
    <meiHead meiversion="5.0">
        <fileDesc>
            <titleStmt>
                <title type="uniform" xml:lang="de">
                    <titlePart type="main" xml:lang="de">Weberiana Cl' I&#xFF07; 24</titlePart>
                    <titlePart type="perf" xml:lang="de">Die drei Pintos: Einige Takte Autograph</titlePart>
                </title>

The rendering

Attempt of explanation

Since this is a rather old issue, it probably got fixed in 2012 by ad25d850a6e2eb3e60a54a643e92b3519702a2e0 where the old way of manually returning a string value (return concat( … )) got changed to a proper serialization of a map object (return serialize($map, $options)).

[riedde]

The same for me, I also can't reproduce this. @bwbohl would you share a file with me that produces the fail? Maybe the problem is caused by a different incident.

[peterstadler]

I really do think this issue is outdated and fixed by proper serialization. I propose to close the issue if we do not come up with a reproducible test case in the next week

[bwbohl]

It

The same for me, I also can't reproduce this. @bwbohl would you share a file with me that produces the fail? Maybe the problem is caused by a different incident.

The issue is so 2017 ;-). I really don't think I still have the file lying around. So, I'm +1 for closing this as it is not reproducible.

[bwbohl]

@thx for all your efforts @riedde & @peterstadler