- **labels**:  --> Fixed_2_19_55
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

Pushed to staging as
commit df854ae456ad2e57139ddcb345760b4c321e1cbb
Author: David Kastrup <[email protected]>
Date:   Sat Jan 28 01:16:54 2017 +0100

    Issue 1375/3: Register scheme engravers
    
    This registers Measure_counter_engraver and Span_stem_engraver
    to make them documented and callable like C++ engravers.

commit 6887546c5caf87cdc94252c020f39b43a57bf057
Author: David Kastrup <[email protected]>
Date:   Tue Jun 16 14:14:27 2015 +0200

    Issue 1375/2: Create Translator_creator class
    
    Previously, translators were created by copying from a context-less
    instantiation of the translator containing its documentation.  This had
    several unpleasant consequences, the most problematic likely being the
    inability to register Scheme engravers because their documentation would
    be identical to all other Scheme engravers.
    
    A new Translator_creator class takes over the task of creating
    Translator instances when called with a context argument.
    
    As a result of joining the mechanisms for Scheme engravers and C++
    engravers, ly:translator-name and ly:translator-description are
    reimplemented in a manner resembling object properties.

commit 6d1c5d25389afa6dbbfb4722df3732e764cbbf2e
Author: David Kastrup <[email protected]>
Date:   Fri Jan 27 13:27:03 2017 +0100

    Issue 1375/1: Let Translator constructor take a Context argument
    
    This is the first step towards constructing rather than cloning translators
    when creating contexts.  On its own, it does not make sense, but the change
    is large and mostly mechanical, so keeping it separate from the actually
    difficult parts makes sense.




---

** [issues:#1375] Enhancement: Scheme engravers support in engraver-init.ly and 
documentation**

**Status:** Fixed
**Labels:** Fixed_2_19_55 
**Created:** Sun Oct 31, 2010 03:34 AM UTC by Anonymous
**Last Updated:** Thu Feb 02, 2017 10:37 AM UTC
**Owner:** David Kastrup


*Originally created by:* *anonymous

*Originally created by:* [v.villenave](http://code.google.com/u/v.villenave/)
*Originally owned by:* [[email protected]](http://code.google.com/u/[email protected]/)

Since the 2.13.11, we've had the ability of implementing engravers using Scheme 
only.  However, this currently has two limitations: such engravers may not be 
directly \consisted in engraver-init.ly, and no proper documentation support 
has been implemented.

Read for example the following discussion, where an engraver had to be 
rewritten in C++ just because of these limitations:
[http://lists.gnu.org/archive/html/lilypond-devel/2010-10/msg00541.html](http://lists.gnu.org/archive/html/lilypond-devel/2010-10/msg00541.html)


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto

Reply via email to