Hello,

On Mon, Jan 05, 2009 at 12:14:36PM +0000, Colin Watson wrote:
> 
> Feeding an mdoc manual page to po4a results in this message:
> 
>   # type: Dd
>   #: /home/cjwatson/src/ubuntu/germinate/germinate/man/germinate.1:1
>   #, no-wrap
>   msgid "May 27, 2005"
>   msgstr ""
> 
> This strikes me as a bit awkward. Yes, technically this is
> human-readable text and so should be translated. However, it's typically
> updated whenever the manual page source is updated (or at least ought to
> be!), and this would produce a fuzzy string every time.
> 
> Should I just use tricks like .if !'po4a'hide' for this, or can the
> defaults be improved? I haven't seen many mdoc pages translated with
> po4a, so I don't know what the common practice is here.

(Note this also happens in groff pages which have a date specified on the
.TH lines)

I usually leave those strings in the PO files.
They can be translated very quickly, and usually, if the date changes,
other strings were also changed. Also, if only this string is fuzzy, this
will not really lower the quality of the translation (and will have the
same effect as .if !'po4a'hide' unless only fully translated pages are
generated).

This could be changed by maintainer who automatically update the date
string at build time (for example @date@)


Ideally, I should interpret this string, try to guess the output language,
and translate it automatically.

But I don't really now how to make a short localized date. For example
$ date -d "May 27, 2005" +%x
27.05.2005

When I expected "27 mai 2005"

Do you think there could be ways to do this?
(Otherwise, I propose to close this bug)


Note: the manpages and manpages-dev packages are translated using po4a.
This makes a lot of pages with dates, and was not really an issue.
Well, we probably lost time translated these strings, but this is usually
only seconds, compared to big paragraphs which take a lot of time.

Best Regards,
-- 
Nekral



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to