> Could you be a bit more specific? Which release are you referring to? In
> Lucid koffice was in universe, so they were not imported. In Maverick
> koffice is back in main, so translations are being imported again.
I’m referring to maverick. I had to import all translations manually (they’re
in
Am Mittwoch, dem 08.09.2010, um 17:19 schrieb David Planella:
> El dc 08 de 09 de 2010 a les 00:35 +0200, en/na Moritz Baumann va
>
> escriure:
> > Am Mittwoch, dem 07.09.2010, um 14:23 schrieb Jonathan Riddell:
> > > I've compiled a list of what needs translated in
Am Mittwoch, dem 07.09.2010, um 14:23 schrieb Jonathan Riddell:
> I've compiled a list of what needs translated in Kubuntu 10.10 which
> is due out at the start of October.
>
> https://wiki.kubuntu.org/Kubuntu/Translations
Thank you for the list!
The .pot files of libdebconf-kde and bluedevil ar
Am Dienstag, dem 21.05.2010, um 19:00 schrieb Adi Roiban:
> > Additionally we are trying to divide work (who does what) within the
> > translation group. (some people prefer to work "offline" with a
> > program like poedit). It's annoying that each person needs to go to
> > wiki and write they want
Hello Andrej.
Am Freitag, dem 21.05.2010, um 15:51 schrieb Andrej Znidarsic:
> I am a coordinatior of slovenian ubuntu translation group and I was
> wondering what are your experiences with establishing and maintaining a
> good relationship with upstream.
The most important thing is contacting yo
Hi Mario,
the original English messages are loaded with acronyms and terms which neither
I nor google have ever seen or heard of before; and they’re becoming more and
more. Could you please consider using more generic terms in future releases?
The current diction makes translations really hard
Am Dienstag, dem 13.04.2010, um 10:02 schrieb David Planella:
> I've manually uploaded an updated template for mountall which includes
> more messages to speed up the resolution of this bug [1]. The new
> strings come from the fix of another bug [2].
>
> It is now in the imports queue and will be
Am Donnerstag, 01. April 2010 18:53:58 schrieb Ask Hjorth Larsen:
> I don't want to sound too antagonistic here (we all want to improve
> Rosetta!), but I view the lack of support for fuzzy strings as a
> serious problem, making launchpad translations inherently more
> wasteful when comparing to 'd
Just finished the German translation. Hope I didn't misunderstand anything,
since the only thing I really know about the Council is that it exists.
Am Donnerstag, 01. April 2010 09:49:26 schrieb David Planella:
> Hi all,
>
> I've been working with Laura Czajkowski to set up the main LoCo Council
Am Samstag, 13. März 2010 00:27:00 schrieb Dylan McCall:
> Would it be okay for the translation effort if I upload the new strings and
> consider them frozen with documentation freeze on March 25? There would
> then be beta 2 and the release candidates for translations to be tested.
This would be
Hi David,
Am Montag, 15. Februar 2010 19:12:22 schrieb David Planella:
> I've now commented on the bug. Let's try to move forward and get it from
> there.
doesn't look like Scott is going to accept any patch and I don't know of any
other way to get comments into the translation templates.
If an
rgeleitete Nachricht --
Betreff: Re: [Bug 521823] Re: Comments would make translations easier
Datum: Montag, 15. Februar 2010, 17:13:22
Von: Scott James Remnant
An: flamin...@online.de
On Mon, 2010-02-15 at 15:50 +, Moritz Baumann wrote:
> To name some examples:
>
> "sto
Hello everyone,
some week ago a user complained about the "printer properties" being
untranslated. (Printing dialogue of any KDE app → click "properties" next to
the printer you selected → "advanced" tab.)
I suspected those strings to come from cups and so I manually imported the
upstream trans
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jeroen and Danilo,
Jeroen Vermeulen schrieb:
> Puzzling indeed! Do you know exactly when this was? We may be able to
> correlate it to something.
the import of gnome-user-docs was done on April 11 or 12 and
approximately one week later I noticed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeroen Vermeulen schrieb:
> 1. Other translations were imported (or selected by another translation
> team member) after you provided yours.
No other member of the German team had worked on these templates.
> 2. If you did a published upload, then an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
during the translation process of Jaunty I've experienced a weird
behaviour multiple times: Rosetta suddenly "degraded" my translations to
suggestions some hours after I've made them. Two examples:
- - computer-janitor
- - new upstream tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Colin Watson schrieb:
> I received a report today of a mistake in the German translation of
> debian-installer, which prompted me to check for other similar errors.
> When translating the installer, it is very important to make sure that
> text such as
17 matches
Mail list logo