Does not accept the right translation

[André Gondim]

When I try to insert the right translation, rosetta doesn't accept it. The right translation is in the "Packaged" item, but not in "Current".

The link is below:

https://translations.edge.launchpad.net/ubuntu/jaunty/+source/kdeutils/+pots/klaptopdaemon/pt_BR/+translate?show=untranslated

Cheers

[Данило Шеган (danilo)]

This is not Launchpad bug: this string is marked as using c-format flags, yet if that's a real correct translation, it's not using them. That should be fixed in klaptopdaemon POT (and possibly source code) as well.

[Jonathan Thomas (echidnaman)]

KDEUtils doesn't have klaptopdaemon in KDE4. Shouldn't Launchpad remove this pot?

[Данило Шеган (danilo)]

That's for Ubuntu translation team to resolve then. Adi, thanks for creating the new task for that then.

[Arne Goetje (arnegoetje)]

I have disabled this template for Jaunty. If it doesn't exist in KDE4, should it also be disabled for Intrepid then?

[Jonathan Thomas (echidnaman)]

Yeah. Maybe we should compile a list of now-nonexistent templates for KDE?

[David Planella (dpm)]

El dt 16 de 06 de 2009 a les 12:18 +0000, en/na Jonathan Thomas va
escriure:
> Yeah. Maybe we should compile a list of now-nonexistent templates for
> KDE?
>

Yes, in any case, we discussed we should do this for Karmic.

@Arne: we talked about this on UDS with ScottK, and the idea was that
the process of getting the template names should be scriptable.

IIRC, he asked you to summarise how to do this on an e-mail, so that he
or someone from the Kubuntu community could come up with an up to date
list of templates.

Have you had a chance to e-mail him? And if not, could you e-mail him or
alternatively first start a discussion on the
ubuntu-translation-coordinator list on how to do this, so we can kick
off a good Kubuntu translation release for Karmic?

Regards,
David.

--
David Planella
Ubuntu Translations Coordinator
david(dot)planella(at)ubuntu(dot)com
www.ubuntu.com

[André Gondim (andregondim)]

Thank you for the solution.

Cheers.

[Arne Goetje (arnegoetje)]

Not yet.

What we need to have is a list containing the source package name and
the .pot or .po filenames for each source package.

Now, if I download the source package for kde-l10n-de for example, it
contains a lot of subdirectories, one for each project, I suppose, which
contain the .po files for German in this case. Each .po file carries the
translation domain in its filename.

When I download the source package of, let's say, kde4libs, it contains
a Messages.sh script, which is supposed to generate the .pot files on
build time if I'm not mistaken.

(Somehow I fail to build both source packages on my local machine, so I
cannot see what is actually happening.)

What I still don't understand is the relationship between those two
packages. In the kde-l10n-de package, the translations for kde4libs are
actually in the directory called 'kdelibs'. This suggests me that the
directory name does not necessarily match the source package name in
Kubuntu... so, how is this mapping done?

So, what we need is a list like:

kde4libs kdelibs4
kde4libs kdelibs_colors
...

We would need this list for every KDE upload, means the lists should be
versioned.

For the upcoming Karmic translation opening (hopefully next week), we
would need this list for the latest release in Jaunty (4.2.2) and for
the current one in Karmic (4.2.90). Then we can produce a diff and can
see what has changed.

We would then need to find out what happened to those templates, which
have changed between those two releases.
 * Is it a new template?
 * Has it been renamed from another name in the older release?
 * Has it moved across source packages?
 * What happened to those templates which were in the old release but
are missing in the new one? Have they been obsoleted, renamed or moved?

I don't know how things work on the Kubuntu-devel side... so, I cannot
give any scripting advice. Maybe those template movements can be tracked
in the svn changelog?

So, I need some input here. :)

[Jeroen T. Vermeulen (jtv)]

Arne Goetje wrote:

> What I still don't understand is the relationship between those two
> packages. In the kde-l10n-de package, the translations for kde4libs are
> actually in the directory called 'kdelibs'. This suggests me that the
> directory name does not necessarily match the source package name in
> Kubuntu... so, how is this mapping done?

I'm in a bit of a rush but if I understand the question correctly, then
the answer is: by template domain. The directory name is ignored, and
indeed there are a few cases where the package names as kept in LP don't
quite match the ones reflected by the directory names you see there.

This also explains why we get showered with warnings when a KDE template
has moved: suddenly there are two templates with the same domain, and
the mapping breaks.

Jeroen

[Данило Шеган (danilo)]

У чет, 18. 06 2009. у 06:11 +0000, Jeroen T. Vermeulen пише:
> Arne Goetje wrote:
>
> > What I still don't understand is the relationship between those two
> > packages. In the kde-l10n-de package, the translations for kde4libs are
> > actually in the directory called 'kdelibs'. This suggests me that the
> > directory name does not necessarily match the source package name in
> > Kubuntu... so, how is this mapping done?
>
> I'm in a bit of a rush but if I understand the question correctly, then
> the answer is: by template domain. The directory name is ignored, and
> indeed there are a few cases where the package names as kept in LP don't
> quite match the ones reflected by the directory names you see there.
>
> This also explains why we get showered with warnings when a KDE template
> has moved: suddenly there are two templates with the same domain, and
> the mapping breaks.

Jeroen: note that this is a discussion about stuff that happens before
KDE templates get into Launchpad (about how packages are structured).
I.e. something that will help Arne figure out how they work today, and
help us come up with a better algorithm for recognizing KDE files in the
future.

Cheers,
Danilo