Re: yelp tracker issue on Texinfo HTML documentation

2024-12-24 Thread Per Bothner
ng a GUI. If you must use a terminal rather than a GUI, there is the option of using emacs with a modified info-mode that wraps eww-mode (or similar). (That is my suggested long-term roadmap for getting rid of the info file format - though I'm unlikely to work on it myself.) -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: yelp tracker issue on Texinfo HTML documentation

2024-12-24 Thread Per Bothner
tern. I am not convinced it added anything. However, adding hooks that can be be overridden by an embedding browser would be more local and modest. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: yelp tracker issue on Texinfo HTML documentation

2024-12-24 Thread Per Bothner
ight be licensing concerns with the GPL3-only js-info; if so re-licensing js-info might be worth considering. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Flood of commits from July?

2024-10-08 Thread Per Bothner
e felt free to use C++ constructs. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Flood of commits from July?

2024-10-07 Thread Per Bothner
On 10/7/24 12:00 PM, Eli Zaretskii wrote: From: Per Bothner First, compared to C++ to Rust, moving from C to C++ is much more modest of terms of code changes as well as new skills needed. That was maybe true 10 or 15 years ago, but is no longer true: C++ got a lot of additional baggage

Re: Flood of commits from July?

2024-10-07 Thread Per Bothner
ry maintainer who is strongly opposed to C++, and unwilling to work on C++ code. So unless those things change, Texinfo will stick with C and Perl. And that's OK. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Flood of commits from July?

2024-10-06 Thread Per Bothner
t C to C++ than to Rust. Of course rewriting the package is a very large job, and should not be decided upon lightly. However, converting existing C code to (working but not idiomatic) C++ is pretty easy. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Flood of commits from July?

2024-10-05 Thread Per Bothner
C, at least for texinfo. (I have written and maintained a lot of code in both. For what it's worth, gcc was converted to a C++ implementation some time ago, not sure when.) Perhaps it is appropriate to use a "legacy" programming language to implement a "legacy" documentation

Re: Flood of commits from July?

2024-10-05 Thread Per Bothner
/wiki/Resource_acquisition_is_initialization and of course: (5) Ultimately get rid of Perl, which fewer and fewer people know. This stays away from the more complicated features of C++. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: EPUB 3.3 spec conformity issues

2024-08-21 Thread Per Bothner
the work. It will happen when it happens. Hopefully soon. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: implementation language [was: library for unicode collation in C for texi2any?]

2023-10-16 Thread Per Bothner
On 10/16/23 05:36, Gavin Smith wrote: On Sun, Oct 15, 2023 at 12:00:51PM -0700, Per Bothner wrote: I'm far from a C++ expert these days, but some ideas: * First of course you can define some helper methods: class TargetElement { Extra *extra; Command *unit_command() { return

Re: implementation language [was: library for unicode collation in C for texi2any?]

2023-10-15 Thread Per Bothner
, and I don't know if this further than you want to go in terms of C++-isms. I can do some research, though. * Perhaps use a subclass for the "extra" fields: class TargetElementWithExtra :: TargetElement { Command *unit_command; } if (auto te = dynamic_cast(target_element)) { // te is target_element safely cast to TargetElementWithExtra*. } -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: implementation language [was: library for unicode collation in C for texi2any?]

2023-10-14 Thread Per Bothner
On 10/14/23 09:12, Patrice Dumas wrote: On Thu, Oct 12, 2023 at 10:25:23AM -0700, Per Bothner wrote: C++ has a more extensive and useful standard library than C. I guess there is an hash map, but I am not sure that we would need much more. In addition to hash maps and maybe some other

Re: implementation language [was: library for unicode collation in C for texi2any?]

2023-10-14 Thread Per Bothner
or operator that occurs in a program. Of course not. In C++ function are by default monomorphic (non-virtual). In my domterm backend the keyword 'virtual' is not used at all. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: implementation language [was: library for unicode collation in C for texi2any?]

2023-10-14 Thread Per Bothner
methods.) If I had started with C++, or if I were more fluent in C++ than I am now, it would look different. But the current hybrid is fine. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: implementation language [was: library for unicode collation in C for texi2any?]

2023-10-12 Thread Per Bothner
is much easier to make a large C++ program well-structured and maintainable: Classes help immeasurably, as do namespaces. -- --Per Bothner p...@bothner.com http://per.bothner.com/

implementation language [was: library for unicode collation in C for texi2any?]

2023-10-12 Thread Per Bothner
een a mistake; switching to C seems like it would be another mistake. But hey - I'm not the one doing the work. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: control over sectioning and splitting

2023-07-27 Thread Per Bothner
/DomTerm/blob/master/doc/DomTerm.texi I don't remember what changes if any I had to make - probably the js/info.js around November 2022. -- --Per Bothner p...@bothner.com http://per.bothner.com/

using hashes for internal URLs

2022-12-15 Thread Per Bothner
The re-mapping table would be hidden if using JavaScript. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: info.js demo on Texinfo manual updated on website

2022-11-30 Thread Per Bothner
quite hard to deal with, and I confess I don't understand what problem it is intended to solve. I don't think it's the right logic for dealing with "window-title" messages. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: info.js demo on Texinfo manual updated on website

2022-11-29 Thread Per Bothner
mmit message. I believe best practice is for the first line of a commit message to be a self-contained short summary, followed by an empty line and further details (if any). So some editing of a ChangeLog entry is usually appropriate before using it as a commit message. -- --Per Bothne

Re: info.js demo on Texinfo manual updated on website

2022-11-29 Thread Per Bothner
suggested, because there is an index entry with that node as its target. Could you try the attached patch? I also implemented sub-entry handling while I was in that area. Optionally, I suggest a wider width for the text-entr box - see the info.css part of the patch. -- --Per B

Re: info.js demo on Texinfo manual updated on website

2022-11-27 Thread Per Bothner
it's useful as an example. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: info.js demo on Texinfo manual updated on website

2022-11-27 Thread Per Bothner
On 11/27/22 12:48, Per Bothner wrote: On 11/27/22 12:24, Gavin Smith wrote: The main other problem is updating the contents sidebar after an index search.  You can see it at It would be good to have this fixed before the 7.0.1 bug-fix release. I do not know if I will have time or be able

Re: info.js demo on Texinfo manual updated on website

2022-11-27 Thread Per Bothner
ng at it. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: @subentry, @seealso and @seenentry better formatted in HTML

2022-11-21 Thread Per Bothner
en there is a new initial character. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: @subentry, @seealso and @seenentry better formatted in HTML

2022-11-20 Thread Per Bothner
On 11/20/22 13:47, Patrice Dumas wrote: On Sun, Nov 20, 2022 at 01:35:33PM -0800, Per Bothner wrote: Before I do that, I suggest cleaning up the generated html a bit, as discussed: - Get rid of the dummy table cells used for indentation. The first column is the letter column. It is not

Re: @subentry, @seealso and @seenentry better formatted in HTML

2022-11-20 Thread Per Bothner
at least removing the class attribute. (Whichever is preferable may depend on the line is styled, such as when table borders are added.) -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: @subentry, @seealso and @seenentry better formatted in HTML

2022-11-19 Thread Per Bothner
dds extra space between elements. Margin (applied to ) doesn't seem to affect the size/spacing of table cells. Specifically, the following doesn't work: td.printindex-index-section { margin-left: 2em } However, this works: td.printindex-index-section a { margin-left: 2em } -

Re: @subentry, @seealso and @seenentry better formatted in HTML

2022-11-19 Thread Per Bothner
in, as long as there is a clean well-defined structure: It is easy to tell entries, subentries, and subsubentries apart, and they're in the "obvious" order. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: info.js demo on Texinfo manual updated on website

2022-11-18 Thread Per Bothner
ks = document.querySelectorAll ("div.printindex td a"); I don't know if this is the right thing - i.e. if it matches all the indices we need. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: info.js demo on Texinfo manual updated on website

2022-11-18 Thread Per Bothner
On 11/18/22 15:48, Patrice Dumas wrote: On Fri, Nov 18, 2022 at 03:19:23PM -0800, Per Bothner wrote: Before, when I converted the DomTerm manual to html the output contained: DomTerm - a terminal emulator and console using DOM and JavaScript This is now gone. Looks a change in the

Re: info.js demo on Texinfo manual updated on website

2022-11-18 Thread Per Bothner
default to the title from @settitle. info.js looks for an element whose class contains "settitle". Before, when I converted the DomTerm manual to html the output contained: DomTerm - a terminal emulator and console using DOM and JavaScript This is now gone. Looks a change in th

Re: Status of texinfo/js/yarn.lock ?

2022-11-16 Thread Per Bothner
On 11/16/22 16:51, Per Bothner wrote: For what it's work, I just updated to Fedora 37, which broke 'git pull' from Savannah: ... ... Same problem with GitLab, but GitHub works OK.  Probably some new keys need to be uploaded - but not today. Actually, GitHub was also bro

Re: Status of texinfo/js/yarn.lock ?

2022-11-16 Thread Per Bothner
the correct access rights and the repository exists. Same problem with GitLab, but GitHub works OK. Probably some new keys need to be uploaded - but not today. (I did do a 'git pull' before updating Fedora, so i do have a recent snapshot.) -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Status of texinfo/js/yarn.lock ?

2022-11-13 Thread Per Bothner
hand". However, figuring out the right files isn't completely obvious, so we may leave it as-is for now. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Status of texinfo/js/yarn.lock ?

2022-11-13 Thread Per Bothner
it works pretty well), though I have some things I'd like to change if/when I get time. However, the directory seems to have some old crud and could probably be cleaned up. Specifically, I don't think yarn.lock is needed or used at this point. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: url protection

