https://issues.apache.org/ooo/show_bug.cgi?id=123604

Rainer Bielefeld <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rainerbielefeld_ooo_qa@biel
                   |                            |efeldundbuss.de
          Component|editing                     |open-import
             Latest|---                         |4.0.1
    Confirmation on|                            |
            Version|4.1.0-dev                   |4.0.0
           See Also|                            |https://issues.apache.org/o
                   |                            |oo/show_bug.cgi?id=120845,
                   |                            |https://issues.apache.org/o
                   |                            |oo/show_bug.cgi?id=123063
            Summary|TOC update loses hyperlink  |particular .doc: TOC update
                   |                            |loses hyperlinks

--- Comment #1 from Rainer Bielefeld 
<[email protected]> ---
Reproducible with server installation of "AOO 4.1.0-Dev – German  UI / German
locale - [AOO410m1(Build:9750)  -  Rev. 1537508 - 2013-11-02]" on German WIN7
Home Premium (64bit)", own separate user profile;  but because of incomplete
LCo selector (Bug 123063) no correct information can be left.

Additional info:
----------------
(a) Not a new effect. OOo 3.1.1 OOo 3.3.0 ... AOO 3.4.1did not show 
    hyperlinks  (or bold) at all (what still is a problem with LibO 4.2)
(b) " AOO 4.0.0-Dev  – English UI / German locale [AOO400m1(Build:9700) - 
    Rev. 1457992 – Rev.1457606  ((2013-03-19))]" already imports hyperlinks in
    TOC (and bold style), and already shows the update losses.
(c) Lost Styles problem seems to be a DUP of "Bug 120845 - [writer001] some TOC 
    entry's styles lost after update TOC when open doc in AOO", so we should 
    limit this one to the hyperlink problem
(d) in Bug 120845 hyperlinks will not be lost after update, so may be
difference
    between sample documents might give a hint concerning bug roots.
(e) I think the root of the problem is an incorrect import of the TOC in
    the document.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.

Reply via email to