Current HTMLDOC supports UTF-8 for Western languages...
On Fri, 03 Mar 2006 02:42:23 +0800 Dan Jacobson wrote:
> Package: htmldoc
> Version: 1.8.24-2
> Severity: wishlist
>
> Support charset UTF-8.
>
>
_________
Michael S
reeType-based font drawing
> librar
> ii xlibs6.8.2.dfsg.1-11 X Window System client libraries
> m
> ii zlib1g 1:1.2.3-9 compression library - runtime
>
> htmldoc recommends no packages.
>
> -- no debconf information
>
>
_
Michael Sweet, Senior Printing System Engineer
, cups.bugs, etc.) will not be returning,
we will just have mailman-based mailing lists going forward...
_____
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
ssuring the folks that are doing the security
audit of the new cups.org server to sign off on it so I can put the public bug
reporter back online. It is a major pain in the butt for me as well, I assure
you!
_____
Michael Sweet, Senior Printin
hanges here, and there is a bug fix for a related issue in the
upcoming 1.6.4 release (probably will go live next week) to make sure we pass
the "correct" MIME media type to the server. (whether it understands that
media type is another matter...)
_____
Dicier,
Too late, 1.6.3 went live last Friday. But I'll add this for the next releases
- dunno if we will have 1.6.4 but definitely for 1.7.0. And I now have a bug
tracking support for quirks files for the USB backend which will allow users
and driver developers to add to the quirks list witho
On Jul 9, 2013, at 11:46 AM, Michael Sweet wrote:
> OK, then it sounds like the /version=1.1 support isn't kicking in for
> client.conf for some reason. Investigating...
>
>
> On 2013-07-09, at 11:09 AM, Vincent Lefevre wrote:
>
>> On 2013-07-09 10:46:15 -0400,
OK, then it sounds like the /version=1.1 support isn't kicking in for
client.conf for some reason. Investigating...
On 2013-07-09, at 11:09 AM, Vincent Lefevre wrote:
> On 2013-07-09 10:46:15 -0400, Michael Sweet wrote:
>> Strange, what happens if you do:
>>
>>
Vincent,
Strange, what happens if you do:
lpr -H lip-printserver1.lip.ens-lyon.fr/version=1.1 bfrange-test.pdf
On 2013-07-09, at 5:17 AM, Vincent Lefevre wrote:
> On 2013-07-08 07:30:45 -0400, Michael Sweet wrote:
>> And the same patch for CUPS 1.6.x...
>
> This patch
And the same patch for CUPS 1.6.x...
rdar14290628-1.6.patch
Description: Binary data
On Jul 2, 2013, at 9:25 AM, Michael Sweet wrote:
> Vincent,
>
> On 2013-06-27, at 6:06 PM, Vincent Lefevre wrote:
>> ...
>> Then I assume that lpq could use cupsGetNamedDest like lp a
ck this issue in the same bug and make them all use cupsGetNamedDest
> to get the default printer.
>
> _
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
_
Michael Sweet, Senior Printing System Engineer, PWG Chair
Dest to
get the default printer.
_________
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
>
_
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
. Then we needed user-savable options and defaults. Then
we needed to be able to set system-side defaults. Then we wanted a
last-used-printer scheme if no user default was set. Aaarrrggghhh!
(http://www.youtube.com/watch?v=avpFGlv7iw8)
__
)
{
+case HTTP_ERROR :
+s = strerror(errno);
+break;
case HTTP_CONTINUE :
s = _("Continue");
break;
_____
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
To UNSUBSCRIBE, email to debian
Dest(name, instance, num_dests, *dests)) != NULL)
- dest->is_default = 1;
+num_dests = cupsRemoveDest(dest->name, dest->instance, num_dests,
+ dests);
+ }
}
/*
_________
Michael Swee
Daniel,
On 2013-06-21, at 2:20 PM, "Daniel Richard G." wrote:
> On Fri, 2013 Jun 21 9:29-0400, Michael Sweet wrote:
>>
>> Well, before we go off and spend extra engineering time on this, how
>> widespread is the use of client.conf in the Linux world? On OS X it
ServerName hostname-or-ip-address[:port]
ServerName /domain/socket
Specifies the address and optionally the port to use when connect-
ing to a server running CUPS 1.4 or later. Note: Not supported on
OS X 10.7 or later.
__
Cheers,
>
> Didier
>
> [0] http://bugs.debian.org/cgi-
> bin/bugreport.cgi?msg=5;filename=http_errormsg.patch;att=1;bug=645436
_
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
erwise, for
>> instance, if a document is sent to a private printer but something
>> goes wrong like here, it may end up on a public printer!
>>
>> [*] by either a lpoptions config file or an environment variable.
>> The -P lpr option is handled directly in lpr, and cupsGe
Vincent,
On 2013-06-20, at 11:05 AM, Vincent Lefevre wrote:
> On 2013-06-20 10:46:00 -0400, Michael Sweet wrote:
>> Given that this is only a problem for users depending on the
>> ServerName directive in client.conf, it seemed much more practical
>> (and reliable) to have t
ractical (and reliable) to have
the user/administrator specify any version limitations there.
_________
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject o
client.conf
(looking forward to getting the cups.org bug tracker back up...)
_
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
(and probably should) change lpq to report the real
error, but that will just yield:
lpq: Bad Request
And since "Bad Request" can be caused by a grab bag of issues, we can't just
map it to "version not supported".
Didier, Sam,
On 2013-06-20, at 8:41 AM, Didier 'OdyX' Raboud wrote:
> Control: tags -1 +upstream
>
> Hi Sam, and thanks for your bugreport,
>
> I'm hereby CC'ing Michael Sweet, Cups upstream author.
>
> Le jeudi, 20 juin 2013 13.59:37, Sam M
Marc,
On 2012-11-28, at 9:00 AM, Marc Deslauriers
wrote:
> On 12-11-27 11:38 PM, Michael Sweet wrote:
>> After looking at this patch in detail, it doesn't actually prevent users in
>> the lpadmin group from modifying cupsd.conf and performing the specified
>> privi
eck: if we are running as root, require the defaults.
________
Michael Sweet, Senior Printing System Engineer, PWG Chair
an install
their own versions of the cups packages. Thoughts?
Sent from my iPad
On 2012-11-28, at 4:54 AM, Didier 'OdyX' Raboud wrote:
> Le mercredi, 28 novembre 2012 05.38:58, Michael Sweet a écrit :
>> After looking at this patch in detail, it doesn't actually prevent
patch we plan on using.
>
> Marc.
>
________
Michael Sweet, Senior Printing System Engineer, PWG Chair
Note: disabling he web interface is not enough, you also need to disable HTTP
PUT in cupsd, which takes care of cupsctl too. However, since that also
disables helpful things like changing the log level you might want to
reconsider fixing things that way...
Sent from my iPad
On 2012-11-27, at
files are in one location. The patch will be very
very messy and hard to maintain.
__
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
L4223
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 2012-11-19, at 1:59 AM, Yves-Alexis Perez wrote:
> On dim., 2012-11-11 at 17:53 +0100, Didier 'OdyX' Raboud wrote:
>> Hi Michael,
>>
>> Le dimanche, 11 novembre 2012 14.57:05, Michael Sweet a écrit :
>>> Lest we forget why we run cupsd as root, her
All,
Lest we forget why we run cupsd as root, here are a few reasons:
1. Authentication (both Kerberos and PAM)
2. Privileged ports for LPD
3. Access to device files for printing
4. Privilege separation from/for filters.
1 and 4 basically require running as root unless we do a hairy mess of meta
f us a lot
of wasted time!
Thanks!
--
__________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Document Software http://www.easysw.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
35 matches
Mail list logo