2022-08-05 Thread Per Bothner
ld be.) -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: url protection

2022-08-05 Thread Per Bothner
crud. Certainly if we have to add a new option/switch to support overriding the default output encoding then it is not worth it. Just switch the output to utf8, change documentation, and rip out the old code. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: url protection

2022-08-05 Thread Per Bothner
} } if (pass == 0) { if (bad_count == 0) return NULL; size_t in_size = (char*) p - in; out = challoc(in_size + 2 * bad_count + 1); } else *q = 0; } return out; } -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: images subdirectories in epub

2022-08-03 Thread Per Bothner
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

Re: url protection

2022-08-03 Thread Per Bothner
/Internationalized_Resource_Identifier#Compatibility -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: images subdirectories in epub

2022-08-03 Thread Per Bothner
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

Re: url protection

2022-08-03 Thread Per Bothner
uri_escape_utf8 or uri_escape depends on whether conversion to utf8 has already been done. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: images subdirectories in epub

2022-08-03 Thread Per Bothner
rated using the docbook xsl stylesheets) contains: mimetype META-INF/ META-INF/container.xml OEBPS/ OEBPS/index.html OEBPS/Unicode.xhtml OEBPS/Sequences.xhtml ... OEBPS/images/ OEBPS/images/border-1.png OEBPS/images/polygon-1.png -- --Per Both

