Apache OpenOffice (AOO) Bugzilla – Issue 35024
alternate texts for images in helpcontent2
Last modified: 2013-08-07 15:00:01 UTC
Among helpcontent2.0 translatable strings there are plenty of strings like \\<image id=\\\"img_id3145632\\\" src=\\\"starmath/res/sc30271.png\\\"\\>\\<alt id=\\\"alt_id3145632\\\" xml-lang=\\\"en-US\\\"\\>Icon\\</alt\\>\\</image\\>, is here something to translate or not... The field xml-lang=\\\"en-US\\\ bothers me too. why is it here and should we change it to according language? I think the right image should be displayed automagically? Is the text 'Icon' an alternate text for image and should be translated?
Confirmed. Ivo, I think we should only export text Icon here. The question is if we want to translate the name of the image but I think this is nonsense. Images will be created under the same name for every language. Is this OK for everyone?
It's an structual problem that can't be fixed till OOo 2.0 . The image tags is inside an Paragraph tag, the whole Paragraph is exported. It looks to me the we need to change the help2 spec.
*** Issue 40215 has been marked as a duplicate of this issue. ***
How would you resolve this? Inline images are inside paragraphs and images need ALT texts. Also, the "xml-lang" attribute is availabel for *every* element that is language dependent. One could discuss to leave it out when the superordinate element contains an xml-lang attribute but I really don't see a big issue here. I am open for suggestions, though. Adding myself to CC.
fpe: for what do you need xml-lang here? Images are only tags that have xml-lang *actually used*: pavel@linux:~/.ooo/cs> grep xml-lang en-US.sdf |grep -v image pavel@linux:~/.ooo/cs> This means that although xml-lang is defined for *every* element, only images use it. Why? Have a look at the result of the help compilation in the installed OOo. Help files for Czech language are inside "cs" directory. So all help files already are "marked" once with the ISO code "cs". Can we reuse it for all xml-lang's?
>fpe: for what do you need xml-lang here? Images are only tags that >have xml-lang *actually used*: No. Look at the XML files. Only that these element tags don't get exported to GSI. You are looking at the special case of an image. Because the complete image element is child of a paragraph element you see this. Again, we may need to reconsider the XML structure for >2.0 > This means that although xml-lang is defined for *every* element, only images > use it. Why? see above, just look at the source XML. The xml-lang attribute actually was a requirement by Release Engineering so that they can find the strings to export. >Have a look at the result of the help compilation in the installed OOo. Help >files for Czech language are inside "cs" directory. So all help files already >are "marked" once with the ISO code "cs". Can we reuse it for all xml-lang's? I guess so, yes.
I've created a new bug for the redudant xml-lang tags #i40909#
The usage of a 'Icon' variable is something for fpe
Created attachment 22897 [details] patch that solves build breakage in helpcontent2 for MacOSX (PowerPC)
Sorry, I just got confused because the search query returned two results. The patch file just happened to got to the wrong issue. Please ignore it!!!
Where's the remaining issue here? It looks like Ivo has fixed the use of xml-lang in i40909. Cleaning up the strings to be less complex for export would be for Ivo, too.
fpe: the only issue now is the text Icon. Maybe it should be exported as second line into GSI? Or is it only some kind of default for image name and help authors forget to change it appropriately to e.g. "Save to file icon"?
@Pavel: "Icon" is used throughout the help as an alt text for all icons. Since those are only used with descriptive text around them we think that the generic description would suffice. You can, however, be more specific. I don't understand your comment "Maybe it should be exported as second line into GSI?". What does that mean? Do you think we should use a reference to the literal text "icon" defined once as a variable somewhere? That would increase the clutter of these paragraphs going from \\<image id=\\\"img_id3145632\\\" src=\\\"starmath/res/sc30271.png\\\"\\>\\<alt id=\\\"alt_id3145632\\\" xml-lang=\\\"en-US\\\"\\>Icon\\</alt\\>\\</image\\> to \\<image id=\\\"img_id3145632\\\" src=\\\"starmath/res/sc30271.png\\\"\\>\\<alt id=\\\"alt_id3145632\\\" xml-lang=\\\"en-US\\\"\\>\\<embedvar href=\\\"text/shared/00/000004.xhp#icon\\\"/\\>\\</alt\\>\\</image\\> The real pain here seems to be how these strings are presented to the translators. This massive abuse of backslashes is not helpful. In plain XML translatable text should be easily identifiable (even by syntax highlighting using an editor). The xml-lang tags part of this issue was taken care of by ihi in i40909. The backslash clutter in the GSI file should be addressed in a separate issue to ihi.
reopened due to braindead issue tracking process implementation
reassign
wontfix
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew