On Thu, Mar 13, 2008 at 02:48:04PM +0200, Eddy Petrișor <[EMAIL PROTECTED]> was 
heard to say:
> Daniel Burrows wrote:
>>   Hello, everyone.
>>
>>   I've got enough bug-fixes and new features into the aptitude source
>> tree that I think it's time for a new release.  This includes:
>
> Could you, please, include also the attached updated Romanian translation in 
> the upload?
> Also, addressing the comments marked with XXX and written in english 
> (extracted here, for your convenience)?
>
> (Note: if you will do no changes related to the comments, is ok, but if 
> you chaneg stuff, I would appreciate a heads up so I can update the 
> translation).
>
>
> 0 [EMAIL PROTECTED] ~/usr/traduceri/po/aptitude/po $ grep XXX -A 5 ro.po
> # XXX: is 'y' translatable?
> #: src/cmdline/cmdline_prompt.cc:732
> #, c-format
> msgid "y: %F"
> msgstr "y: %F"

  I don't think "y" is translatable here.  Perhaps it should be, but
doing so is a bit awkward because this isn't just a yes/no prompt.

> # XXX: intentionally made aptitude less independent
> # XXX: does "I want to resolve" here means "aptitude is configured to 
> resolve" or
> #         does it mean "aptitude would resolve, if you'd configured it to,"?
> #: src/cmdline/cmdline_resolver.cc:512
> msgid "I want to resolve dependencies, but no dependency resolver was 
> created."
> msgstr ""
> "Aptitude „vrea” să rezolve dependențele, dar nu s-a creat nici un rezolvator 
> "

  It means "OMG, Daniel screwed up and something 'impossible' happened!"
I've been moving away from flagging these "internal errors" for
translation since there's not usually anything the translators can do
with them -- but for now you could just add the equivalent of "internal
error" at the front of your translation.

  The menu entries should perhaps be split, as you note, but I'm not
sure I want to do that and break all the languages that have translated
them already (those are pretty old strings).

> BTW, would you prefer I publish my aptitude repo and pull from there (of 
> course, given that I don't mess up the history - will probably need to 
> clone again since I already have 2 or three merges).

  Sure.

  Daniel



Reply via email to