Ian Jackson wrote:
> As a good rule of thumb, there is no point translating an
> incomprehensible English message :-).
Agreed!
Preferably it shouldn't show up in the POT files either.
Jacob
--
»When in Rome; burn it«-- Diziet Sma
--
To UNSUBSCRIBE, email to [EMAIL PR
Ian Jackson wrote:
> You seem to be suggesting removing the detail from dpkg's
> error handling - ie, reporting less information to make
> the translation easier.
Removing information from the error messages is generally a
bad idea, BUT it is also a waste of everybody's time to put
strings which
On Wed, Aug 31, 2005 at 07:30:48PM +0100, Ian Jackson wrote:
[...]
> Err, are you complaining that the string
> dpkg: failed to write status record about `%.250s' to `%.250s'
> is too hard to translate ?
>
> You seem to be suggesting removing the detail from dpkg's error
> handling - ie, reporti
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_
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&quo
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
> > An internal error occured in dpkg. Please report the issue to the debian
> > BTS if you can, alongside with any relevant information such as what you
> > did
> > to reach this error and the detail of the issue indicated below. If you
> > know
> > how to reproduce the issue, please make sure
On Fri, Aug 26, 2005 at 06:36:39PM +0100, Ian Jackson wrote:
> 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)".
>
On Tue, 30 Aug 2005, Scott James Remnant wrote:
> We won't be seeing anything like that while I'm maintainer.
Like dpkg hasn't switched maintainers before.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, 2005-08-30 at 17:17 +0200, Martin Quinson wrote:
> <<
> An internal error occured in dpkg. Please report the issue to the debian
> BTS if you can, alongside with any relevant information such as what you did
> to reach this error and the detail of the issue indicated below. If you
On Tue, Aug 30, 2005 at 09:36:07AM +0200, Jacob Sparre Andersen wrote:
>
> I.e. error messages related to incorrect use of a program
> should be fully translatable whereas error messages due to
> errors in a program should be untranslatable (but
> accompanied by translatable advice on bug reportin
On Mon, Aug 29, 2005 at 06:57:54AM +0200, Christian Perrier wrote:
> > > Scott, the above was obiously humor but it then confuses my mind..:-)
> > > Do you actually agree with the messages better being *not*
> > > translatable or do you prefer keeping the current situation?
> > >
> > It's an inter
Eddy Petriºor wrote:
> Scott James Remnant wrote:
> > > Denis Barbier wrote:
> > > > Scott James Remnant wrote:
> > > > > Yes, because god forbid a developer should be able
> > > > > to understand what's going on when a user files a
> > > > > bug report.
> > > >
> > > > These ohshite messages tell
On 8/29/05, Konstantinos Margaritis <[EMAIL PROTECTED]> wrote:
> On Κυριακή 28 Αύγουστος 2005 12:52, Scott James Remnant wrote:
> > It's an interesting question, certainly; to my mind I don't think
> > it's any scarier to dump a scary english message or a scary french
> > one. The added advantage
On Κυριακή 28 Αύγουστος 2005 12:52, Scott James Remnant wrote:
> It's an interesting question, certainly; to my mind I don't think
> it's any scarier to dump a scary english message or a scary french
> one. The added advantage to translating them is that the user
> might have the skill to know wha
On 8/28/05, Scott James Remnant <[EMAIL PROTECTED]> wrote:
> On Sun, 2005-08-28 at 08:05 +0200, Christian Perrier wrote:
>
> > Quoting Denis Barbier ([EMAIL PROTECTED]):
> > > On Fri, Aug 26, 2005 at 09:00:04PM +0100, Scott James Remnant wrote:
> > > > Yes, because god forbid a developer should be
> > Scott, the above was obiously humor but it then confuses my mind..:-)
> > Do you actually agree with the messages better being *not*
> > translatable or do you prefer keeping the current situation?
> >
> It's an interesting question, certainly; to my mind I don't think it's
> any scarier to du
On Sun, 2005-08-28 at 08:05 +0200, Christian Perrier wrote:
> Quoting Denis Barbier ([EMAIL PROTECTED]):
> > On Fri, Aug 26, 2005 at 09:00:04PM +0100, Scott James Remnant wrote:
> > > Yes, because god forbid a developer should be able to understand what's
> > > going on when a user files a bug rep
Quoting Denis Barbier ([EMAIL PROTECTED]):
> On Fri, Aug 26, 2005 at 09:00:04PM +0100, Scott James Remnant wrote:
> > Yes, because god forbid a developer should be able to understand what's
> > going on when a user files a bug report.
>
> These ohshite messages tell nothing to end users, so they a
On Fri, Aug 26, 2005 at 09:00:04PM +0100, Scott James Remnant wrote:
> Yes, because god forbid a developer should be able to understand what's
> going on when a user files a bug report.
These ohshite messages tell nothing to end users, so they are mostly
useful for dpkg developers to deal with bug
On Fri, 2005-08-26 at 20:37 +0200, Denis Barbier wrote:
> On Fri, Aug 26, 2005 at 06:36:39PM +0100, Ian Jackson wrote:
> > Adam Heath writes ("Re: comments/string changes and issues with dpkg's
> > messages"):
> > > ohshite should really be for int
On Fri, Aug 26, 2005 at 06:36:39PM +0100, Ian Jackson wrote:
> 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)".
>
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. Th
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
On Thu, 18 Aug 2005, Eddy Petrisor wrote:
> On 8/17/05, Adam Heath <[EMAIL PROTECTED]> wrote:
> > On Wed, 3 Aug 2005, Eddy Petrisor wrote:
> >
> > > On 8/3/05, Denis Barbier <[EMAIL PROTECTED]> wrote:
> > > > On Tue, Jul 26, 2005 at 05:10:38PM +0300, Eddy Petrisor wrote:
> > > > [...]
> > > > > 3)
On 8/17/05, Adam Heath <[EMAIL PROTECTED]> wrote:
> On Wed, 3 Aug 2005, Eddy Petrisor wrote:
>
> > On 8/3/05, Denis Barbier <[EMAIL PROTECTED]> wrote:
> > > On Tue, Jul 26, 2005 at 05:10:38PM +0300, Eddy Petrisor wrote:
> > > [...]
> > > > 3) in some cases the messages are so cryptical that rephra
On Wed, 3 Aug 2005, Eddy Petrisor wrote:
> On 8/3/05, Denis Barbier <[EMAIL PROTECTED]> wrote:
> > On Tue, Jul 26, 2005 at 05:10:38PM +0300, Eddy Petrisor wrote:
> > [...]
> > > 3) in some cases the messages are so cryptical that rephrasing them would
> > > be a
> > > much better solution than ad
> A quick test on dpkg-1.13.10 by running
> perl -pi -e 's/ohshite\(_\((".*?")\)/ohshite($1/g' */*.? dselect/*
> shows that removing _() in ohshite calls removes 273 messages (on a
> total number of 999 messages), and I for one won't miss them ;)
> If you are willing to make these changes, please
On Wed, Aug 03, 2005 at 09:33:18AM +0300, Eddy Petrisor wrote:
> On 8/3/05, Denis Barbier <[EMAIL PROTECTED]> wrote:
> > On Tue, Jul 26, 2005 at 05:10:38PM +0300, Eddy Petrisor wrote:
> > [...]
> > > 3) in some cases the messages are so cryptical that rephrasing them would
> > > be a
> > > much be
On 8/3/05, Denis Barbier <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 26, 2005 at 05:10:38PM +0300, Eddy Petrisor wrote:
> [...]
> > 3) in some cases the messages are so cryptical that rephrasing them would
> > be a
> > much better solution than adding automatic comments:
> >
> > message:
> > "unable
On Tue, Jul 26, 2005 at 05:10:38PM +0300, Eddy Petrisor wrote:
[...]
> 3) in some cases the messages are so cryptical that rephrasing them would be a
> much better solution than adding automatic comments:
>
> message:
> "unable to open tmpfile for vsnprintf"
>
> code:
> ...
> if (!file) {
>
On 7/27/05, Christian Perrier <[EMAIL PROTECTED]> wrote:
> Quoting Eddy Petrisor ([EMAIL PROTECTED]):
> > Hello,
> >
> > As I have said in at a previous time, I have started working on adding
> > comments in the dpkg code, in order to add automatic comments to the
> > translatable strings.
>
> WON
Quoting Eddy Petrisor ([EMAIL PROTECTED]):
> Hello,
>
> As I have said in at a previous time, I have started working on adding
> comments in the dpkg code, in order to add automatic comments to the
> translatable strings.
WONDERFUL.
If you can do it on your own TLA branch, that'd be great. See S
Eddy Petrisor wrote:
> The support is there, but the original phrasing makes the feature
> useless; As I said:> > > > > > Thus, the string
> > > "unhold: upgrade or leave uninstalled" is ambiguous (in
> how many are uninstalled?
Wouldn't
printf(ngettext("unhold: upgrade or leave uninstalled
On 7/26/05, Jacob Sparre Andersen <[EMAIL PROTECTED]> wrote:
> Eddy Petrisor wrote:
>
> > 2) in some languages forms like "3 installed packages", "1
> > installed package" and "6 installed packages" need three
> > different forms for the word "installed". Thus, the string
> > "unhold: upgrade or l
On 2005-07-26T17:30:00+0300, [EMAIL PROTECTED] wrote:
> Isn't there a feature for handling this problem in GNU
> Gettext?
printf(ngettext("%d file copied", "%d files copied", i), i);
And this ngettext makes its magic so this works in every language
(i.e. there is just right amount of different pl
Eddy Petrisor wrote:
> 2) in some languages forms like "3 installed packages", "1
> installed package" and "6 installed packages" need three
> different forms for the word "installed". Thus, the string
> "unhold: upgrade or leave uninstalled" is ambiguous (in
> this case might not be the case - I
Hello,
As I have said in at a previous time, I have started working on adding
comments in the dpkg code, in order to add automatic comments to the
translatable strings.
Unfortunately, I was caught in other issues with some translation
sychronizations, and have halted a little the work. Also, the
38 matches
Mail list logo
