Skip to content

feature request: turn off EUOUAE on for grenextscore #1758

Open

Description

@MRoth1910
Image

In the screenshot you can see that I'm using a score where I have removed (or commented out, either way it's the same effect) the EUOUAE tags.

I would rather not clutter the directory. I have both bilingual sheets/booklets for a given Sunday or feast where I need the antiphon and a very much work-in-progress bilingual book that would involve page turns, and I've also copied the score from another directory that is Latin-only.

It'd be nicer to just search for one score file name without worrying about the appended no_euouae bit and then comment it out when the EUOUAE is not needed (for example, when there is no congregational chant at all or when the Magnificat is printed on the same page as its antiphon).

Something similar came up on the mailing list a long time ago and then I discovered a good use case for such a feature in building a booklet today.

Activity

  1. davidweichiang commented on May 21, 2026

    @davidweichiang
    Contributor

    Can you please clarify? For example, could you show what you would like the score/TeX to look like? Maybe \greseteuouae{keyword} where keyword is visible, invisible (takes up no space), or phantom (takes up space but does not print), as in #1683?

  2. MRoth1910 commented on May 22, 2026

    @MRoth1910
    Author

    Sure.

    Default should be visible.

    I think I would prefer invisible so the score prints at the last (::) and ignores everything after it; I don't personally see a use case for phantom since the will go to a new line if needed, which we probably don't want…

  3. fiat96 commented on Aug 7, 2026

    @fiat96

    I second this request, but I think a different approach might be more widely applicable.

    For instance, I experience the same inconvenience with the Euouae, but the intonation star (*) is also something that typically disappears the second time an antiphon is printed. So, like OP, I've been having to make two gabc files for each antiphon in a publication.

    My proposal - and I have no idea if this is viable - is to make a tag in the gabc that could be toggled in tex. For instance, if we used <x>, then

    (c4) PRo(f)té(fffd)ctor(ef) no(ghhg)ster(g.) <x>*</x>(,) 
    á(gjj)spi(h)ce,(g) De(h_f/h_g/hffef)us,(fe..)  (::) 
    Gló(hg)ri(gh)a(h) Pa(h)tri.(h) (::)
    <x><eu>E(h) u(h) o(gf) u(gh) a(g) e.</eu>(e.) (::)</x>
    

    could be invoked with something like \gresetfirstrepetitiontext{0} (I have no idea what to call it) to remove everything in the tags.

    This, used in combination with \gresetinitiallines and firstsyllableinitial would improve QOL significantly for projects with repeated antiphons by eliminating the need for two gabc files.

  4. MRoth1910 commented on Aug 8, 2026

    @MRoth1910
    Author

    I rarely print full antiphons twice in my own case, and I personally prefer doing something different than in real books (not using Ant. for an annotation, as I don't use a large initial for repeats). However, sometimes I do…and on those rare occasions I could be convinced to do something different if it meant only one file.

    Personally I usually use * directly: taking that into account as well as the Gregorio-provided formats would work well, although those don't go in tags, and there's no need for that, as this would cause a lot of issues for existing scores.

    I think the shorter the name with the fewer arguments the better: if that means multiple commands, so be it. Yes, one good thing about LaTeX is the number of arguments, but getting them right is such a pain…and David's proposal is short and clear.

  5. fiat96 commented on Aug 10, 2026

    @fiat96

    I concede these points, and on a second reading, David's solution would work just as well; I would just need to put the asterisk in euouae tags.

    That said, couldn't it be useful to have a second tag, so that the the visible / invisible / phantom functionality could be used independently of the <euouae> functionality?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions