Bug 582680 - <indexterm> should be standalone in a translation
Summary: <indexterm> should be standalone in a translation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 1.6
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-15 14:50 UTC by Raphaël Hertzog
Modified: 2010-11-24 04:16 UTC (History)
6 users (show)

Fixed In Version: publican-1.6.3-0.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-17 18:57:11 UTC
jfearn: needinfo-
jfearn: needinfo-


Attachments (Terms of Use)

Description Raphaël Hertzog 2010-04-15 14:50:59 UTC
Description of problem:

If you have
<indexterm><primary>package</primary><secondary>search</secondary></indexterm> outside of a translatable tag, in the PO file you will have to translate "package" and "search" separately.

This is too fine-grained and will not allow proper translation in many cases
(consider when "search" is meant as a noun and when "search" is meant as verb, it will often require two different words in other languages).

In the same spirit, a translator might want to create two entries in the index for a given expression because there's no clear mapping for the given expression. If the PO file contains only the content of <indexterm> and not the tag in its entirety, he will not be able to do this.

Comment 1 Jeff Fearn 🐞 2010-05-04 04:08:33 UTC
Made indexterm a single translation entry.

Comment 2 Ruediger Landmann 2010-05-06 05:05:24 UTC
<indexterm><primary>package</primary><secondary>search</secondary></indexterm> 

appears as two separate msgids in version 1.6.3.t122:

#. Tag: primary
#, no-c-format
msgid "package"
msgstr ""

#. Tag: secondary
#, no-c-format
msgid "search"
msgstr ""

Comment 3 Ruediger Landmann 2010-05-06 05:42:10 UTC
Confirmed fixed in version 1.6.3.t150

Comment 4 jito 2010-05-11 22:46:44 UTC
<indexterm> tags do not appear on the test PO file; <primary> and <secondary> tags are now separate entries.

Comment 5 jito 2010-05-12 03:51:45 UTC
Further to the comment above, there are entries in the PO files that correspond to <indexterm> tags even though these tags do not appear on the files:

#. Tag: indexterm
#, no-c-format
msgid "<primary>text elements</primary><secondary>basic</secondary>"
msgstr ""

Comment 6 Fedora Update System 2010-05-13 22:20:58 UTC
publican-1.6.3-0.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/publican-1.6.3-0.fc13

Comment 7 Fedora Update System 2010-05-13 22:22:14 UTC
publican-1.6.3-0.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/publican-1.6.3-0.fc12

Comment 8 Fedora Update System 2010-05-15 20:36:38 UTC
publican-1.6.3-0.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update publican'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/publican-1.6.3-0.fc12

Comment 9 Fedora Update System 2010-05-15 20:45:51 UTC
publican-1.6.3-0.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update publican'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/publican-1.6.3-0.fc13

Comment 10 Fedora Update System 2010-05-17 18:55:55 UTC
publican-1.6.3-0.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2010-05-17 18:59:46 UTC
publican-1.6.3-0.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.