Re: control over sectioning and splitting

2022-01-23 Thread Per Bothner
nodes: I.e. the next @node command would have to be followed by a sectioning comand at the same or higher level. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: error with autogen.sh probably related to gnulib update

2022-01-16 Thread Per Bothner
rated automatically. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: change in the sectioning commands div extent classes

2022-01-12 Thread Per Bothner
associated to the section heading element. It may require some change in the javascript, maybe? I did a little testing, and found no problems. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: permanent links using #fragment names

2022-01-09 Thread Per Bothner
-style URL it's a bit trickier: We could *assume* there is a redirection page NAME.html and load that, and count on redirection to take us to the correct page. However I'm not sure how robust that is - plus it requires another round-trip. Probably better to put an index in the top page. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: permanent links using #fragment names

2022-01-09 Thread Per Bothner
ll take them to the correct file and location. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: permanent links using #fragment names

2022-01-09 Thread Per Bothner
On 1/9/22 10:28, Gavin Smith wrote: On Sun, Jan 09, 2022 at 09:32:38AM -0800, Per Bothner wrote: An idea I've been mulling: Currently, we handle changes in node structure by generating extra stub pages that redirect to the correct location. This works, but it's a bit clunky. For

Re: permanent links using #fragment names

2022-01-09 Thread Per Bothner
"emacs#Outline-Search" and the latter would be the preferred ("perma-link") URL. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: permanent links using #fragment names

