On 28 Nov 2017, at 10:03, Hussein Shafie wrote:
On 11/28/2017 12:25 AM, Leif Halvard Silli wrote:
One practical issue is that when you add an empty or new file to your
map, the title of the document is not added. If you add several
files,
you could then rearrange the files a little (inside the map file)
before
adding content to them. But if the file name is completely
unreadable,
or requires that you open the file in its own tab - to add a title -
this option does not exist. (Unless, of course, you standardize on
practice of not using non-ASCII letters, and preferably avoid spaces
in
the names).
As already said, we will not change XXE code to switch it from URLs to
IRIs.
However, if this can really help, we can improve the *CSS*
*stylesheets* of DITA topics and maps.
In the styled view of a map, you would see (imagine what follows
"styled"):
topicref href="русский фаил.dita"
instead of:
topicref
href="%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%B8%D0%B9%20%D1%84%D0%B0%D0%B9%D0%BB.dita"
In the styled view of a topic, you would see (imagine what follows
"styled"):
xref href="русский фаил.dita#foo/bar"
instead of:
xref
href="%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%B8%D0%B9%20%D1%84%D0%B0%D0%B9%D0%BB.dita#foo/bar"
Please confirm that this would somewhat improve the situation.
First impression:
It looks/sounds as if this would improve the situation not only somewhat
but very, very much! The fact that not only the non-ASCII characters but
the space character as well would be displayed “as themselves” is
excellent!
Would this improved styled display also include the display of the
fragment urls: #Русский_файл
Qualification:
The fact that you include the 'href="' part in the styled view is
somewhat confusing with regard to being absolutely certain that we talk
about the same issue/solution. I suppose that the 'href="' part will -
like today - not display in the styled part. And thus that, in the
improved styled view that you propose, the display of the URL is
supposed to look like in the attached screenshot (see the ”Chapter
4” of that screenshot).
I also include the source files for that DITA document upon which the
screenshot is based. I think there is something wrong with the treatment
of URL fragments: why are they, currently (as well) rendered in the
source not percentage encoded but un-encoded? See scrennhot.
Leif Halvard Silli
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA BookMap//EN"
"bookmap.dtd">
<bookmap>
<title>The suggested improved CSS for (old) URLs</title>
<frontmatter>
<booklists>
<toc/>
</booklists>
</frontmatter>
<chapter href="See-below-0.dita">
<topicref href="%D0%A4%D0%B0%D0%B9%D0%BB%201.dita#Файл_1"/>
</chapter>
<chapter href="See-below-1.dita">
<topicref
href="%D0%A4%D0%B0%D0%B9%D0%BB%201.dita#%D0%A4%D0%B0%D0%B9%D0%BB_1"/>
</chapter>
<chapter href="See-below-2.dita">
<topicref href="Файл%201.dita#Файл_1"/>
</chapter>
<chapter href="See-below-3.dita">
<topicref href="Файл 1.dita#Файл_1"/>
</chapter>
</bookmap>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
"concept.dtd">
<concept id="как_ты">
<title>Actual current behavior</title>
<conbody>
<p/>
</conbody>
</concept>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
"concept.dtd">
<concept id="как_ты">
<title>Intended current behavior?</title>
<conbody>
<p/>
</conbody>
</concept>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
"concept.dtd">
<concept id="Файл_1">
<title xml:lang="ru">Файл 1</title>
<conbody>
<p/>
</conbody>
</concept>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
"concept.dtd">
<concept id="как_ты">
<title>The suggested, improved display?</title>
<conbody>
<p/>
</conbody>
</concept>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
"concept.dtd">
<concept id="как_ты">
<title>Improved styled display</title>
<conbody>
<p/>
</conbody>
</concept>
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
