Thank you for pointing out this, Kelemen. However I don't know how to
include a newline when the string isn't already considered multiline in
Launchpad. How is this done?
TLE is right that this is an i18n error which must be fixed in unity.
But I guess we can patch it for now. Presumably the
Thanks. I could have sworn there was no such button when I looked at it
previously, but there it is at its well-known usual place... It is now
fixed in both places with an actual newline. Marking as fix committed
although we still need to open the general i18n issue in unity.
** Changed in:
Which strings are affected? Since this is apparently a GTK issue, is it
thousands (and thus impossible to fix for translators)? What should
translators do specifically?
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to
I also confirm that localized keys work in apt (actually in Spanish, but
it's the same issue). The screenshot from Jonas Karlsson is surprising
though. Jonas, if indeed it does not work, and no other reason can be
found, it must indicate a bug in apt. Or is there a specific version
where it
Thank you all. Possibly related bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1734545
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations
The Launchpad developers have not commented.
My suggestion: Disable translations entirely in Launchpad and always
import from upstream.
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching
Thank you very much.
(It would appear that the util-linux translations have not quite made it
yet:
https://translations.launchpad.net/ubuntu/artful/+source/util-
linux/+pots/util-linux/da/+details
It is still at 17% at the moment. I assume the new files are in the
import queue though which
Right! Excellent. Thank you again.
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1730793
Title:
Translations
Sorry, I meant to say that it is used as a noun, not a verb. But this
does not change much.
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
Thanks for reporting this, and to all of you for the discussion.
I/we discussed this when translating it.
The problem is that 'advise(-snap)' is used like a verb, but is also the
name of a command. This means when we translate it, we need to choose
either a proper translation (i.e., a verb), or
So what will happen exactly on the dev side?
There are many cases in snappy where command names are used rather
interchangeably as command names (nouns) or verbs, prompting translators
to decide which of the two to pick. Should I/we update the string to
get rid of the warning? (Maybe for next
Right - the English string wasn't changed after all.
Why do you, Zygmunt Krynicki (zyga), think the translation is wrong?
The string is "Advise will talk to apt via an apt hook". Advise is used
as a noun here, which is of course wrong unless referring to a command.
So why would it be wrong to
missed a word: ... don't really /have/ the resources
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1808213
I have changed the translation now ("Kommunikér med apt via en apt-
hook"), but please keep in mind that I/we have definitely not been one-
sidedly ignoring anything. AFAIK it was the English string which was
supposed to change, and the warning persists only because this did not
happen.
Please
Just FYI, translators don't see this kind of warning while translating
because we don't really the resources (or an appropriate environment) to
compile and test the programs. The best I can do is usually to infer
the context by looking at the source code.
--
You received this bug notification
Ubuntu presumably ships a particular version of GNOME. I understand
that this version is no longer based on the major (September) release,
but rather a previous minor release, in this case from July. Is that
always the case now and is that documented somewhere?
As can be seen here, the
Indeed GTK did not follow the GNOME release schedule, so I will try to
find out why. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
17 matches
Mail list logo
