-
Notifications
You must be signed in to change notification settings - Fork 5
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
Speaker changes in dialogues #105
Comments
Turkish also uses this pattern. I believe from bookstore observation that many publishers use a thin space after it in their internal style guides while others fall victim to the same stretching problem you note here to rather unsightly effect. Do you have branch(es) with attempts to make this work on the SILE side? |
Interesting!
I don't know what I was thinking in those attempts, trying to do it in |
Interesting perhaps but not that surprising. Back about 100 years ago when Turkish orthography was being switched over from the (Arabic-like) RTL script to a Latin-derived script, it was a team a largely French linguists that were tasked with adapting the orthography and many (but not all) of the typography rules were invented by some folks with largely French training. That being said, there are probably more languages out there with French influence. |
Hence, issue rejected here:
|
In French (at least), it's common do have speaker changes in dialogues introduced by an em-dash:
— Lorem ipsum dolor sit amet, consectetur adipiscing elit, dit il.
— C’est sûr !
For comparison, English does not use such dashes normally.
“Lorem ipsum dolor sit amet, consectetur adipiscing elit,” he said.
“Sure!”
(English may used em-dashes, but at the end of a quote. Anyway, that's not the point).
The tricky thing here is that the following space ought to be fixed (= not stretched or shrinked by line justification) so that subsequent dialogue lines start identically.
Of course, I need to typeset such dialogues...
I was first tempted to do it in SILE itself (as we do for other fancy Unicode character and French punctuation, etc.) but it is not completely obvious to do there (I'm pulling my hair out trying, and I don't have much hair left, lol) and it requires awaiting a release...
It would be fairly obvious to do here, intercepting
—[ ]+
at the start of a paragraph (where the—
is native or derives from---
in Markdown or Djot, it ends up as — anyway in the SILE AST).The workaround is to manually enforce it, working in Djot only (attributes on anything, here a nbsp):
Cumbersome and annoying when copying/pasting text....
I dunno. Try harder to implement it in SILE for any input (incl. SIL), or push my already working attempt here?
The text was updated successfully, but these errors were encountered: