On Sun, Nov 13, 2022 at 07:45:44PM +, Gavin Smith wrote:
> When I run "make distcheck", there are two test failures:
I think that I just fixed that, by chance while looking at something
else, the issue is that the tested init files were not in DIST.
https://git.savannah.gnu.org/cgit/texinfo.gi
On 11/13/22 11:54, Gavin Smith wrote:
There are three files that may be removed: package.json, tsconfig.json
and yarn.lock.
I'm pretty sure we can also remove server.js.
I believe these are all related to the npm package manager.
npm was originally used when this code was being developed.
On Sun, Nov 13, 2022 at 05:46:08AM -0800, Per Bothner wrote:
>
>
> On 11/13/22 01:22, Hilmar Preuße wrote:
> > hopefully this is not a FAQ, but I found nothing in the archive.
> >
> > What is the status of the code sitting in subdir "js"? To me this code
> > looks quite unmaintained.
>
> It is
When I run "make distcheck", there are two test failures:
FAIL: t/init_files_tests.t 44 - customize_translations converted file_html
FAIL: t/init_files_tests.t 66 - customize_special_element converted file_html
These tests pass usually when I just run "make check".
I found that the files were no
On Sun, Nov 13, 2022 at 11:53:54AM +, Gavin Smith wrote:
> On Sun, Nov 13, 2022 at 12:26:33PM +0100, Patrice Dumas wrote:
> > On Sun, Nov 13, 2022 at 11:12:17AM +, Gavin Smith wrote:
> > > I've done it myself. I didn't change the makeinfo invocation. I don't
> > > like the "-c TEXINFO_OUT
Hello,
For LaTeX output, it seems important to allow to customize the
beginning of the preamble, with the documentclass and usepackage.
The remaining of the generated preamble can probably be undone/modified
by LaTeX code in a @latex block appearing in the preamble, before any
formatted content, t
On 11/13/22 01:22, Hilmar Preuße wrote:
hopefully this is not a FAQ, but I found nothing in the archive.
What is the status of the code sitting in subdir "js"? To me this code
looks quite unmaintained.
It is definitely maintained. It hasn't seen much development recently
(it works pretty we
On Sun, Nov 13, 2022 at 12:26:33PM +0100, Patrice Dumas wrote:
> On Sun, Nov 13, 2022 at 11:12:17AM +, Gavin Smith wrote:
> > I've done it myself. I didn't change the makeinfo invocation. I don't
> > like the "-c TEXINFO_OUTPUT_FORMAT=plaintexinfo" option much but it is
> > not a big deal if
On Sun, Nov 13, 2022 at 11:12:17AM +, Gavin Smith wrote:
> I've done it myself. I didn't change the makeinfo invocation. I don't
> like the "-c TEXINFO_OUTPUT_FORMAT=plaintexinfo" option much but it is
> not a big deal if you would rather use it. (My feeling is that
> "plaintexinfo" is not v
On Sat, Nov 12, 2022 at 12:47:21PM +, Gavin Smith wrote:
> On Wed, Aug 24, 2022 at 08:36:50PM +0200, Patrice Dumas wrote:
> > > My preference would be to leave the code as it is now, as it looks fairly
> > > complicated and it is one more thing to break when the code gets a
> > > wider audience
>> Interesting. Using either evince 41.3 or okular 21.12.3 on my
>> GNU/Linux box, copy and paste works correctly.
>>
>> What PDF viewer is problematic for you?
>
> evince 3.36.10.
OK, thanks.
>> This is a nice idea, since PDF version 1.5 is the standard format
>> of pdftex nowadays. I thin
On Sun, Nov 13, 2022 at 06:59:32AM +, Werner LEMBERG wrote:
> Interesting. Using either evince 41.3 or okular 21.12.3 on my
> GNU/Linux box, copy and paste works correctly.
>
> What PDF viewer is problematic for you?
evince 3.36.10.
>
> > I did investigate if something could be done inside
On Sun, Nov 13, 2022 at 10:22:23AM +0100, Hilmar Preuße wrote:
> Hi,
>
> hopefully this is not a FAQ, but I found nothing in the archive.
>
> What is the status of the code sitting in subdir "js"? To me this code
> looks quite unmaintained. I'm just asking, b/c the dependabot [1]
> reports a lot
Hi,
hopefully this is not a FAQ, but I found nothing in the archive.
What is the status of the code sitting in subdir "js"? To me this code
looks quite unmaintained. I'm just asking, b/c the dependabot [1]
reports a lot of vulnerabilities in js/yarn.lock. I'm aware that the are
mostly sitting in
>> Since you have a real use case here, and the case of someone trying
>> to use a degree sign without the EC font is only hypothetical, I
>> have instated your proposed definition for \textdegree.
>
> Thanks.
For consistency I think you should apply the following.
Werner
15 matches
Mail list logo