Re: [PATCH] binary-io: do not treat set_binary_mode() on stdin/out/err as an error on OS/2

Hi KO, Thanks for the answers. > > * What is the result of isatty(1) > > a) for console output? > 1 > > > b) for pipe output? > 0 > > > c) for regular file output? > 0 > > > > > * What is the result of isatty(0) > > a) for console input? > 1 > > > b) for pipe input? > 0 > > >

Re: [PATCH] Make it possible to call canonicalize_filename_mode from C++.

Hi James, > diff --git a/lib/canonicalize.h b/lib/canonicalize.h > index 2ffa1f681..d21b5b203 100644 > --- a/lib/canonicalize.h > +++ b/lib/canonicalize.h > @@ -21,6 +21,10 @@ > > #define CAN_MODE_MASK (CAN_EXISTING | CAN_ALL_BUT_LAST | CAN_MISSING) > > +# ifdef __cplusplus > +extern "C" { >

Re: localized URLs

> Le 28 mai 2019 à 19:59, Bruno Haible a écrit : > > Support for a preference list of languages is part of the current web > standards. > [1] Oh wow, weighted languages... It feels like language theory :) Thanks, I had no idea. > However, I'm not sure I prefer the web pages that do dynami

Re: localized URLs

Akim Demaille wrote: > However, such support from the web site itself > is the surest way to be always up to date, even if you are on some old > distro with a piece of software that was released many years ago. Indeed. > If there's really demand, they could also support this "path" of languages.

Re: localized URLs

> Le 28 mai 2019 à 10:49, Bruno Haible a écrit : > > Hi Akim, > >> On the other end, it would be nice if the FSF supported something like >> '?locale=CODE' or '?lang=CODE', as some sites do, as it would relieve us >> from having to maintain some correspondance by hand. > > The only benefit t

Re: localized URLs

Hi Bruno, > Le 28 mai 2019 à 10:55, Bruno Haible a écrit : > > Akim Demaille wrote: >> I don't think errors in URL translations are more serious that plain errors >> in the translations (I fixed some of them in my own language that were even >> conveying incorrect semantics), or delicate pieces

[PATCH 2/2] Make it possible to call opendir_safer from C++.

* lib/dirent-safer.h: use extern "C". --- lib/dirent-safer.h | 8 1 file changed, 8 insertions(+) diff --git a/lib/dirent-safer.h b/lib/dirent-safer.h index 4d8e5ee92..6f6288e61 100644 --- a/lib/dirent-safer.h +++ b/lib/dirent-safer.h @@ -19,4 +19,12 @@ #include +# ifdef __cplusplu

[PATCH] Make it possible to call canonicalize_filename_mode from C++.

* lib/canonicalize.h: use extern "C". --- lib/canonicalize.h | 8 1 file changed, 8 insertions(+) diff --git a/lib/canonicalize.h b/lib/canonicalize.h index 2ffa1f681..d21b5b203 100644 --- a/lib/canonicalize.h +++ b/lib/canonicalize.h @@ -21,6 +21,10 @@ #define CAN_MODE_MASK (CAN_EXIS

Re: localized URLs

Akim Demaille wrote: > I don't think errors in URL translations are more serious that plain errors > in the translations (I fixed some of them in my own language that were even > conveying incorrect semantics), or delicate pieces of text such as the GPL > disclaimer excerpt. That's not the point.

Re: localized URLs

Hi Akim, > On the other end, it would be nice if the FSF supported something like > '?locale=CODE' or '?lang=CODE', as some sites do, as it would relieve us > from having to maintain some correspondance by hand. The only benefit that this syntax would have is that the PATTERN could be derived fro