Take the 2-minute tour ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

(Remark: Maybe this is a typically German problem, I'm not sure in which other languages that might be relevant)

Sometimes there are words which start with a hyphen, as they are connected with a word used before, e. g. Werkstoffforschung und -entwicklung is a shorter (and I think more elegant) way to say Werkstoffforschung und Werkstoffentwicklung.

However, if the second word, which starts with the hyphen, is at the beginning of a new line, it can happen that the hyphen stays in the previous line and the word itself is the first one in the next line.

Minimal example:

\documentclass[11pt]{scrreprt}
\usepackage[ngerman]{babel}  
\begin{document}
Das ist ein Mustertext, der dazu da ist, um diese aa Textsatzproblematik
    bzw. -schwierigkeit zu demonstrieren 
\end{document}

output

(I hope that the example "works" for you to demonstrate the problem, when I typeset it with pdflatex, the "-" is at the end of the first line and the "schwierigkeit" is in the second one which is not wanted.)

Is there a smart* way to avoid that problem?
* pdflatex shall handle this automatically and "know" that a hyphen at the beginning of a word always has to stay connected to the word and shall not be separated from it.

share|improve this question
    
You could probably use the same logic as in here. Also, I guess you could try wrapping the word in {}. –  morbusg Mar 13 '11 at 8:13
5  
This kind of usage is legal in English, too. It's just that we don't have enough long words to make it a problem. :-D –  Matthew Leingang Mar 13 '11 at 11:23
    
@Matthew: lucky you are. ;-) –  Martin Mar 13 '11 at 11:48
    
also remember to write bzw.\ for correct spacing. –  Ben Mar 13 '11 at 21:49
    
@Ben: No, usually not, in German the standard is \frenchspacing. –  Hendrik Vogt Mar 13 '11 at 22:03

4 Answers 4

up vote 27 down vote accepted

UPDATE: babel v3.9, released in March 2013, introduces a set of \babelhyphen macros -- see section 1.6 of the manual for details. In particular, \babelhyphen{nobreak} (the non-starred version) provides a non-breakable hyphen which allows hyphenation in the rest of the word -- for the present question, this may be used to define a new shorthand which removes the need to look up allowed breakpoints. (Note: Sometimes, the first allowed breakpoint will be located three or less characters after the non-breakable hyphen; if you consider such a breakpoint as inadequate, use my original answer.)

