Sorry but we have never received your initial post ("On 2/5/2020 11:11
AM, H. Andrew Black wrote:").
I'm not sure to be able to reproduce this issue on any of our computers.
Which operating system/file system (name, version) sometimes uses NFD
and sometimes NFC to represent its file names? Seems to be a weird idea
inevitably leading to a lot of troubles (not just with XXE).
---
PS: I found my info about NFD/NFC here:
https://en.wikipedia.org/wiki/Unicode_equivalence
On 2/5/20 9:00 PM, H. Andrew Black wrote:
We just discovered that the acute i in the file name that works is NFC
(composed) while the acute i in the one that does not work is NFD
(decomposed). So it looks like the Choose File option converts the NFD
acute i to NFC. When XXE tries to find the file using the URI with NFC,
it cannot find the file that has NFD. Does this make sense?
Yes. Totally.
--Andy
On 2/5/2020 11:11 AM, H. Andrew Black wrote:
Hi, Hussein.
Using XXE version 9.2.0 (or earlier versions, too, like 8.3.0 and
7.5.0), we've noticed an odd thing with graphic image file names. In
the Attributes Editor tool, we use the Choose File option to find the
image file. Some file names that contain an acute i (í) display
correctly and some do not. The ones that do not give the red message
of "Cannot display image: (file location) (The system cannot find the
file specified)." In both cases, the acute i is converted to %C3%AD
which is the UTF-8 code for an acute i.
I'm attaching a minimal working example of this problem for a DocBook
section file. Unzip it and load the XML file into XXE and, hopefully,
you'll see that the first image renders fine but the second does not.
Is there something we're doing incorrectly with the second file?
Thanks,
--Andy
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
https://www.xmlmind.com/mailman/listinfo/xmleditor-support
