Issue 40215 - "Icon" and xml-lang in icons
Summary: "Icon" and xml-lang in icons
Status: CLOSED DUPLICATE of issue 35024
Alias: None
Product: documentation
Classification: Unclassified
Component: Online help (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: frank.thomas.peters
QA Contact: issues@documentation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-08 22:40 UTC by pavel
Modified: 2005-01-24 16:06 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description pavel 2005-01-08 22:40:12 UTC
Hi,

during our current translation process, we found two inconveniencies with icons
and their alternative texts. I'm talking about lines like this in the GSI file:

helpcontent2    source\text\shared\01\02220000.xhp      0       help   
par_id3149811                           0       en-US   \<image
id=\"img_id3147275\" src=\"svx/res/nu07.png\" width=\"5.64mm\"
height=\"5.64mm\"\>\<alt id=\"alt_id3147275\"
xml-lang=\"en-US\"\>Icon\</alt\>\</image\>                           20050107
08:42:05

1. xml-lang attribute in them is IMO useless.

   - xml-lang is not used anywhere else
   - language is automatically determined in the GSI file (if I'm translating
for "cs", what else could be in xml-lang?)

2. The string "Icon" could be unified across the whole helpcontent2.

There are 1260 such lines in the GSI (3% of all helpcontent2 strings).

We already have them all "translated" by macro in my editor, but I do not think
this is optimal solution. It at least makes the planning process of the
translations hard.
Comment 1 pavel 2005-01-08 23:01:13 UTC
duplicate, all facts still apply though.


*** This issue has been marked as a duplicate of 35024 ***
Comment 2 frank.thomas.peters 2005-01-09 20:07:08 UTC
For #1: see #i35024# - you are looking at it from a GSI perspective. GSI is only
the localization transfer format.

For #2: Using a decent pretranslation or TM process would also resolve that
issue. See also my comments on #i40213#. In the case of "icon" I agree there is
room for optimization by using variables.
Comment 3 frank.thomas.peters 2005-01-24 16:06:21 UTC
Closing duplicate