> Date: Fri, 26 Dec 2014 16:48:00 +
> From: Gavin Smith
> Cc: Texinfo
>
> I discovered this problem with the "gnucobpg.info" file that is part
> of GNU Cobol (downloadable at
> http://opencobol.add1tocobol.com/guides/), which has many CR-LF line
> endings (but not consistently). I don't know
On Thu, Dec 25, 2014 at 3:51 PM, Eli Zaretskii wrote:
> Today I discovered that the Info reader built from the current trunk
> cannot display any Info file that was produced natively on Windows (as
> opposed to Info files that come from distribution tarballs, which were
> produced on Unix). The r
> Date: Thu, 25 Dec 2014 18:05:25 +
> From: Gavin Smith
> Cc: Texinfo
>
> On Thu, Dec 25, 2014 at 3:51 PM, Eli Zaretskii wrote:
> > Today I discovered that the Info reader built from the current trunk
> > cannot display any Info file that was produced natively on Windows (as
> > opposed to
> Date: Thu, 25 Dec 2014 20:23:01 +0200
> From: Eli Zaretskii
> Cc: jad...@yahoo.com.au, bug-texinfo@gnu.org
>
> > Please go ahead and commit any of the changes you've posted for
> > Windows
>
> OK, will do.
Done.
> Date: Thu, 25 Dec 2014 20:01:03 +0200
> From: Eli Zaretskii
> Cc: bug-texinfo@gnu.org
>
> > Date: Thu, 25 Dec 2014 17:32:17 +
> > From: Gavin Smith
> > Cc: Texinfo
> >
> > On Wed, Dec 24, 2014 at 5:41 PM, Eli Zaretskii wrote:
> > > . memrchr and asprintf are being used, but the corres
> Date: Fri, 26 Dec 2014 19:13:24 +1000
> From: Jason Hood
> CC: bug-texinfo@gnu.org
>
> On 26/12/2014 18:37, Eli Zaretskii wrote:
> > The speed is fine on my machines, and cputs does NOT write one
> > character at a time, it uses WriteConsole. Only cprintf writes one
> > character at a time.
>
On 26/12/2014 18:37, Eli Zaretskii wrote:
> The speed is fine on my machines, and cputs does NOT write one
> character at a time, it uses WriteConsole. Only cprintf writes one
> character at a time.
Not according to the Visual Studio 2010 source, which is presumably
similar to what MSVCRT.DLL wou
> Date: Fri, 26 Dec 2014 11:44:26 +1000
> From: Jason Hood
> CC: bug-texinfo@gnu.org
>
> On 26/12/2014 2:00, Eli Zaretskii wrote:
> > [...] when the output encoding,
> > as determined by the current console codepage, is UTF-8 or UTF-7. For
> > these 2 encodings, the _only_ way of delivering text
Ineiev writes:
> Still it's an issue.
OK, have it your way. I suspect that you will not decrease the number
of complaints by much, but *shrug* it won't be my problem.
Ineiev writes:
> GNU webmasters did receive reports from such visitors. I'm sure many
> cases were not reported.
If GNU websites are correctly configured and send the correct MIME
charset in the Content-Type in the HTTP headers, the users should not
have a problem, and if they do have such prob
Ineiev writes:
> On Wed, Dec 24, 2014 at 12:27:25PM +0900, Stephen J. Turnbull wrote:
> > AFAIK the encoding declaration is optional, defaulting to UTF-8. In
> > that case, we can (and IMHO *should*, but I am no longer an expert on
> > current encoding practice) require that our software gener
11 matches
Mail list logo
