GSoC 2020 update, June 19

Hi all! Here with another weekly update. This week, I corresponded with Daniel Spreadbury on the W3C Music Notation Community Group public email list and Behdad Esfahbod on the HarfBuzz mailing list, and received some clarifications on how to continue. It looks like we won't need to add OpenType s

Re: Parsing JSON in C++

Hi, in C++ I worked with property_trees from BOOST (under the BOOST license): https://www.boost.org/doc/libs/1_73_0/doc/html/property_tree.html Cheers, Joram

Re: Parsing JSON in C++

guile-json is not a GNU project, but it is hosted on Savannah. It has a release in May 2020, and is licensed by GPL3.0. This sounds very compatible, but I don't know that it's the best. Carl On 6/19/20, 5:30 PM, "lilypond-devel on behalf of Owen Lamb" wrote: Hi all, I need to be able to

Parsing JSON in C++

Hi all, I need to be able to expose the contents of a SMuFL font's JSON metadata file to LilyPond. From what I can tell, LilyPond currently doesn't have any sort of JSON-parsing library in its dependencies, either in Scheme or in C++. An internet search revealed that there are... a *lot* of option

Re: releasing 2.21.2

Am Donnerstag, den 11.06.2020, 16:12 +0200 schrieb Jonas Hahnfeld: > Hi all, > > with an initial CG update for GitLab committed, I'd like to propose > that we have our next unstable release 2.21.2 to get the documentation > available online. > > Due to the problems we had in the past, I decided t

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Freitag, den 19.06.2020, 16:31 +0200 schrieb Han-Wen Nienhuys: > Thanks; yours is much nicer. > > Meanwhile, mine is failing for unknown reasons. > > How does this thing work? > > make doc > => > # Making input/regression/out-www/collated-files.pdf < texi > TEX=/home/hanwen/vc/lilypond/script

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Thanks; yours is much nicer. Meanwhile, mine is failing for unknown reasons. How does this thing work? make doc => # Making input/regression/out-www/collated-files.pdf < texi TEX=/home/hanwen/vc/lilypond/scripts/build/xetex-with-options.sh PDFTEX=/home/hanwen/vc/lilypond/scripts/build/xetex-with

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Freitag, den 19.06.2020, 15:36 +0200 schrieb Jonas Hahnfeld: > Am Freitag, den 19.06.2020, 15:11 +0200 schrieb Jonas Hahnfeld: > > Am Freitag, den 19.06.2020, 14:49 +0200 schrieb Han-Wen Nienhuys: > > > [hanwen@t460-wlan lilypond]$ qpdf --qdf --object-streams=disable > > > broken2.pdf /dev/stdou

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Han-Wen Nienhuys writes: > On Fri, Jun 19, 2020 at 3:13 PM David Kastrup wrote: >> >> Han-Wen Nienhuys writes: >> >> > On Fri, Jun 19, 2020 at 12:50 PM Jonas Hahnfeld wrote: >> >> No changes for me. Please also keep in mind that the same command >> >> string works via the API interpreter. It c

Re: xdvipdfmx fails with some regtests (“Invalid object”)

On Fri, Jun 19, 2020 at 3:13 PM David Kastrup wrote: > > Han-Wen Nienhuys writes: > > > On Fri, Jun 19, 2020 at 12:50 PM Jonas Hahnfeld wrote: > >> No changes for me. Please also keep in mind that the same command > >> string works via the API interpreter. It could be that this is related > >> t

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Freitag, den 19.06.2020, 15:11 +0200 schrieb Jonas Hahnfeld: > Am Freitag, den 19.06.2020, 14:49 +0200 schrieb Han-Wen Nienhuys: > > On Fri, Jun 19, 2020 at 12:50 PM Jonas Hahnfeld wrote: > > > No changes for me. Please also keep in mind that the same command > > > string works via the API inte

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Han-Wen Nienhuys writes: > On Fri, Jun 19, 2020 at 12:50 PM Jonas Hahnfeld wrote: >> No changes for me. Please also keep in mind that the same command >> string works via the API interpreter. It could be that this is related >> to processing other files before the "empty" one... >> I'll try to w

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Freitag, den 19.06.2020, 14:49 +0200 schrieb Han-Wen Nienhuys: > On Fri, Jun 19, 2020 at 12:50 PM Jonas Hahnfeld wrote: > > No changes for me. Please also keep in mind that the same command > > string works via the API interpreter. It could be that this is related > > to processing other files

Re: xdvipdfmx fails with some regtests (“Invalid object”)

On Fri, Jun 19, 2020 at 2:49 PM Han-Wen Nienhuys wrote: > This does present a quandary, because we'd either have to find > configuration that causes the problem to go away, or we have to modify > the string we're executing if we're not using the API. > > But the latter undoes the benefit of unifyi