2022-01-09 Thread Per Bothner
On 1/9/22 09:45, Eli Zaretskii wrote: Date: Sun, 9 Jan 2022 09:32:38 -0800 From: Per Bothner A related change is that we should change how info node/anchor names are mapped into URLs to use standard %-encoding. This would make URL cleaner and more readable. For continuity, we could map

permanent links using #fragment names

2022-01-09 Thread Per Bothner
nal ids such as the "-toc-foo" or "-def-printf". (I've suggested this before, I'm pretty sure, but I think it makes sense to co-ordinate these changes, at least for a specific manual.) -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: The HTML-Info initiative

2021-12-27 Thread Per Bothner
On 12/27/21 12:39, Gavin Smith wrote: On Mon, Dec 27, 2021 at 09:07:21AM -0800, Per Bothner wrote: It seems unaware of and not making use of info.js. Integration with info.js would be nice - at the very least disable the latter's sidebar and other duplicated functionality. Another d

Re: The HTML-Info initiative

2021-12-27 Thread Per Bothner
fo.js. Integration with info.js would be nice - at the very least disable the latter's sidebar and other duplicated functionality. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: epub init file, and questions

2021-12-26 Thread Per Bothner
can't have math, etc etc. - though a few terminals do support images.) Instead, an info-reading application that uses an embedded browser (such as webkitgtk) seems to make more sense. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: id attributes for header elements

2021-12-26 Thread Per Bothner
On 12/26/21 12:04, Patrice Dumas wrote: On Sun, Dec 26, 2021 at 11:24:59AM -0800, Per Bothner wrote: I believe putting the link on the sectioning command is slightly better (more semantically meaningful and easier to work with) than putting it before - and it is never worse. I agree, and

Re: epub init file, and questions

2021-12-26 Thread Per Bothner
On 12/25/21 22:48, Eli Zaretskii wrote: Your comments are all on-point, but I'll just add a few notes. Date: Sat, 25 Dec 2021 11:44:34 -0800 From: Per Bothner Note that using eww-mode running in a terminal displays texi2any-generated html work pretty decently, so that could potent

Re: id attributes for header elements

2021-12-26 Thread Per Bothner
On 12/26/21 10:29, Patrice Dumas wrote: On Sun, Dec 26, 2021 at 10:08:50AM -0800, Per Bothner wrote: I don't remember, and I don't see how it could be better for navigation.. It was some time ago, at least some people expected the link to point to the start of the header, and

Re: use for hancors without content, not

2021-12-26 Thread Per Bothner
. For those reasons, it still seems to me that is better than and actually the best choice among elements. Using this way makes me a little uncomfortable, but I don't have a strong objection. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: id attributes for header elements

2021-12-26 Thread Per Bothner
On 12/26/21 09:30, Patrice Dumas wrote: On Sat, Dec 25, 2021 at 02:10:29PM -0800, Per Bothner wrote: Two requests: (1) Don't generates the implicit id="Electron-1" when it immediately follows an explicit id="Electron". I do not think that it is a good idea, the @an

Re: use for hancors without content, not

2021-12-26 Thread Per Bothner
presents a placeholder for where a link might otherwise have been placed, if it had been relevant, consisting of just the element's contents." https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a does not suggest or give any examples of using without an href attribute. --

id attributes for header elements

2021-12-25 Thread Per Bothner
easier post-processing, such as by JavaScript or XSLT. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: epub init file, and questions

2021-12-25 Thread Per Bothner
html-supporting info mode. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: epub init file, and questions

2021-12-25 Thread Per Bothner
easonable to include info.js in an epub document. You should be able to unzip an epub (or use a web server that does so on-the-fly); if you then browse to the top page, you should get an experience more-or-less the same as browsing plain html, including using info.js if that was included. --

Re: info.js bugs

2021-12-24 Thread Per Bothner
ey events would get passed to the minibuffer element after it got focus. Seems to be fixed by adding a call to preventDefault on the keydown event. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: XHTML validation (was: texi to epub)

