Re: guile-2.0 and debian

Hi, for now I looked only at a single problem, the meta-data. (Giving me a royal headache) 2016-11-19 16:05 GMT+01:00 Antonio Ospite : > The following change fixes the issue at hand: > > - > diff --git

Re: Add using Extract PDFmark for document building (issue 314130043 by truer...@gmail.com)

Thank you for your advice. https://codereview.appspot.com/314130043/diff/20001/configure.ac File configure.ac (right): https://codereview.appspot.com/314130043/diff/20001/configure.ac#newcode305 configure.ac:305: [" documentation and the final PDF files.)"]) On 2016/11/19 14:06:07, pkx166h

Re: guile-2.0 and debian

Hi, just to confirm my understanding about some previous items. On Thu, 17 Nov 2016 13:05:47 +0100 Antonio Ospite wrote: [...] > I compared the postscript output of the same lilypond git revision built > with both guile-1.8 (in a debian stable container) and guile-2.0, and by >

Re: guile-2.0 and debian

Antonio Ospite writes: > AFAICS in guile-2.0 the difference between characters and bytes is > taken very seriously. The problem is that lily/parser.yy and particularly lily/lexer.ll implement robust and fast recognition and interpretation of UTF-8. It transparently maps them to

Re: guile-2.0 and debian

2016-11-19 16:05 GMT+01:00 Antonio Ospite : > But I don't really know what I am talking about here... Speaking of it, the whole encoding-issue is not exactly my prefered topic ... > I still need to clean things up, and ask for advice for better fixes, > but I wanted to report

Re: guile-2.0 and debian

On Thu, 17 Nov 2016 22:24:27 +0100 David Kastrup wrote: > Antonio Ospite writes: > > > - > > (process:18706): Pango-WARNING **: Invalid UTF-8 string passed to > > pango_layout_set_text() > >

Re: guile-2.0 and debian

On Sat, 19 Nov 2016 16:05:22 +0100 Antonio Ospite wrote: [...] > - and than when scm_read() (lily/parse-scm.cc in ^ This is a "then". > internal_ly_parse_scm()) is called to parse the embedded scm, and > the latter is interpreted as Latin1 too. > --

Re: guile-2.0 and debian

On Fri, 18 Nov 2016 00:24:19 +0100 Thomas Morley wrote: [...] > Hi Antonio, > Hi, > as said, no time to dive in deeper, though here some observations (my > test-file attached.) > > - toplevel-markups with special characters working > - ly-identifier with special

Re: Add using Extract PDFmark for document building (issue 314130043 by truer...@gmail.com)

Domou Hosoda-Sama. https://codereview.appspot.com/314130043/diff/20001/configure.ac File configure.ac (right): https://codereview.appspot.com/314130043/diff/20001/configure.ac#newcode305 configure.ac:305: [" documentation and the final PDF files.)"]) All I would say is that "... and the final

Re: Add using Extract PDFmark for document building (issue 314130043 by truer...@gmail.com)

On 2016/11/19 06:11:09, lemzwerg wrote: Ah, bad wording, sorry. I don't care about the actual length of the message but the line length in the source code, so please just wrap the message to stay within 80 columns or so if possible. Here's another version of the message which you might

Re: meta-data with guile2

> Hi, > > this is a single problem from > http://lists.gnu.org/archive/html/lilypond-devel/2016-11/msg00090.html > about pdf-meta-data with guile2 > > In framework-ps.scm we have `metadata-encode' defined as part of > `handle-metadata' > There's the comment: > ;; First, call

Re: meta-data with guile2

On Sat, 19 Nov 2016 13:09:08 +0100 Thomas Morley wrote: > Hi, > > this is a single problem from > http://lists.gnu.org/archive/html/lilypond-devel/2016-11/msg00090.html > about pdf-meta-data with guile2 > > In framework-ps.scm we have `metadata-encode' defined as part

meta-data with guile2

Hi, this is a single problem from http://lists.gnu.org/archive/html/lilypond-devel/2016-11/msg00090.html about pdf-meta-data with guile2 In framework-ps.scm we have `metadata-encode' defined as part of `handle-metadata' There's the comment: ;; First, call ly:encode-string-for-pdf to encode