https://bugs.documentfoundation.org/show_bug.cgi?id=94488

Regina Henschel <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #5 from Regina Henschel <[email protected]> ---
So you get these problems:
Nesting an embedvar-element into a link for to help translators does not work,
because no link is generated.
Nesting the link into the variable gives the user a link to the current text,
which is confusing for the user.

It is indeed a problem, therefore I set the issue to new.

A solution is not straight forward.

1.
The helpdocument.dtd allows an embedvar-element as child of a link-element. And
it allows a link-element as child of a variable-element. I don't know yet,
where in case of nesting embedvar-element into link-element, the link is
removed or not set. And I do not know, whether this behavior intended and only
the doctype definition has not been adapted, or whether it is a bug.

2.
If putting an embedvar-element (which might contain a link-element) into an
link-element, it might be, that a link in a link is generated. In the end an
html-document is generated where the link-element becomes an anchor-element <a
...> and such anchor-elements may not be nested in html. So somewhere on the
way to html such nested links need to be resolved.

3.
The transformation from xhp to html by main_transform.xsl removes for a heading
the link to itself. That is in line #265-#267. Extend that to also catch the
case of linking to a fragment in the file? How to do that?

4.
For Calc-functions I can think of a solution, where each Calc-functions gets
its own file, so that a link can always go to the topmost heading. But changing
the existing files would generate a large amount of work for translators.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to