Thank you, Werner; I appreciate your openness to feedback here! Here is my suggestion for the v2.25 documentation at 36.9 Aligning objects (LilyPond Notation Reference) <https://lilypond.org/doc/v2.25/Documentation/notation/aligning-objects>.
First, a note: I think that “alignment point” (language that Carl S and I have been using in our recent emails) is conceptually different from “reference point.” Example: I recently wrote the following code — \tweak LyricText.parent-alignment-X #3.4 — which defines an AP (alignment point) associated with a note head. I *think* that that AP is not the same point as the RP (reference point) that is used to define the horizontal extent of the note. (If I have misunderstood things, please let me know.) Gabriel %%% BEGIN DRAFT LANGUAGE The self-alignment-interface defines objects’ alignment points. This interface applies to many graphical objects in LilyPond (see the list at self-alignment-interface <https://lilypond.org/doc/v2.25/Documentation/internals/self_002dalignment_002dinterface> ). An “alignment point” is a point associated with an object, along either the X axis or the Y axis, that LilyPond uses when aligning that object with other objects. “Self” alignment points are within the object itself. “Parent” alignment points are within the object’s parent. For example, LyricText.parent-alignment-X is the property of a lyric that specifies the alignment point along the X axis of that lyric’s parent, which is the note head linked to that lyric. %%% END DRAFT EXPLANATION ---------- Forwarded message --------- From: Werner LEMBERG Date: Sun, 25 Jan 2026 Subject: Re: IPA Transcriptions for Lyrics: Approaches Cc: <[email protected]> >> I think I'd explain the overrides a little differently. > > This language is very helpful, Carl. Your explanation is easier for > me to understand than what’s in the documentation > < https://lilypond.org/doc/v2.24/Documentation/internals/self_002dalignment_002dinterface > > or the wording in my earlier attempt. If there are suggestions to improve the documentation, please provide them! Many developers are not native English speakers, including me. Werner