2021-12-20 Thread Per Bothner
ation (amongst others). For more details, please see the WHATWG FAQ. Work on this specification is also done at the WHATWG. The W3C HTML working group actively pursues convergence with the WHATWG, as required by the W3C HTML working group charter. -- --Per Bothner p...@bot

Re: texi to epub

2021-12-19 Thread Per Bothner
concatenation with ">") but faster in the USE_XML_SYNTAX case (avoid the regex substitution), but neither likely to be measurable since I'm also guessing it's not called that frequently. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: texi to epub

2021-12-18 Thread Per Bothner
) for HTML5. Maybe try the online version first: https://validator.w3.org/nu/ If it seems helpful you can download and build a local version. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: texi to epub

2021-12-18 Thread Per Bothner
On 12/18/21 14:33, Patrice Dumas wrote: On Wed, Dec 15, 2021 at 05:21:26PM -0800, Per Bothner wrote: Emacs nxml mode should be sufficient to check well-formedness. Is there documentation on how use nxml mode to check well-formedness from the command line? I cannot find any information on

Re: texi to epub

2021-12-18 Thread Per Bothner
e to know which elements have empty content (hr) and which don't (a). -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Replace HTML4 doctype declaration

2021-12-18 Thread Per Bothner
hat nobody cares about anymore. Does anybody object if I go and change texi2any to output this instead of the HTML4 Transitional doctype? I think it would make sense. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Directory names hard-coded in Texinfo Perl scripts

2021-12-18 Thread Per Bothner
ix is /tmp/.mount_DomTerfjMAQ5/usr/ . -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: texi to epub

2021-12-18 Thread Per Bothner
poposal is still reasonable: https://lists.gnu.org/archive/html/bug-texinfo/2021-09/msg0.html -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Directory names hard-coded in Texinfo Perl scripts

2021-12-17 Thread Per Bothner
Perl FindBin module and the C whoami package exist. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Directory names hard-coded in Texinfo Perl scripts

2021-12-17 Thread Per Bothner
file "../share/texinfo/foo.info" doesn't work, since that is relative to $PWD *unless* there is logic to change the effective $PWD. And how do figure out how what to change the $PWD to? You do something like my example code - or use a library that does something similar. --

Re: texi to epub

2021-12-16 Thread Per Bothner
? -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Directory names hard-coded in Texinfo Perl scripts

2021-12-16 Thread Per Bothner
For DomTerm (https://domterm.org) whose main executable is C/C++ I use whereami: https://github.com/gpakosz/whereami -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: texi to epub

2021-12-16 Thread Per Bothner
there that crashes in this case. There may be all kinds of buggy or obsolete readers. I would not worry about them, especially with something so hypothetical. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Directory names hard-coded in Texinfo Perl scripts

2021-12-16 Thread Per Bothner
a.jar ANYDIR/share/kawa/... Then if you execute ANYDIR/bin/kawa directly, or via a symlink, or if ANYDIR/bin (or a symlink) is on your PATH the script will set $kawadir to ANYDIR. Given that it can find ANYDIR/lib/kawa.jar, ANYDIR/share/kawa or other needed files. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: texi to epub

2021-12-16 Thread Per Bothner
TML 1.0 but not in 1.1). I think that it would make sens to always use tbody. Again, it's just a warning - but if it's easy to fix, we might as well. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: texi to epub

2021-12-15 Thread Per Bothner
a big step there. Emacs nxml mode should be sufficient to check well-formedness. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: texi to epub

2021-12-15 Thread Per Bothner
generating "polyglot" output (valid both as html and xml) as an option (and perhaps in the future the default) for --html. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: control over sectioning and splitting

2021-10-10 Thread Per Bothner
ing at a particular level on the hierarchy, but that is too inflexible: It makes for a non-optimal browsing expeience. -- --Per Bothner p...@bothner.com http://per.bothner.com/

control over sectioning and splitting

2021-10-09 Thread Per Bothner
ng I could do, but it doesn't help for traditional info and it doesn't solve the missing entries in the ToC. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: @tieaccent{..} does not display the tie accent in HTML