Re: xdvipdfmx fails with some regtests (“Invalid object”)

On Fri, Jun 19, 2020 at 12:50 PM Jonas Hahnfeld wrote: > No changes for me. Please also keep in mind that the same command > string works via the API interpreter. It could be that this is related > to processing other files before the "empty" one... > I'll try to write a small wrapper around the A

Re: xdvipdfmx fails with some regtests (“Invalid object”)

On Fri, Jun 19, 2020 at 1:01 PM Han-Wen Nienhuys wrote: > > It looks like this was discussed here: > > https://github.com/CTeX-org/forum/issues/29 > > (it's in Chinese, but google translate does a good job on the text.) > > According to the report, it's a bug in xdvipdfmx, and the blank pdf > file

Re: xdvipdfmx fails with some regtests (“Invalid object”)

On Fri, Jun 19, 2020 at 12:50 PM Jonas Hahnfeld wrote: > > Am Freitag, den 19.06.2020, 12:18 +0200 schrieb Han-Wen Nienhuys: > > On Fri, Jun 19, 2020 at 12:11 PM David Kastrup wrote: > > > Jonas Hahnfeld via Discussions on LilyPond development > > > writes: > > > > > > > Am Freitag, den 19.06.20

Re: xdvipdfmx fails with some regtests (“Invalid object”)

It looks like this was discussed here: https://github.com/CTeX-org/forum/issues/29 (it's in Chinese, but google translate does a good job on the text.) According to the report, it's a bug in xdvipdfmx, and the blank pdf file is within spec. I looked at epdf.c, but there was no change in the las

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Freitag, den 19.06.2020, 12:18 +0200 schrieb Han-Wen Nienhuys: > On Fri, Jun 19, 2020 at 12:11 PM David Kastrup wrote: > > Jonas Hahnfeld via Discussions on LilyPond development > > writes: > > > > > Am Freitag, den 19.06.2020, 11:47 +0200 schrieb Han-Wen Nienhuys: > > > > On Thu, Jun 18, 202

Re: xdvipdfmx fails with some regtests (“Invalid object”)

On Fri, Jun 19, 2020 at 12:11 PM David Kastrup wrote: > > Jonas Hahnfeld via Discussions on LilyPond development > writes: > > > Am Freitag, den 19.06.2020, 11:47 +0200 schrieb Han-Wen Nienhuys: > >> On Thu, Jun 18, 2020 at 7:45 PM Jonas Hahnfeld wrote: > >> > Am Donnerstag, den 18.06.2020, 11:2

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Jonas Hahnfeld via Discussions on LilyPond development writes: > Am Freitag, den 19.06.2020, 11:47 +0200 schrieb Han-Wen Nienhuys: >> On Thu, Jun 18, 2020 at 7:45 PM Jonas Hahnfeld wrote: >> > Am Donnerstag, den 18.06.2020, 11:21 -0600 schrieb Carl Sorensen: >> > > is it the difference between a

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Freitag, den 19.06.2020, 11:47 +0200 schrieb Han-Wen Nienhuys: > On Thu, Jun 18, 2020 at 7:45 PM Jonas Hahnfeld wrote: > > Am Donnerstag, den 18.06.2020, 11:21 -0600 schrieb Carl Sorensen: > > > is it the difference between an output .ps file and an output .eps file? > > > > No, broken.ps file

Re: xdvipdfmx fails with some regtests (“Invalid object”)

On Thu, Jun 18, 2020 at 7:45 PM Jonas Hahnfeld wrote: > > Am Donnerstag, den 18.06.2020, 11:21 -0600 schrieb Carl Sorensen: > > On Thu, Jun 18, 2020 at 11:04 AM Jonas Hahnfeld via Discussions on > > LilyPond development wrote: > > > Am Donnerstag, den 18.06.2020, 00:23 +0200 schrieb Valentin Vill

Re: Texinfo - manual line breaks in URLs?

> The patch did not solve the problem. OK. It was a shot into the dark. > A glance into the texi2dvi code showed that rather this tool causes > the problem. See > http://git.savannah.gnu.org/cgit/texinfo.git/diff/util/texi2dvi?id=2405caa6c7ab01d99af56aa056b1e77485ba Thanks for investigat

Re: Texinfo - manual line breaks in URLs?

Am 18.06.2020 um 22:36 schrieb Michael Käppler: Am 18.06.2020 um 18:57 schrieb Werner LEMBERG: What seems most likely to me is that the indices are generated correctly, but texi2pdf refuses to generate the sorted versions. If I call texi2pdf --debug I do not see any invocations of 'texindex'.