Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implemented a toggle-able forced hyphen for empty initial syllables. #656

Closed
wants to merge 1 commit into from

Conversation

henryso
Copy link
Contributor

@henryso henryso commented Oct 23, 2015

Fixes #653.

Please review and merge if satisfactory.


### Empty first syllable hyphen

Prior to version 4.0, GregorioTeX would put a hyphen below an empty first syllable (which happens when the first syllable consists only of the initial). The spacing algorithm was improved in 4.0, but that eliminates the hyphen if there is not enough space between the note of the first syllable and the next syllable. The `\gresetemptyfirstsyllablehyphen` command controls this behavior. It defaults to `force`, which restores the pre-4.0 behavior, but may be changed to `auto` (i.e., `\gresetemptyfirstsyllablehyphen{auto}`) if you prefer the space-based behavior.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it would be best to document this for 4.0, as it it where the change happened? Thinking about that again, I'm wondering if it's a good idea not to do this hyphen thing for 4.0... what do you think (again)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little confused by your statement. Are you saying that we should do this change in 4.0 or leave it here in develop? If you think the scope of these changes is not "too much" for this late in the 4.0 cycle, then I can reopen the pull request against release-4.0.

My only concern with doing it this late in 4.0 is code quality. Of course, programmers never think they write buggy code, but experience often proves otherwise...

If this is not what you mean, can you clarify?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's what I mean indeed, I'm just concerned by this change in 4.0 that might not be easily spotted by users but would "damage" their scores...

@eroux
Copy link
Contributor

eroux commented Oct 23, 2015

Apart from the commentary, it looks good

@henryso
Copy link
Contributor Author

henryso commented Oct 24, 2015

I will re-open against release-4.0.

@henryso henryso closed this Oct 24, 2015
rpspringuel added a commit to rpspringuel/gregorio-test that referenced this pull request Dec 9, 2015
* develop:
  Addeds test and expectations for note-in-same-glyph episema height fix. Tests the fix for gregorio-project/gregorio#693.
  Updated expectations to match the fix for gregorio-project/gregorio#675.
  Added gabc-to-gabc tests and expectations.
  Added support for gabc-to-gabc tests.
  Updated expectations to match changes for gregorio-project/gregorio#670.
  Updated test for biginitial style deprecation. Corresponds with changes for gregorio-project/gregorio#632.
  Updated tests and expectations for initial-style deprecation. Corresponds with changes for gregorio-project/gregorio#632.
  Added support for per-gabc-output-test preamble files.
  Updated expectations to match changes for gregorio-project/gregorio#632.
  Added a test for the forced initial hyphen. Corresponds with gregorio-project/gregorio#656. Tests the fix for gregorio-project/gregorio#653.
  Added tests and expectations corresponding to gregorio-project/gregorio#636. This tests the implementation of gregorio-project/gregorio#631.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants