Quoting Alexander Wirt ([EMAIL PROTECTED]):

(in -i18n, Alexander called for an update of ipvsadm templates....I
use this as a good start for more general comments. Please don't CC
him to answers as I suspect he's subscribed to -devel)

Some comments:


> Dear Debian I18N people,
> 
> I would like to know if some of you would be interested in translating
> ipvsadm.
> 
> ipvsadm already includes cs.po de.po es.po fr.po it.po ko.po nb.po nl.po 
> pt.po pt_BR.po ru.po sv.po vi.po.
> So do not translate it to these languages (the translators will be
> contacted separately).

I suggest you use the "--languageteam" switch when using
podebconf-report-po. As far as I can see, on ly translators were
contacted, which may become a problem in case one is MIA (which
happens quite often). You'll certainly get some bounces from
pseudo-teams listed in some PO files.....or from the Vietnamese team
(which uses a poster-restricted list, grmbl)....but that's worth it
for the teams (German, French, Portuguese....) who use a properly
setup mailing list.


> #. Type: select
> #. Description
> #: ../ipvsadm.templates:1002
> msgid ""
> "ipvsadm can activate the IPVS synchronization daemon. \"master\" starts this 
> "
> "daemon in master mode, \"backup\" in backup mode and \"both\" uses master "
> "and  backup mode at the same time. \"none\" disables the daemon."
> msgstr ""

double spaces between "and" and "backup"

Very probably because "and" is at the end of a line in the templates
file and you have a trailing space there. I sometimes wonders whether
we could add a lintian check for this, indeed. I can't think of *good*
use cases for trailing whitespaces in debconf templates.

Anyway, if you fix that without care, you'll screw existing
translations.

The Right Way is:

- go to debian/po
- put received translations in place
- run "sed 's/and  backup/and backup'" on all PO files
- run debconf-updatepo

If you later receive translation updates, you'll have to similarly run
"sed" on them before running "debconf-updatepo" or building your package.

> #. Type: string
> #. Description
> #: ../ipvsadm.templates:4001
> msgid "Muilticast interface for ipvsadm:"
> msgstr ""

Typo. s/Muilticast/Multicast

Same way to "unfuzzy" than above


> 
> #. Type: string
> #. Description
> #: ../ipvsadm.templates:4001
> msgid ""
> "Select the multicast interface to be used by synchronization daemon. e.g. "
> "eth0, eth1..."
> msgstr ""

These templates would indeed benefit from a small review by
debian-l10n-english. We would then suggest you to remove the latinisms
(and slightly incorreect typography). However, that would require a
new translation update round....


> 
> #. Type: string
> #. Description
> #: ../ipvsadm.templates:4001
> msgid "${interface_error}"
> msgstr ""

That one should be non translatable. Recent po-debconf versions (etch
and lenny) allow this by using:

#flag:translate!:3

*just* before the "_Description" line of that specific template. The
"3" means "third component of this part is non translatable"

It is *very* important to mark such strings as non translatable as
this minimizes translator errors: some would otherwise *translate*
"interface" and "error".

Another hint: when a template contains such variable *in the middle*
of a translatable string, try putting a comment to translators such as
"Please DON'T translate ${foo} as this is a variable name".

This can be done this way:

# TRANSLATORS: don't translate ${disk}
_Description: Erase disk ${disk}?
 You can entirely erase the ${disk} disk.
 .
 Please confirm this is really what you want.

Or, even better:
#flag:comment:1,2
# TRANSLATORS: don't translate ${disk}
_Description: Erase disk?
 You can entirely erase the ${disk} disk.
 .
 Please confirm this is really what you want.



-- 


Attachment: signature.asc
Description: Digital signature

Reply via email to