Created attachment 49868 [details] English ODT file with several types of hyperlinks: English (without language identification), English (with language identification), French and Chinese. When you create a hyperlink in a Writer document (LibreOffice or OpenOffce.org), the language is explicitly set to "zxx" by default (this is shown in the statusbar as "[None]"). In order to identify the language of a hyperlink, you need to explicitly set it by selecting the link and picking a language. The cause seems to be a default in Writer. When you unpack an ODT file and inspect the file "styles.xml", you will find the following lines: <style:style style:name="Internet_20_link" style:display-name="Internet link" style:family="text"> <style:text-properties fo:color="#000080" fo:language="zxx" fo:country="none" style:text-underline-style="solid" style:text-underline-width="auto" style:text-underline-color="font-color" style:language-asian="zxx" style:country-asian="none" style:language-complex="zxx" style:country-complex="none"/> </style:style> The relevant attributes here are * fo:language="zxx" fo:country="none" * style:language-asian="zxx" style:country-asian="none" * style:language-complex="zxx" style:country-complex="none" It is unclear to me why these defaults exist. I could not find anything in the ODF 1.2 specification that justifies their existence. Some background from that specification (notably section 16.2<style:style>): "Styles defined by the <style:style> element use a hierarchical style model. The <style:style> element supports inheritance of formatting properties by a style from its parent style. A parent style is specified by the style:parent-style-name attribute on a <style:style> element." (Note that the style:style element for hyperlinks does not have a style:parent-style-name attribute.) "For styles with family text which are applied to elements which are contained in another element that specifies a style with family text, the search continues within the text style that is applied to the nearest ancestor element that specifies a style with family text, and continues in its parent styles." Based on this I would expect hyperlinks to inherit language properties from the paragraph within which it is contained. In my test document, they would inherit * fo:language="en" fo:country="GB" * style:language-asian="zh" style:country-asian="CN" * style:language-complex="ar" style:country-complex="SA" (I always enable East-Asian and CTL in Writer, and set the default language for Asian languages to "Chinese (simplified)".) However, the default hyperlink styles appear to prevent this. Authors usually forget to set the language of hyperlinks, so Writer should remove the defaults that set the language of hyperlink text to "zxx" / "[None]" (see first XML fragment). Since language information is essential for conversion to audio (in a screen reader or when converting to an audio book) and to Braille (punctuation and contracted forms are language-dependent), this is an accessibility issue. Hence the "[accessibility]" in the summary field of this bug.
There is a workaround for users who are familiar with styles: 1. In the Styles and Formatting panel (which can be opened with F11), select Character Styles (second button on the little toolbar); 2. Right-click on the style "Internet Link" and select Modify; 3. On the Font tab of Character Style dialog, select the default language for links. But it would be better if the languages were simply inherited from an ancestor.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
reproduced on LibO 3.5.0 beta 1
** 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 (4.4.0.3 or later): 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-02-19
I rechecked this bug using a freshly installed version of LibreOffice 4.3.6.2 on Windows 7 (32 bits) and I found that the issue is still present. The workaround that I described in my second comment still applies.
Migrating Whiteboard tags to Keywords: (a11y -> accessibility)
** 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) http://downloadarchive.documentfoundation.org/libreoffice/old/ 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! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Dear Christophe Strobbe, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I can confirm this bug in LibreOffice Writer 7.1.3.2 on OpenSUSE Leap 15.2. Select a span of text (e.g. with language set to "English (UK)"), press Ctrl + K to turn the text into a hyperlink, enter a URL into the URL field, press OK, and check the status bar: when the cursor is on the link, the status bar says the language is "[none]".
Fixed in Bug 126657, Bug 152492 and Bug 45949.