9

I have a strange behavior with the microtype package (for some reason it won't break a word, but no warnings).

What can I do to post a MWE without personal informations? If I just replace the text with random Words, this obviously changes the layout and the behavior just disappears.

| |
  • Hmmm … Perhaps search for similar words, where you observe the same unwanted behaviour? Sort the letters of the personal information word by word alphabetical? – Speravir Dec 2 '13 at 4:40
  • blur it or overpaint it on MSpaint? – percusse Dec 2 '13 at 8:11
  • 3
    this doesn't address the mwe question, but is an approach to figuring out why a word isn't broken. you can use the command \showhyphens{thewordyouwantinformationabout} to find out how (la)tex thinks it can be broken. if the result doesn't show hyphenation points you can add them either with \hyphenation{this-is-how-to-break-it} entries in the preamble or with "discretionary hyphens" (\-) in appropriate places. if hyphenation points are shown, remember that a word that is already hyphenated can't automatically be hyphenated further, and some other tactic is needed. – barbara beeton Dec 2 '13 at 15:20
  • If the behavior is not reproducible, there's little people can do in order to help you. – egreg Dec 3 '13 at 8:53
10

Unless you discover a bug along the lines of: "when I put someonr in a section heading, the computer expolodes", it should always be possible to reproduce the bug.

If the problem is in TeX's word-breaking algorithm, then as long as the word to break is not strictly confidentail, you can replace everything else on the line by a properly sized \rule{10em}{1ex}. This puts a black box of width 10em (approx. 25 letters) into the text.

And I honestly can't think of a word in text that would be strictly confidential alone, and I would ever use it. However, if you have such a word that causes problems, then I don't think we can really help you.

| |
  • I just did this. Result is this question: tex.stackexchange.com/questions/148626/… – someonr Dec 6 '13 at 4:25
  • @someonr Well done and I certainly upvoted it! Even though it's unfortunate, old, and well-known bug, which is quite a pity :( – yo' Dec 6 '13 at 11:56
  • Not well known enough ;), I didn't find it while googling (but I also didn't expect a LuaLaTex Bug) – someonr Dec 6 '13 at 22:16

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .