Improvement when exporting reports

[Binchen]

Hi,

may i ask for improving the export functionality of reports a little bit?

Look at this:

ref.xhtml,166,,Map of A,B and C,Section0003.xhtml,map1,no,,,,

In column D (Text) it may happen that there are already commas in the text which will than be not correctly imported into spreadsheet apps (or any other importing app as well)

Can this column be quoted to tell the importing app that the comma is part of the text and not indicating the next item?

ref.xhtml,166,,"Map of A,B and C",Section0003.xhtml,map1,no,,,,

Or maybe change the separating character to a tab(09)?

Binchen

[KevinH]

Much later after the Reports were added (before my time with Sigil), I added a real quoted csv output routines for saved searches. I should be able to use those routines to fix the Reports.

[Tex2002ans]

Or TSV export instead. Then no CSV problems.

[KevinH]

Tabs can be used in xhtml files, they only represent a single space but do exist.

[Binchen]

Thanks Kevin.

By the way, what is the last column in the link report is tellinh me? Column name is match with values yes, no and _blank_ but i have no idea what its trying to tell me.

Binchen

[Tex2002ans]

Originally Posted by Binchen

By the way, what is the last column in the link report is tellinh me? Column name is match with values yes, no and _blank_ but i have no idea what its trying to tell me.

The "Match?" column?

"Yes"

This lets you know if there's 2 href + id that point back to each other. For example:

<p>Example link that matches.<a href="#fn1" id="ft1">[1]</a></p>
- - -
<p class="footnote"><a href="#ft1" id="fn1">[1]</a> Points back to the first note in the text.</p>

You can see green href matches with green id in footnote.

And blue id matches with blue href in footnote.

"No"

But let's say you had a 2nd link that pointed to the same location:

<p>Example link that matches.<a href="#fn1" id="ft1">[1]</a></p>
<p>But this one points one-way.<a href="#fn1" id="ft1-2">[1]</a></p>
- - -
<p class="footnote"><a href="#ft1" id="fn1">[1]</a> Points back to the first note in the text.</p>

Now you can see a red id that doesn't have anything pointing back to it.

In this case, the "Matches?" column will say:

2 "Yes" = the green/blue links
1 "No" = the red link, because nothing points back to ft1-2.

Blank

This means it's a URL, or pointing to an id that doesn't exist in the book:

<p>Visit <a href="http://www.example.com">http://www.example.com</a> and the note.<a href="#fn999" id="ft999">[999]</a></p>

In these 2 cases, the "Target exists?" column will say:

"n/a" = URL
"no" = broken note, doesn't point to anything.

[KevinH]

Changed all the Reports to do proper CSV quoting just to be safe as filenames can include commas technically. That change is in my local tree and I will push it to master once I know no follow-on serious bug fix release is needed. In about a week or so I would guess.

[Binchen]

[Binchen]

But html5 only restricts IDs to non-whitespaces. In html4/xhtml it must start with a letter. After that, letters, digits, hyphen, underscore, colon and period is allowed.

So it might happen in epub3 having an ID containing a comma...

[KevinH]

The added routine treats all data values (columns) equally and properly quotes any values that need it.

[KevinH]

This fix has now been pushed to master. It will appear in the next release.