Created attachment 98584 [details] shows how the file looked before saving as an RTF and afterwards I download the .docx file found at < http://download.microsoft.com/documents/uk/partner/publicsector/DraftMicrosoftResponsetoGovernment.docx > and opened it in LibO and saved it as an RTF. Then i reopened the RTF file and all links had black underlines rather than blue. This was tested in Linux Mint on the last releases from 3.6 to 4.2 and 4.3 alpha. Its a fileopen problem as the same RTF file opened in word 2010 has the links with blue underlines.
double check your screenshot. I see blue underlines in both images.
double checked the screenshot and the top one is dark blue and the bottom is black.
so check your monitor color-settings :-) I confirm "Unicode 6.2" text is bold blue underlined in both images and I cannot spot significant color difference between .docx and .rtf only differences I see is that not underlined text is grey, bold, italic in .docx while is bold black in before "unicode 6.2" and no-bold, no-italic, black in .rtf
(In reply to comment #3) > so check your monitor color-settings :-) > you should have said for me to check my eyes as monitors cant change underline colors. :) > I confirm "Unicode 6.2" text is bold blue underlined in both images and I > cannot spot significant color difference between .docx and .rtf > > only differences I see is that not underlined text is grey, bold, italic in > .docx > while is bold black in before "unicode 6.2" and no-bold, no-italic, black in > .rtf already submitted bugs for the color issue (bug 78313). :)
Created attachment 98609 [details] zoomed in blue link with black underline
ok now I see it!!! first screenshot was to small and my eyes are not so good as yours!!! :D issue confirmed under Win7x64 using 4.2.3.3
would have thought you'd try out the steps in the initial summary to see if worked there an not really just on my screenshots. :)
my bad :-)
Created attachment 98628 [details] minimal test case to save as .rtf
i normally do upload files created by other software (kingsoft, word, etc) encase the team doesnt have that software on their pc, but as its all LibO, i didnt see the advantage of doing that as well.
I think a minimal test case is easier and faster to use to reproduce the bug, rather than scrolling a multipage document looking for the exact point where the issue is.
also remember that external hyperlinks may change or expire, so it's alway good practice to upload documents in bugzilla, removing unnecessary parts.
someone on the mailing mentioned that it would be best to upload these files as well but i told them all my test .docx files were from documents on microsoft's website, which isnt going anywhere. :)
\ulc0 keyword is interpreted as 'black', not as 'the font color'. Also it is the default value which doesn't have to be exported at all.
Migrating Whiteboard tags to Keywords: (filter:rtf)
I've fixed this with commit 76c0d0abc89cd8948706083c2660b71a2dad670c on 2014-09-07 in 4.4 (4.3 was still bad).
Verified fixed: Version: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: it_IT.UTF-8 OS: openSUSE Tumbleweed (20160422) (x86_64) Version: 5.1.3.1 Build ID: 10m0(Build:1) Thread CPU: 4; Versione SO: Linux 4.5; Resa interfaccia: predefinito; Locale: it-IT (it_IT.UTF-8) OS: openSUSE Tumbleweed (20160422) (x86_64)