2021-09-01 Thread Per Bothner
both "xhtml" and "polyglot" modes we do: (1) Don't uses named entities except the builtin XML ones. (2) Close all tags. Where HTML prohibits separate closing tags, use the XML shorthand, e.g. . This works everywhere I've tried it. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: @tieaccent{..} does not display the tie accent in HTML

2021-08-31 Thread Per Bothner
On 8/30/21 3:44 PM, Gavin Smith wrote: On Mon, Aug 30, 2021 at 10:00:51AM -0700, Per Bothner wrote: What I'm looking for is: (1) Be able to post-process html output with xml tools, such as xslt. (2) Generate valid epub3 ebooks. These seem like valid goals so would be happy to see pa

Re: @tieaccent{..} does not display the tie accent in HTML

2021-08-30 Thread Per Bothner
at hex values are used almost universally for Unicode, and decimal values are rarely used. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: @tieaccent{..} does not display the tie accent in HTML

2021-08-27 Thread Per Bothner
decimal or hex numerical entities I think hex is preferable, as that is much more common for Unicode values. I.e. © rather than © for ©. -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: @tieaccent{..} does not display the tie accent in HTML

2021-08-27 Thread Per Bothner
the plain text accent markers. It works fine also on Google Chrome, and on Epiphany (based on the Safari/WebKit engine). Just generate 'oo͡o' and be done with it. (I would prefer using the hex value - one reason is it's easier to search for its meaning.) -- --Per B

scrolling js-info help page

2021-06-22 Thread Per Bothner
hrome and Firefox): 2021-06-22 Per Bothner * js/info.css: Styling tweaks for js-info to make help scrollable. diff --git a/js/info.css b/js/info.css index d8d20e1723..14537b67ad 100644 --- a/js/info.css +++ b/js/info.css @@ -166,13 +166,12 @@ table#keyboard-shortcuts th { dis

Fix js-info in iframe

2021-06-22 Thread Per Bothner
we're close to a release, but this seems fairly safe - plus it's in an "experimental" feature. Ok to check in? -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: texinfo-6.7.91 pretest

2021-06-19 Thread Per Bothner
Another thing worth mentioning in the "Full news" section: * texi2any - changes to HTML output - HTML is better structured and more modern, using elements for nested sections, and 'id' attributes for references -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: texinfo-6.7.91 pretest

2021-06-18 Thread Per Bothner
'description' is at least two bytes shorter (to make room for final newline plus final null) than strlen(entry) ? Probably, but there is no comment explaining why, and you'd have to look caefully to make sure there no case that could risk overflow. -- --Per Bothner p...@bot

Re: texinfo-6.7.91 pretest

2021-06-18 Thread Per Bothner
size_t length = strlen (ptr); - strncat (*description, ptr, length); - ptr += length; + strcat (*description, ptr); + ptr += strlen (ptr); } } /* Descriptions end in a new line. */ -- --Per Bothner p...@bothner.com http://per.bothner.com/

Re: Unadorned cross-references

2021-06-02 Thread Per Bothner
arser. The new JavaScript "html-info" reader handles both index search and full-text search (though that latter seems broken - haven't looked into it). You can see a sample in action here: https://per.bothner.com/tmp/Kawa-txjs/index.html If JavaScript can do, Emacs-Lisp can do

Re: Unadorned cross-references

2021-06-01 Thread Per Bothner
aults to creating a new eww buffer. We could call it "hinfo" mode, and describe it as "an experimental mode for browsing HTML documents (especially ones generated from texinfo) using info-style keybindings and behavior". We just need a volunteer ... -- --Per Bothne

Re: how to skip default css format lines in html output

2021-05-06 Thread Per Bothner
On 5/6/21 1:13 PM, Gavin Smith wrote: On 5/6/21 12:36 PM, Gavin Smith wrote: On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote: It seems wrong to include inline css in generated html files, especially when using the --ccs-ref or -C INFO_JS_DIR options. The documentation is

Re: how to skip default css format lines in html output

2021-05-06 Thread Per Bothner
On 5/6/21 12:36 PM, Gavin Smith wrote: On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote: It seems wrong to include inline css in generated html files, especially when using the --ccs-ref or -C INFO_JS_DIR options. The documentation is complicated. The advice to use !important to

  1   2   3   4   >