\documentclass[11pt]{scrreprt}
\usepackage[ngerman]{babel}  
% The following requires babel v3.9 (released March 2013)
\defineshorthand[ngerman]{"+}{\babelhyphen{nobreak}}
\begin{document}
Das ist ein Mustertext, der dazu da ist, um diese aa Textsatzproblematik
    bzw. "+schwierigkeit zu demonstrieren 
\end{document}

ORIGINAL ANSWER: Use babel's "~ shorthand to add an explicit hyphen with prohibited line break; supplement this by using the "- shorthand to specify the first allowed follow-up breakpoint. (You will have to look up those with \showhyphens{Schwierigkeit}. See pp. 5--7 of the documentation of the german package for details and other shorthands. (Note: the babel shorthands originate from the german package, which is considered obsolete nowadays.)

By the way, using "~ but not "- in your example would produce an overfull hbox.

\documentclass[11pt]{scrreprt}
\usepackage[ngerman]{babel}  
\begin{document}
Das ist ein Mustertext, der dazu da ist, um diese aa Textsatzproblematik
    bzw. "~schwie"-rigkeit zu demonstrieren 
\end{document}

enter image description here

share|improve this answer
    
@lockstep: thanks! I feared that something with ˚\mbox{} would be the recommended solution for that problem, but I dislike this kind of solutions very much as it makes the source text more difficult to read and it requires me thinking about such things. IMHO it is contrary to the philosophy of TeX (for my understanding to separate text editing and typesetting to avoid distractions) if I have to think all the time about how to trick LaTeX into doing it the correct way. :-( ... –  Martin Mar 12 '11 at 21:12
    
so isn't it possible (and wouldn't it make sense) to let LaTeX never separate a hyphen from the following characters or words if it follows a space (or in other words to never leave a lonely hyphen at the end of a line)? In what situation could it make sense what LaTeX does in this case? –  Martin Mar 12 '11 at 21:16
    
@Martin: I don't know if your suggested rule could be implemented. As for "making sense": I guess it made sense to the (English-speaking) developers of (La)TeX not to worry about words starting with a hyphen. –  lockstep Mar 12 '11 at 21:21
    
Another option would be to use the \discretionary primitive (perhaps that's what ngerman does internally?): Das ist ein Mustertext, der dazu da ist, um diese aa Textsatzproblematik bzw. \discretionary{-}{-}{-}schwie\-rigkeit zu demonstrieren –  Gonzalo Medina Mar 12 '11 at 21:45
1  
@Martin: Good question. The best would be to fix the internal hypenation algorithm of TeX, but that won't happen: It's a lot more important that TeX is stable, i.e., the output doesn't depend on whether you compile now or in 10 years. And the discussion here shows that it'll be hard to write a package that fixes the problem. –  Hendrik Vogt Mar 13 '11 at 14:28

(Edited answer; my initial idea of redefining \- was bad; thanks to lockstep for pointing that out and for suggesting \declare@shorthand.)

Based on Ulrike's solution I came up with a version that does not have the side effect of disabling hyphenation at the - in "Arbeiter-Unfallversicherung"; you also won't have to specify the first allowed follow-up breakpoint (cf. lockstep's answer). I can't tell if it has other side effects. The drawback is that you'll have to type "_ to get a hyphen that disallows a linebreak after it.

\documentclass[11pt]{scrreprt}
\usepackage[ngerman]{babel}
\makeatletter
\declare@shorthand{ngerman}{"_}{\hyphenchar\font=-1 -\hyphenchar\font=`\-}
\makeatother
\begin{document}
Das ist ein Mustertext, der dazu dient, diese unsch"one Textsatzproblematik
bzw. "_schwierigkeit zu demonstrieren.
Im n"achsten Satz gibt es einen Test f"ur die Arbeiter-Unfallversicherung.
\end{document}

Note that this solution does not depend on T1-encoding.

share|improve this answer
    
Well yes the solution doesn't depend on T1. But it doesn't depend on the number "127" either. Any number different to the position of the hyphen will work (including -1). –  Ulrike Fischer Mar 14 '11 at 13:20
    
@Ulrike: Thanks a lot for this comment. -1 looks indeed more natural in my solution; I've edited the answer accordingly. –  Hendrik Vogt Mar 14 '11 at 19:28
    
@Hendrik: I'm not sure if the original definition of \- is without use in German and therefore would plead for defining a new command, possibly in form of a new babel shorthand. –  lockstep Mar 14 '11 at 19:39
    
@lockstep: Why would you use \-? But if you have a better idea, please tell me - I've actually thought about it for a few minutes and then came up with \-. –  Hendrik Vogt Mar 14 '11 at 19:55
    
@Hendrik: Example of a new babel shorthand: \usepackage[ngerman]{babel} \makeatletter \declare@shorthand{ngerman}{"+}{\hyphenchar\font=-1 -\hyphenchar\font=`\-} \makeatother –  lockstep Mar 14 '11 at 19:56

You can use T1-encoding and set \hyphenchar to 127. But you must do it for all fonts, which in the end means that for you must correct the font definitions (here as an example the entries from T1cmr.fd:

\documentclass[11pt]{scrreprt}

\makeatletter
\providecommand{\EC@family}[5]{%
  \DeclareFontShape{#1}{#2}{#3}{#4}%
  {<5><6><7><8><9><10><10.95><12><14.4>%
   <17.28><20.74><24.88><29.86><35.83>genb*#5}{\hyphenchar\font=127}}
\DeclareFontFamily{T1}{cmr}{}
\EC@family{T1}{cmr}{m}{n}{ecrm}
\EC@family{T1}{cmr}{m}{sl}{ecsl}
\EC@family{T1}{cmr}{m}{it}{ecti}
\EC@family{T1}{cmr}{m}{sc}{eccc}
\EC@family{T1}{cmr}{bx}{n}{ecbx}
\EC@family{T1}{cmr}{b}{n}{ecrb}
\EC@family{T1}{cmr}{bx}{it}{ecbi}
\EC@family{T1}{cmr}{bx}{sl}{ecbl}
\EC@family{T1}{cmr}{bx}{sc}{ecxc}
\EC@family{T1}{cmr}{m}{ui}{ecui}
\makeatother
\usepackage[T1]{fontenc}
\usepackage[ngerman]{babel}
\begin{document}

Das ist ein Mustertext, der dazu da ist, um diese aa Textsatzproblematik bzw. -schwierigkeit zu demonstrieren

\end{document}
share|improve this answer
    
Could this possibly affect the output if one uses microtype and its protrusion feature? –  lockstep Mar 13 '11 at 17:37
    
@lockstep: No idea. I never use the \hyphenchar-trick myself. In the few case where I had to suppress a line break I used "~ or \mbox. –  Ulrike Fischer Mar 13 '11 at 17:56
    
thank you, in fact it works. Could there be any side-effects or unwanted "interactions" with other packages? –  Martin Mar 13 '11 at 19:19
1  
@Martin: I guess the side effect will be that you won't get hyphenation at the - in "Arbeiter-Unfallversicherung". –  Hendrik Vogt Mar 13 '11 at 22:08
    
@Hendrik: Good catch -- I did some quick tests, and this is indeed the case. –  lockstep Mar 13 '11 at 22:22

Perhaps it's useful to think about breaking the line at this explicit hyphen in terms of how TeX looks at the issue.

According to the TeXbook at the bottom of pg. 96, hyphenating words at their explicit hyphen implies in a penalty given by \exhyphenpenalty, whose default is 50 (at least in plain TeX).

So forbidding breaks at the explicit hyphen with \exhyphenpenalty=10000 in the preamble of your document seems to me like the least effort solution. I tested here and it works with your MWE.

share|improve this answer
2  
This would inhibit breaking also at legitimate hyphens. –  egreg Nov 26 '12 at 17:02
2  
This disables line breaks after all explicit hyphens, not only those at the start of a word. –  lockstep Nov 26 '12 at 17:02
    
@lockstep: Surely, but I'd say that breaking at explicit hyphens is not always wanted anyways (like in 2-D). Of course you can cook up examples like the Arbeiter-Unfallversicherung from Hendrik above, but TeX could find another paragraph break in that case. My solution avoids having to type extra stuff to circunvent the issue -- one can always type things inside mboxes to avoid hyphenation as a last resource. –  Mafra Nov 26 '12 at 17:31

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.