On Mon, Jul 9, 2012 at 7:54 AM, Lennart Poettering
wrote:
> UTF8 is a superset of ASCII
Yes, for true 7-bit ASCII. Unfortunately, many systems interpret
"ASCII" to be a license for use of Latin-1 (and other traditional
8-bit character sets) in a way that's not safe to read as UTF-8.
Clearly speci
On Fri, 29.06.12 15:09, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> > It shouldn't be ignored, but journalctl currently just skips over it in
> > the normal output, since there is nothing to show. The data should
> > actually be stored on disk just fine, and the verbose mode of journa
On Fri, Jun 29, 2012 at 6:09 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> Let's just hope that this doesn't deteriorate into web-style 90%-successful
> encoding-guessing-game.
Indeed. It would be great to just go UTF-8 clean for text and treat
failures as binary data. UTF-8 is identical to ASCII in t
On 06/29/2012 02:49 PM, Lennart Poettering wrote:
> On Fri, 29.06.12 14:39, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
>> Hi,
>>
>> I've been playing around with the python journald client, and I'm not
>> entirely clear on a few API details. I think it would be nice if the new
>> doc
On Fri, 29.06.12 14:39, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> Hi,
>
> I've been playing around with the python journald client, and I'm not
> entirely clear on a few API details. I think it would be nice if the new
> documentation cleared them up:
>
> 1. If the iovect passed t
On 06/27/2012 11:28 AM, Lennart Poettering wrote:
> On Tue, 26.06.12 17:31, David Strauss (da...@davidstrauss.net) wrote:
>
>> I would like to document the native journald API with some usage
>> examples. Would this be best handled in the form of a man page,
>> comments in the main header file, or
On Tue, 26.06.12 17:31, David Strauss (da...@davidstrauss.net) wrote:
> I would like to document the native journald API with some usage
> examples. Would this be best handled in the form of a man page,
> comments in the main header file, or elsewhere?
Awesome, much appreciated!
I think this wou
David Strauss writes:
> I would like to document the native journald API with some usage
> examples. Would this be best handled in the form of a man page,
> comments in the main header file, or elsewhere?
Personally, I'd love to have a man page (or header comments, this
doesn't really matter) fo
I would like to document the native journald API with some usage
examples. Would this be best handled in the form of a man page,
comments in the main header file, or elsewhere?
--
David Strauss
| da...@davidstrauss.net
___
systemd-devel mailing list