Version: (using KDE Devel) Installed from: Compiled sources OS: OS X 1. po:47 reference: ⑤ cupsd.conf.template.cpp:327 Original: ⌘0 _: Do not translate the keyword between brackets (e.g. ServerName, ServerAdmin, etc.)\n <b>Browse allow/deny (BrowseAllow/BrowseDeny)</b>\n <p>\n <u>BrowseAllow</u>: specifies an address mask to allow for incoming browser\n packets. The default is to allow packets from all addresses.</p>\n <p>\n <u>BrowseDeny</u>: specifies an address mask to deny for incoming browser\n packets. The default is to deny packets from no addresses.</p>\n <p>\n Both \"BrowseAllow\" and \"BrowseDeny\" accept the following notations for\n addresses:</p>\n - to deny for incoming browser packets + to deny incoming browser packets from Clytie, Vietnamese translator (I added the Vietnamese translation a few days ago and didn't get around to reporting this until today: sorry)
I suppose that it is part of kdeprint.
It's very difficult to tell from the filename where it belongs, except, as you've surmised, this is a CUPS file and therefore to do with printing. Does that mean I should have reported it against kdeprint? The trouble is, I don't know these modules well. I don't even use KDE. So I'm more likely to be able to report typos against the file, than against the parent module: this file was in kdelibs. I hope that is still useful. :)
On Tuesday 14 March 2006 07:38, Clytie Siddall wrote: (...) > ------- Additional Comments From clytie riverland net au 2006-03-14 07:38 > ------- It's very difficult to tell from the filename where it belongs, > except, as you've surmised, this is a CUPS file and therefore to do with > printing. That is unfortunately a known problem. (Again something where we should try to find a solution for KDE4.) > Does that mean I should have reported it against kdeprint? It would have been better. Wrong user messages are in the source code, so KDE consider such a bug as being source code errors, so it should be reported in the original bug category. > > The trouble is, I don't know these modules well. I don't even use KDE. So > I'm more likely to be able to report typos against the file, than against > the parent module: this file was in kdelibs. Well, you can keep putting them in "i18n"; the only problem is that the bug report risks to stay there for long. As for the parent module, only very few KDE modules are categories in KDE Bugs, so that it is seldom a solution. > > I hope that is still useful. :) Have a nice day!
KDEPrint is obsolete, unmaintained and will never be revived. Closing all open bugs.