Git Product home page Git Product logo

Comments (6)

eroux avatar eroux commented on July 24, 2024

The best solution is to make annotation global (and not voice_info dependant), and use it. For nabc, there is also a annotation_nabc that will most certainly appear.

from gregorio.

rpspringuel avatar rpspringuel commented on July 24, 2024

I agree that the annotation fields should be fixed.

One thing that might make things easier is a rewrite of the setannotation interface that I've been thinking about. Right now there are two different annotation boxes, one for the first and one for the second, which are filled by separate commands. My idea was to create a single annotation box to which lines could be added by successive calls of the same function. In this fashion there's less to keep track of when writing information from the gabc into the gtex.

The idea came to me some months ago while working on texrenaming in gregoriotex.tex and I think I left myself some notes there in the form of a comment labeled TODO.

from gregorio.

eschwab avatar eschwab commented on July 24, 2024

First there should be an improved annotation setting macro in TeX. See this idea from @rpspringuel

Then however that works out, the gabc should be able to set the annotation with full formatting control i.e. annotation:\color{red}\emph{H}.\color{black}II;

from gregorio.

eroux avatar eroux commented on July 24, 2024

Apart from the fact that \color{red}H\color{black} is anti-pattern and should be replaced by {\color{red}H}, I admit I'm not particularly keen on having too much TeX in gabc... But I also admit it's just practical, and I don't think it would be reasonable (from a development resource point of view) to have some kind of markdown parsing in the gabc headers, so I don't disagree on this.

from gregorio.

jperon avatar jperon commented on July 24, 2024

Just a thought about that : to help one separate style and content, I think that approach should remain optional, and, if modelineone and modelinetwo are added, mode should remain (without any effect on the final output).

from gregorio.

rpspringuel avatar rpspringuel commented on July 24, 2024

The revamp to a single annotation function that I talked about is now in #476. This should make it much easier to implement this carry-over.

from gregorio.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.