e AppArmor maintainers:
I have filed this as `serious' not to try to force you to fix this,
but because this bug seems like it will cause AppArmor to work badly
for many people and I felt you would want me to be sure you noticed.
So please adjust the severity as you like.
I hope everyone fi
it an emotional
experience. You have made me happy.
I hope you found that I had made your work convenient.
On a technical note: reading your translation caused me to spot a
formatting error in the English text. I am fixing that and will
unfuzz the Dutch translation myself.
Regards,
Ian.
--
Ian
ot;"
#. type: textblock
#: ../dgit-user.7.pod:364
msgid ""
"The proper solution is to build the package for all the architectures you "
"have enabled. You'll need a chroot for each of the secondary "
"architectures. This is somewhat tiresome, e
e to send a .pot to this mailing list like
that ? Also, because each manual is its own .pot, there are 13 .pot
files.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
t the top of its pile, rather
than at the bottom, so changes can be made quite late. 8.0 (just
uploaded) has nontrivial changes and depending on my CFT (Copious Free
Time (-:) I may yet do more significant work on it.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed yo
Ian Jackson writes ("Re: advice on po/pot/po4a layout etc. [and 1 more
messages]"):
> I'm still working on marking up git-debrebase for message translation,
> and haven't done anything about the docs. When I have done those
> things, and subject to any review com
Helge Kreutzmann writes ("Re: advice on po/pot/po4a layout etc. [and 1 more
messages]"):
> Hello Ian,
> On Mon, Sep 17, 2018 at 03:42:39PM +0100, Ian Jackson wrote:
> > > Giving context information to translators is always good. You can add
> > > annotations v
this, and that users of my
programs (the latter being - at least sort-of - programmers) will be
able to cope with the resulting odd-sounding messages. I guess these
kind of problems are hardly new.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl
ail. I'll
reply only with the bits I had further questions/comments on.
> On Wed, Sep 12, 2018 at 09:48:56PM +0100, Ian Jackson wrote:
> > Relatedly, how do automatic translation coversge tools (we have those
> > I think?) deal with the variety of different possible layouts ?
>
n't see
anything relevant.
Perhaps you would like to file a bug ?
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
wers to my questions in the
documentation for gettext, etc. Am I missing some best practice
guide ?
All advice and opinions gratefully appreciated.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
FYI I have just uploaded xfonts-traditional 1.5 which contains all of
the translations from the tarball provided by Christian Perrier.
Thanks, Christian.
There is one wrinkle I need to bring to your attention, though. As
previously discussed, I have not accepted all of the changes suggested
by de
Christian PERRIER writes ("Re: Bug#660965: Exploring the possibility of an l10n
upload of xfonts-traditional to fix pending po-debconf l10n bugs (and debconf
templates changes)"):
> But, as there are many packages which I want to focus on (with the
> release in perspective), I would really love t
Christian PERRIER writes ("Re: Exploring the possibility of an l10n upload of
xfonts-traditional to fix pending po-debconf l10n bugs (and debconf templates
changes)"):
> - pick the PO files *as they are* in my final summary in the review
> bug report
I assume you mean #660965. You have CC'd 658
Christian PERRIER writes ("Re: Exploring the possibility of an l10n upload of
xfonts-traditional to fix pending po-debconf l10n bugs (and debconf templates
changes)"):
> Quoting Ian Jackson (ijack...@chiark.greenend.org.uk):
> > If I wish to take some but not all of the chang
Christian PERRIER writes ("Exploring the possibility of an l10n upload of
xfonts-traditional to fix pending po-debconf l10n bugs (and debconf templates
changes)"):
> So, sorry for this, but the radar beeped at your package and here am I
> with what I usually call an "NMU intent"...:-). Please tak
Davide Prina writes ("Re: Description-less Packages indices"):
> the DDTSS is totally broken :-(
Well, I don't know anything about "DDTSS". I don't know what it is,
at all, and I have never been involved in the translation effort. But
I do think I understand how the client code works, mostly any
Eddy PetriÅor writes ("Please improve the wording of the translatable
messages"):
> Way too spartan messages to be understood (I looked at the code and
> couldn't understand how they should have been translated as, until I
> realised the format was "operation that was attempted: error string")
W
Jacob Sparre Andersen writes ("Re: comments/string changes and issues with
dpkg's messages"):
> I find this a very bad example. In most cases "could not
> stat file" is just an incomprehensible way of writing "file
> not found". But if the error _is_ due to an error in the
> program and not due
Martin Quinson writes ("Re: comments/string changes and issues with dpkg's
messages"):
> But maybe the problem is that they should first get translated from geek to
> regular english?
>
> What about changing "cannot stat %s" to "cannot access %s"? I know it loses
> a bit of information, but does
Denis Barbier writes ("Re: comments/string changes and issues with dpkg's
messages"):
> On Fri, Aug 26, 2005 at 06:36:39PM +0100, Ian Jackson wrote:
> > Adam Heath writes:
> > > ohshite should really be for internal errors only. Things that
> > > "S
Eddy Petrisor writes ("comments/string changes and issues with dpkg's
messages"):
> 1) dpkg-1.13.8/dselect/helpmsgs.cc states that it is generated from
> helpmsgs.src by mkhelpmsgs.pl.
> Neither of these two files is present. Where are they?
This is very strange. The last version of dpkg I hav
Adam Heath writes ("Re: comments/string changes and issues with dpkg's
messages"):
> ohshite should really be for internal errors only. Things that "Should Not
> Happen(tm)".
This is totally 100% INcorrect. ohshite is used nearly everywhere for
system call failures, eg `disk full'.
Ian.
--
Santiago Vila writes ("Re: dpkg and I18N"):
> On Thu, 22 Jul 1999, Wichert Akkerman wrote:
> > Previously Ian Jackson wrote:
> > > Is i18n support currently enabled or disabled in the stable and
> > > unstable versions of dpkg ? There have been a num
Is i18n support currently enabled or disabled in the stable and
unstable versions of dpkg ? There have been a number of problems with
it, I know - coredumps in some i18n function.
Ian.
Martin Schulze writes ("Re: dpkg i18n and gettext"):
> Ian Jackson wrote:
> > I'm rather unimpressed with the current state of dpkg's build system,
> > including the i18n stuff. I'm also unimpressed by GNU gettext (I
> > agree with gettext's de
I'm rather unimpressed with the current state of dpkg's build system,
including the i18n stuff. I'm also unimpressed by GNU gettext (I
agree with gettext's detractors in favour of catgets).
Over the next weeks and months I expect to be un-reorganising dpkg's
build system to look more like the way
27 matches
Mail list logo
