I can not restore the chain of events. But I submitted a patch  that shows that the HelpAutoring 1.3 may leave blank ID tags. Most likely it happened when I edited the document and not at the time of its creation.
Yes i see an id="" on line 455, but also notice that a number of paragraph ids in the document dont seem to be created by the authoring tool, so i'm not sure what to think.
Can you please let me know which version of the authoring tool you are using because there isnt any 1.3 version. The latest version is 3.1.2.
I see cases, where id="" happens. When a paragraph has no id, then it will get id="" on opening. Then it has an id and the macros do not detect, that the attribute is empty.
I see several ways to solve it, perhaps combine them:
(1) Correct the missing id attributes in all help files. Would that launch translations?
(2) Correct the mistake on import by generating an id in xmlhelp2soffice.xsl
(3) Use the "on load" event and the macro CheckOnLoad to correct the missing value in the id attribute.
(4) Check the IDs on save and correct an empty value then.
What do you think, what ansatz to use?
(In reply to Regina Henschel from comment #2)
> I see several ways to solve it, perhaps combine them:
> (1) Correct the missing id attributes in all help files. Would that launch
If there is a means of fixing all these in one swoop, that would be the most ideal, assuming the authoring tool isnt pushing out any empty ids.
> (2) Correct the mistake on import by generating an id in xmlhelp2soffice.xsl
The next best thing.
> (3) Use the "on load" event and the macro CheckOnLoad to correct the missing
> value in the id attribute.
Doing it there would cause undos to appear when loading a page and if you dont edit the page, it would ask to save changes which would be annoying.
> (4) Check the IDs on save and correct an empty value then.
As good as option 2. Would prefer to use this option over 2 though, so that we could also add to the routine to check for duplicates, as lera has found help files with duplicates.
In my proposed patch https://gerrit.libreoffice.org/19166 for bug #93981 I add an id, if it is missing at all in the file or if it has an empty value. That is the way (2).
It is still useful to make sure that the id values are correct, when saving the file. The user might have tried to enter values manually. So way (4) is still necessary. Doing it in the macro and not in the export filter has the advantage, that the user gets informed, that something is wrong with the file.
Jay: Do you like to improve the scripts?
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice
(5.1.6 or 5.2.3 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Helpauthoring extension is deprecated. closing wontfix.