Hello,
On Wed, Dec 24, 2014 at 12:59:32AM +0700, Yuri Khan wrote:
What browsers are there that do not support CSS *and* at the same time
have the capability of displaying proportional fonts?
They may not be able to exactly display proportional fonts, but they
may highlight it in a different
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 generate UTF-8
and omit the
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 reader says it cannot find the Top node in any
such Info file.
Date: Fri, 07 Nov 2014 17:55:36 +1000
From: Jason Hood jad...@yahoo.com.au
Find attached a patch (based on the 5.2 release; apply with -p1) to
address some issues with the Windows port:
* enhances the gnulib stat replacement to provide meaningful values for
st_ino st_dev, thus
Date: Fri, 07 Nov 2014 17:55:36 +1000
From: Jason Hood jad...@yahoo.com.au
* enhances the gnulib stat replacement to provide meaningful values for
st_ino st_dev, thus enabling detection of duplicate directories;
This was reported by Jason to Gnulib, but I see no responses to that
message
Date: Fri, 07 Nov 2014 17:55:36 +1000
From: Jason Hood jad...@yahoo.com.au
* improves the visual bell;
This patch, which I reproduce below rebased to the current trunk,
corrects a real bug with the visual bell implementation in the current
code, and I recommend to commit it:
---
Date: Fri, 07 Nov 2014 17:55:36 +1000
From: Jason Hood jad...@yahoo.com.au
* improves screen output (faster, correctly displays both UTF-8 and
latin1 files).
This part of the patch was the most complex to deal with. Its main
part deals with displaying non-ASCII characters on the Windows
On Wed, Dec 24, 2014 at 5:53 PM, Eli Zaretskii e...@gnu.org wrote:
While working on the MinGW port of Info, I noticed an annoying
problem: the welcome message displayed in the echo area when the
reader starts up causes the entire display to scroll up one line,
which messes up the display until
On Fri, Dec 26, 2014 at 12:58:24AM +0900, Stephen J. Turnbull wrote:
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
On Fri, Dec 26, 2014 at 02:09:33AM +0900, Stephen J. Turnbull wrote:
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
On Wed, Dec 24, 2014 at 5:41 PM, Eli Zaretskii e...@gnu.org wrote:
. memrchr and asprintf are being used, but the corresponding Gnulib
modules were not imported, and so the build on any platform that
lacks these is broken.
I've tried to add these gnulib modules.
On Wed, Dec 24, 2014 at 5:41 PM, Eli Zaretskii e...@gnu.org wrote:
In addition, there are non-fatal warnings: libiconv routines are
called with 'char **' arguments where the functions expect to get a
'const char **' argument, and there's one case of conflicting
prototypes in pcterm.c. Patch
Date: Thu, 25 Dec 2014 17:33:59 +
From: Gavin Smith gavinsmith0...@gmail.com
Cc: Texinfo bug-texinfo@gnu.org
On Wed, Dec 24, 2014 at 5:41 PM, Eli Zaretskii e...@gnu.org wrote:
In addition, there are non-fatal warnings: libiconv routines are
called with 'char **' arguments where the
Date: Thu, 25 Dec 2014 17:32:17 +
From: Gavin Smith gavinsmith0...@gmail.com
Cc: Texinfo bug-texinfo@gnu.org
On Wed, Dec 24, 2014 at 5:41 PM, Eli Zaretskii e...@gnu.org wrote:
. memrchr and asprintf are being used, but the corresponding Gnulib
modules were not imported, and so
On Thu, Dec 25, 2014 at 3:51 PM, Eli Zaretskii e...@gnu.org 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
On Thu, Dec 25, 2014 at 3:55 PM, Eli Zaretskii e...@gnu.org wrote:
Date: Fri, 07 Nov 2014 17:55:36 +1000
From: Jason Hood jad...@yahoo.com.au
* enhances the gnulib stat replacement to provide meaningful values for
st_ino st_dev, thus enabling detection of duplicate directories;
This was
Date: Thu, 25 Dec 2014 18:11:21 +
From: Gavin Smith gavinsmith0...@gmail.com
Cc: Jason Hood jad...@yahoo.com.au, Texinfo bug-texinfo@gnu.org
On Thu, Dec 25, 2014 at 3:55 PM, Eli Zaretskii e...@gnu.org wrote:
Date: Fri, 07 Nov 2014 17:55:36 +1000
From: Jason Hood jad...@yahoo.com.au
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 to the Windows
console is by using the wide APIs, which accept UTF-16 encoded text.
Actually,
18 matches
Mail list logo
