> Date: Wed, 3 Aug 2022 14:36:58 -0700
> From: Per Bothner
>
> On 8/3/22 13:46, Patrice Dumas wrote:
> > This is not what we do in general for html/xhtml. For epub we always
> > emit utf8, as it is mandated by the standard, but for html/xhtml, we
> > use, in the default case, the input encoding
On Wed, Aug 03, 2022 at 03:08:09PM -0700, Per Bothner wrote:
>
>
> On 8/3/22 14:01, Patrice Dumas wrote:
> > On Wed, Aug 03, 2022 at 12:16:04PM -0700, Per Bothner wrote:
> > > Again - why? More specifically: why are you putting the html/xhtml file
> > > in a
> > > separate xhtml subdirectory? I
On Wed, Aug 03, 2022 at 02:36:58PM -0700, Per Bothner wrote:
> On 8/3/22 13:46, Patrice Dumas wrote:
> > This is not what we do in general for html/xhtml. For epub we always
> > emit utf8, as it is mandated by the standard, but for html/xhtml, we
> > use, in the default case, the input encoding fo
On 8/3/22 14:01, Patrice Dumas wrote:
On Wed, Aug 03, 2022 at 12:16:04PM -0700, Per Bothner wrote:
Again - why? More specifically: why are you putting the html/xhtml file in a
separate xhtml subdirectory? If you get rid of that, it seems you avoid the
problem.
No, the problem is not avoid
On 8/3/22 13:46, Patrice Dumas wrote:
This is not what we do in general for html/xhtml. For epub we always
emit utf8, as it is mandated by the standard, but for html/xhtml, we
use, in the default case, the input encoding for the output encoding.
I think that is a mistake.
It seems clear that i
Jean-Christophe Helary wrote:
On Aug 3, 2022, at 15:15, Patrice Dumas wrote:
Hello,
There are many uses of valign in HTML tables generated by texi2any.
They come from texi2html days. I did some tests, and the differences
with and without are not important. And more fundamentaly, I see lit
On Wed, Aug 03, 2022 at 01:49:25PM +0100, Gavin Smith wrote:
> On Wed, Aug 03, 2022 at 02:22:04PM +0200, Patrice Dumas wrote:
> > I like 1) better, but there is a risk of files having the same name but
> > in two different directories.
> >
> > Ideas, comments?
> >
>
> One idea is the images do n
On Wed, Aug 03, 2022 at 12:16:04PM -0700, Per Bothner wrote:
>
>
> On 8/3/22 11:48, Patrice Dumas wrote:
> > On Wed, Aug 03, 2022 at 09:13:31AM -0700, Per Bothner wrote:
> > > On 8/3/22 05:22, Patrice Dumas wrote:
> > > > In EPUB, the images are copied to a directory, such as
> > > > my_manual_ep
On Wed, Aug 03, 2022 at 09:10:32PM +0200, Jean-Christophe Helary wrote:
>
>
> > On Aug 3, 2022, at 15:15, Patrice Dumas wrote:
> >
> > Hello,
> >
> > There are many uses of valign in HTML tables generated by texi2any.
> > They come from texi2html days. I did some tests, and the differences
>
On Wed, Aug 03, 2022 at 12:08:15PM -0700, Per Bothner wrote:
> On 8/3/22 06:26, Patrice Dumas wrote:
> > The standard does not seems to clear on the encoding to use for the %
> > encodings. URI::Escape has uri_escape() and uri_escape_utf8. My
> > feeling is that the best would be to use first enc
On 8/3/22 11:48, Patrice Dumas wrote:
On Wed, Aug 03, 2022 at 09:13:31AM -0700, Per Bothner wrote:
On 8/3/22 05:22, Patrice Dumas wrote:
In EPUB, the images are copied to a directory, such as
my_manual_epub_package/EPUB/images/
The manual files are in
my_manual_epub_package/EPUB/xhtml/*.xhtm
> On Aug 3, 2022, at 15:15, Patrice Dumas wrote:
>
> Hello,
>
> There are many uses of valign in HTML tables generated by texi2any.
> They come from texi2html days. I did some tests, and the differences
> with and without are not important. And more fundamentaly, I see little
> point in try
On 8/3/22 06:26, Patrice Dumas wrote:
The standard does not seems to clear on the encoding to use for the %
encodings. URI::Escape has uri_escape() and uri_escape_utf8. My
feeling is that the best would be to use first encode to the output
encoding and then call URI::Escape uri_escape().
If I
> On Aug 3, 2022, at 15:29, Patrice Dumas wrote:
>
> Hello,
>
> I propose to replace the elements removed from HTML5, acronym and tt.
> acronym HTML element replaced by abbr, and tt by a span, where there is
> no semantics for the tt, for example with @t. This would lead to
>
>
>
>
> spa
On Wed, Aug 03, 2022 at 09:13:31AM -0700, Per Bothner wrote:
> On 8/3/22 05:22, Patrice Dumas wrote:
> > In EPUB, the images are copied to a directory, such as
> > my_manual_epub_package/EPUB/images/
> > The manual files are in
> > my_manual_epub_package/EPUB/xhtml/*.xhtml
> > and the paths to imag
On 8/3/22 05:22, Patrice Dumas wrote:
In EPUB, the images are copied to a directory, such as
my_manual_epub_package/EPUB/images/
The manual files are in
my_manual_epub_package/EPUB/xhtml/*.xhtml
and the paths to images in the XHTML files have ../images/ prepended.
Why? I don't see any such req
Hello,
I propose to replace the elements removed from HTML5, acronym and tt.
acronym HTML element replaced by abbr, and tt by a span, where there is
no semantics for the tt, for example with @t. This would lead to
span.t => font-family: monospace;
Does it looks ok?
--
Pat
Hello,
In general, hrefs generated by texi2any to Texinfo manuals, be it the
current manual or external manual, only contain ascii characters
acceptable in hrefs. However, for some other href, for file
names, or from @url{}, there could be any characters.
I think that it would be cleaner to per
Hello,
There are many uses of valign in HTML tables generated by texi2any.
They come from texi2html days. I did some tests, and the differences
with and without are not important. And more fundamentaly, I see little
point in trying to set that kind of information, unless there is an
obvious issu
On Wed, Aug 03, 2022 at 02:22:04PM +0200, Patrice Dumas wrote:
> I like 1) better, but there is a risk of files having the same name but
> in two different directories.
>
> Ideas, comments?
>
One idea is the images do not have to have the same base file name
as the source images. They could nam
Hello,
When the images are in subdirectories, like
@image{subdir/toto}
the resulting HTML references is like "subdir/toto.png".
In EPUB, the images are copied to a directory, such as
my_manual_epub_package/EPUB/images/
The manual files are in
my_manual_epub_package/EPUB/xhtml/*.xhtml
and the path
On Wed, Aug 03, 2022 at 04:30:49AM +, Werner LEMBERG wrote:
>
> > Also this: https://practicaltypography.com/bold-or-italic.html
>
> IMHO, these advices are not applicable for technical documentation,
> since different kinds of meta-ness *do* make sense.
>
Fair enough.
22 matches
Mail list logo
