CCing Philipp Gesang, luaotfload developer
Dear Nikilaus,
> thanks much for Your immediate response and for posting issues in
> github. Of course, this is by no means an urgent issue, 3.0.3 is
> still working fine, but once I hit this strange error I thought it
> might help stabilize 4.0.0 (and/
> I thought it might help stabilize 4.0.0 (and/or also luatex with its
> frequent changes ?) in uptodate TeXLiVe environments if
> inconsistencies are communicated to development asap .
It does, thank you very much for that!
--
Elie
___
Gregorio-users
Am 17.12.2015 um 13:41 schrieb Élie Roux:
I don't have much time these days, I'm affraid I won't until beginning
of january but I've reported the issue here:
https://github.com/lualatex/luaotfload/issues/308
https://github.com/gregorio-project/gregorio/issues/717 It's been a
long time since I'
Dear Nikolaus,
> following your findings I tried to reverse what is mentioned in
> lines 112ff. of the 2.6 luaotfload-tool code:
>
>>> "\fileent{luatex-basics-gen.lua} calls functions from the
>>> \luafunction{texio.*} library; too much for our taste. We
>>> intercept them with dummies. "
>
> b
Am 16.12.2015 um 21:34 schrieb Henry So Jr.:
This is what I've found so far. 2.5 -> 2.6 was a pretty big change,
including a built-in custom (but switchable) version of the font loader.
I am curious as to whether switching the font loader to the reference
loader (or some other version) would mak
This is what I've found so far. 2.5 -> 2.6 was a pretty big change,
including a built-in custom (but switchable) version of the font loader.
I am curious as to whether switching the font loader to the reference
loader (or some other version) would make 2.6 work with gregorio. I
will have to get m
Am 16.12.2015 um 19:33 schrieb Henry So Jr.:
Thank you. I'll take a look and report what I find. By the way, those
are commit numbers? On which system?
Henry
Henry,
35328 and 39093 are TeXLive revision numbers. I'm not sure if just
luaotfload is the 'bad guy': couple days before I applied
tterspacing.
>
> Hope that helps...
> Fr Bernard
>
>
> - Original Message -
> From: "Henry So Jr."
> To: "Bernard Marsh"
> Cc: "Nikolaus Breuer" , gregorio-users@gna.org
> Sent: Wednesday, 16 December, 2015 4:38:00 PM
> Subject: R
...
Fr Bernard
- Original Message -
From: "Henry So Jr."
To: "Bernard Marsh"
Cc: "Nikolaus Breuer" , gregorio-users@gna.org
Sent: Wednesday, 16 December, 2015 4:38:00 PM
Subject: Re: [Gregorio-users] gregorio 4.0: trouble with latest tex/luatex
updates of
Breuer"
> To: gregorio-users@gna.org
> Sent: Tuesday, 15 December, 2015 5:35:55 PM
> Subject: [Gregorio-users] gregorio 4.0: trouble with latest tex/luatex
> updates of TeXLive 2015
>
> Dear gregorio-user-fellows,
>
> it seems gregorio (this time 4.0.0) can'
gre@font@music \GreCPPesOneNothing
l.33 }
%
Reverting to luaotfload 35328 gets rid of the error.
Bernard
- Original Message -
From: "Nikolaus Breuer"
To: gregorio-users@gna.org
Sent: Tuesday, 15 December, 2015 5:35:55 PM
Subject: [G
Dear gregorio-user-fellows,
it seems gregorio (this time 4.0.0) can't cope with latest TeXLive 2015
updates:
Before installing
[Sun Dec 13 15:40:04 2015] update: fbb (38195 -> 39071)
[Sun Dec 13 15:40:43 2015] update: fithesis (39009 -> 39079)
[Sun Dec 13 15:40:49 2015] update: gnuplottex (32
First, always reply to list.
On 2015-12-10 12:09 PM, Jan De Schryver wrote:
Dear Sir,
Since I did the upgrade, there is some fundamental changed in the
layout of the score, when I use the old template, after changing to
Gre.. instead setafter or before, there is something not clear for
fontsize
Yes, you can install the official release without uninstalling any of the betas
or release candidates. Version information is attached to the files so that
Windows can tell that you are upgrading an existing installation and will
overwrite the files as appropriate.
Br.
I have allready the beta version on Windows 10. Can I simply do the gregorio
4.0 setup above the beta version?
Greetings
Jan de Schryver
___
Gregorio-users mailing list
Gregorio-users@gna.org
https://mail.gna.org/listinfo/gregorio-users
On Fri, Oct 30, 2015 at 12:39:05AM -0400, Henry So Jr. wrote:
> > By the way, looking at gregall font, I see there are some unbalanced shapes
> > (for example, very thick neumes and thinner ones, or bigger shapes next to
> > smaller ones, see e.g. toG and toM, or clpp2 and clppt1). I think that it
On Thursday, 22 October 2015 at 09:19:04 am +0200, Abbazia Mater Ecclesiae
wrote:
> 2015-10-20 18:21 GMT+02:00 Jakub Jelinek :
>
> > On Tue, Oct 20, 2015 at 05:53:46PM +0200, Abbazia Mater Ecclesiae wrote:
> > > 2015-10-18 8:30 GMT+02:00 Abbazia Mater Ecclesiae <
> > > sangiulioinferme...@gmail.c
Dear Friends, no clues at all about this?
>
>
I'll remove all my nabc lines from my heading while I wait for something
new
Thanks,
Sr. Maria Ruth OSB
___
Gregorio-users mailing list
Gregorio-users@gna.org
https://mail.gna.org/listinfo/gregorio-users
On Tue, Oct 20, 2015 at 05:53:46PM +0200, Abbazia Mater Ecclesiae wrote:
> 2015-10-18 8:30 GMT+02:00 Abbazia Mater Ecclesiae <
> sangiulioinferme...@gmail.com>:
>
> > I only have TeXLive 2014, but it works for me fine.
> >> Attached is what I get. You haven't posted a corresponding main *.tex
> >
>
> I only have TeXLive 2014, but it works for me fine.
> Attached is what I get. You haven't posted a corresponding main *.tex
> file,
> so it is hard to find out what might be wrong.
>
Yes, I'll attach as soon as I can, but what could be the reason for this
strange output? The font is correctly
On Sat, Oct 17, 2015 at 06:55:54PM +0200, Abbazia Mater Ecclesiae wrote:
> Dear All,
>
> this is what happens with new upgrading... I installed TeXLive 2015 also, I
> hope this is not the cause...
>
> What can I do to get correct nabc neumes?
I only have TeXLive 2014, but it works for me fine.
A
Dear All,
this is what happens with new upgrading... I installed TeXLive 2015 also, I
hope this is not the cause...
What can I do to get correct nabc neumes?
Thanks!
Sr. Maria Ruth
a--ecce-rex-veniet.gabc
Description: Binary data
ant.ecce.pdf
Description: Adobe PDF document
On Friday, 09 October 2015 at 07:41:15 pm +0200, Abbazia Mater Ecclesiae wrote:
> 2015-10-09 15:52 GMT+02:00 Henry So Jr. :
>
> > The space (//) after the forced custos (e+) is causing TeX to break the
> > line at that point. Because of how line endings work in Gregorio, this
> > is causing the d
2015-10-09 15:52 GMT+02:00 Henry So Jr. :
> The space (//) after the forced custos (e+) is causing TeX to break the
> line at that point. Because of how line endings work in Gregorio, this
> is causing the double-clef on the following line.
I have to add the (//) to avoid the custos collapsing
The space (//) after the forced custos (e+) is causing TeX to break the
line at that point. Because of how line endings work in Gregorio, this
is causing the double-clef on the following line. This is probably a
bug, so I entered it into the issue tracker at
https://github.com/gregorio-proje
Dear friends,
it happens that an old bug, the double-clef at the beginning of lines,
comes back again!
That's really strange, but... see the attached.
I'm really sorry to stress you so often... God bless your patience! :)
Thank you all,
Sr. Maria Ruth OSB
doubleclef.rar
Description: applicatio
On Saturday, 12 September 2015 at 11:34:33 am -0400, Henry So Jr. wrote:
> On Saturday, 12 September 2015 at 04:34:37 pm +0200, Abbazia Mater Ecclesiae
> wrote:
> >
> > Another question: see the pdf attached. I have the output you see in the
> > pdf in that point ONLY at the second compilation pa
On Saturday, 12 September 2015 at 04:34:37 pm +0200, Abbazia Mater Ecclesiae
wrote:
> >
> > Would you mind sending the source files for this second issue? It smells
> > like a bug, but it could be a number of things.
> >
>
> I discovered by chance that the problem was that I have to leave a blan
>
> Would you mind sending the source files for this second issue? It smells
> like a bug, but it could be a number of things.
>
I discovered by chance that the problem was that I have to leave a blank
line before the \includescore (\gregorioscore) command... If I do this,
that strange space disa
On September 12, 2015 5:15:01 AM Abbazia Mater Ecclesiae
wrote:
Dear All,
when I try to include the attached gabc file in my main.tex I get the
following error:
(./a--quaerite-dominum-4_0_0-beta2.gtex
! Argument of \GreSyllable has an extra }.
\par
l.18 \GreSyllable
{r}{i}{}{0}{
Dear All,
when I try to include the attached gabc file in my main.tex I get the
following error:
(./a--quaerite-dominum-4_0_0-beta2.gtex
! Argument of \GreSyllable has an extra }.
\par
l.18 \GreSyllable
{r}{i}{}{0}{\GreSetNextSyllable{t}{e}{}}{}{0}{}{%
?
This happens when the initial
2015-09-03 15:29 GMT+02:00 Henry So Jr. :
> I'm still trying to figure out why you're getting the extra } problem.
> If it's some weird version mismatch, then that might explain why these
> other things are not working for you.
>
Henry, with your advices everything works fine, and thanks to you I
2015-09-04 3:08 GMT+02:00 Br. Samuel Springuel :
> Okay, the problem here is that you can't put the custos blocking command
> in the lyrics, it has to be in the notes. This means that you have to use
> macros, not the `` tags.
>
> Add the following to your gabc file header:
>
> def-m1:\greseteolc
On 2015-09-03 12:55 PM, Abbazia Mater Ecclesiae wrote:
2. The command \greseteolcustos{manual} doesn’t work if it’s set in the
middle of a score, it just works at the beginning of a score inclusion
(in my documents, at least…). But what if a line break occurs just
before the /divisio finalis/ tha
On 2015-09-03 12:55 PM, Abbazia Mater Ecclesiae wrote:
2. The command \greseteolcustos{manual} doesn’t work if it’s set in the
middle of a score, it just works at the beginning of a score inclusion
(in my documents, at least…). But what if a line break occurs just
before the /divisio finalis/ tha
On Thursday, 03 September 2015 at 06:55:53 pm +0200, Abbazia Mater Ecclesiae
wrote:
> Something else I found in the meanwhile:
>
> 1. If a .gabc file with initial-style:0; has the “mode” field filled with
> something, and this file is included without commenting the "mode" field,
> that string ap
2015-09-03 15:29 GMT+02:00 Henry So Jr. :
> On Thursday, 03 September 2015 at 01:40:24 pm +0200, Abbazia Mater
> Ecclesiae wrote:
> Would you mind sending the generated .gtex file?
Yes, I'll do as soon as I can.
> Something doesn't make
> sense because the files you are sending work fine on my
On Thursday, 03 September 2015 at 01:40:24 pm +0200, Abbazia Mater Ecclesiae
wrote:
> Here's another file that gives me the same error (long episema on “est”):
>
> Module gregoriotex info: compiling the score a--non-auferetur.gabc...
Would you mind sending the generated .gtex file? Something do
Here's another file that gives me the same error (long episema on “est”):
Module gregoriotex info: compiling the score a--non-auferetur.gabc...
(./a--non-auferetur-4_0_0-beta2.gtex(load luc:
C:/texlive/2014/texmf-var/luatex-
cache/generic/fonts/otf/arnopro-display.luc)
! Argument of \GreHEpisem
>
> I don't get an error with the attached gabc file. Are you sure this is
> the one that fails?
>
Yes, I am.
Anyway, I'll try again.
I have problems with other bridged episemi (I'll send images), but I never
thought about the possibility to write them separately, as you suggest
below:
> > What
On Wednesday, 02 September 2015 at 02:43:07 pm +0200, Abbazia Mater Ecclesiae
wrote:
> Now, a question: while compiling the attached .gabc file, I’m not able to
> obtain the long episema on *Domini.* The following error occurs when I try
> to put a bridged episema on the puncta inclinata or somewh
Dear Gregorio Team,
and Brother Samuel particularly, thank you so much for this last release,
since the \greillumination feature was something lying in my desires but I
never dared to express! So thank you very very much!
Now, a question: while compiling the attached .gabc file, I’m not able to
Since this is getting into the nitty-gritty of the code, I've opened an
issue to continue the discussion:
https://github.com/gregorio-project/gregorio/issues/584
✝
Br. Samuel, OSB
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
___
Greg
> I don't know. I didn't make any changes to the fact that it was
> commented out. I just renamed the function contained on that line.
> Browsing through the history it looks like you commented it out back in
> 2010 when end of line shifts were first introduced (commit
> 049b0ac806a67b967d9ae5d66
On 2015-08-25 1:18 PM, Élie Roux wrote:
Br. Samuel: there's quite a confusion in the code between eolshifts and
bolshifts. These are two different things: eolshift is always active,
while bolshift can be enabled or disabled, but it should be by
\gresetbolshifts instead of \greeteolshifts, I think
>
> BTW, don't you like this feature?
Oh no, I like it very much, but since I have to test the new version to
find bugs... :)
> The current way of inputting is not optimal indeed, but it has its
> own logic to get used to...
>
It's just a matter of finding it, no problem!
Thank you,
Sr. M.
Dear all,
> I noticed that if I disable the default option \greseteolshifts, the
> correct initial syllable alignment is disabled too… Does this happen
> with a logic connection between the two options or not?
Indeed. But it shouldn't.
Br. Samuel: there's quite a confusion in the code between
Dear All,
I noticed that if I disable the default option \greseteolshifts, the
correct initial syllable alignment is disabled too… Does this happen with a
logic connection between the two options or not?
Moreover, it could be useful having in the Ref doc some examples of the
tag at work, since
I don't have the fonts you're using, so I can't actually typeset your
document to see the warnings you're getting. If the fonts are free, can
you indicate where to get them? If they aren't, can you attach the log
file generated when you typeset the document so that I can at least see
what Lua
Dear Friends,
thanks again for the huge work done on Gregorio 4.0. I’m testing it and,
since now, I found everything right.
I need an help in managing initials: I’m trying to obtain a very huge
initial for the first pace of a booklet which is reproducing the first page
of a manuscript. There, t
The Dominican chant fonts replace the augmented liquescent glyphs with
"tail" stems rather than Solesmes-like "drips". This includes the virga
glyphs, which you mention and the final note in longer liquescent forms.
The other glyph replaced is the epiphonus (with a longer "tail").
Other than the
What version of OS X are you using?
—OS X 10.10.4
What version of TeXLive are you using? Were any previous versions of
TeXLive installed on the machine?
Did you use the MacTeX installer or the TeXLive install script? MacTex
Installer
What version of MacPorts are you using? 2.3.3. [I think]
Wha
I'm glad you got it working, but I'd like to debug the installation
instructions if you're willing to help. Can you answer the following
questions so that I can try to replicate the problem you had? (Note,
some may be repetitive of information you've already provided or of
what's on the websi
Dear Br Samuel,
Thanks for your message. One specifically Dominican upgrade question (which
is not mentioned in the UPGRADE.md file): if I have the Dominican chant
font selected, is the only GABC change I need to make adding a V before >
or < ? Or are there any other significant changes in the fon
Dear Br Samuel,
Thanks for your message. I did the Git installation method described on the
installation page.
I tried the Mac installer, and now it is working fine. Thanks!
fr Innocent
On Mon, Aug 17, 2015 at 5:00 PM, Br. Samuel Springuel wrote:
> Which source file did you download? The fil
This is what the UPGRADE.md file is for (it's plain text, despite the
unusual extension, and should open in any text editor). If, after
following the instructions there, you have a project which still doesn't
work under the new regime, please post something more specific to the
problem you're
Which source file did you download? The files labeled "Source code" are
a picture of the repository at the time of the release created
automatically by GitHub. Building from them requires all the same tools
as building from a clone of the repository (including the tools
necessary to build the
Hello,
I just sent another email regarding a font problem I'm having with Gregorio
4.0. I thought that I should use a different thread for this question.
I appreciate the change log that Br Samuel provided here (
https://www.mail-archive.com/gregorio-users@gna.org/msg02800.html).
Is it possible
Hello,
I'm trying to use the Gregorio 4.0 beta. I'm using TeXLive 2015 and
installed the beta from source (as described here:
http://gregorio-project.github.io/installation-mac.html). I'm doing this on
a new computer that I haven't used for Gregorio or LaTeX before. It is
running Mac OS X 10.10.4.
On Thursday, 25 June 2015 at 06:55:07 pm +0200, Abbazia Mater Ecclesiae wrote:
> >
> > The "Unreleased" section of the change log at
> > https://github.com/gregorio-project/gregorio/blob/develop/CHANGELOG.md
> > lists all the changes already implemented for the next release.
> >
>
> Thank you all!
>
> The "Unreleased" section of the change log at
> https://github.com/gregorio-project/gregorio/blob/develop/CHANGELOG.md
> lists all the changes already implemented for the next release.
>
Thank you all!
When do you think Gregorio 4.0 could be released?
Sr. M. Ruth
_
On Thursday, 25 June 2015 at 04:02:30 pm +0200, Abbazia Mater Ecclesiae wrote:
> Dear Gregorio Project Team,
> can someone tell me precisely (if it's possibile) which features and new
> behaviors will be found in Gregorio 4.0? I have to do a big work on spacing
> algorithm and I'd like not to have
Le 25/06/2015 16:02, Abbazia Mater Ecclesiae a écrit :
> can someone tell me precisely (if it's possibile) which features and new
> behaviors will be found in Gregorio 4.0?
You can find it here:
https://github.com/gregorio-project/gregorio/blob/develop/CHANGELOG.md
> I have to do a big work on
>
Dear Gregorio Project Team,
can someone tell me precisely (if it's possibile) which features and new
behaviors will be found in Gregorio 4.0? I have to do a big work on spacing
algorithm and I'd like not to have to do everything from the beginning
after Gregorio 4.0 release, since I'll surely need
64 matches
Mail list logo
