title_body: Is it better to let a footnote link wrap to the next line or force it to remain with the last word block it references? I'm preping an Epub file and found an example on my reader where a footnote link rolled to the next line.  E.G., 
  
  This is some random text.[17]  After this is more.
  
  
  becomes in my reader...
  
  This is some random text.
  [17]  After this is more.
  
  
  I can add ...&lt;span style="white-space:nowrap;"&gt;text.[17]&lt;/span&gt;... (link tag removed for convenience) to force the issue, creating...
  
  This     is     some    random
  text.[17]  After this is more.
  
  
  All that extra white space is because I'm using full justification.  It looks better generally, but I might remove it due to problems with smaller screens.
  
  My question is which solution is preferable?  Should I force the footnote link to remain with its referent text or let the link roll to the next line with the possibility that it looks odd and may even lose context to the uninitiated (if there are uninitiated)?
upvoted_answer: I'm somewhat mystified that the reading system would put the footnote on the next line. Are you sure that in the HTML source  there is no random space (or extra character) between the last word of the sentence, the period, and the number reference in brackets?  One might expect these characters to run after another without spaces regardless of which line it appears on.  
  
  My preference would be not to hard code wrapping/justification defaults in the element (P? LI? etc)  and just let the reading system (and the reader) do it. Or maybe specify a default for body text? For one thing, this becomes less of an issue when displays are wider and reading systems become more powerful. You don't want your publisher css to depend on the user turning justification on or off.  If the user perceives that justification is impeding the ability to read the text, they can usually turn it off on settings. Handling of justification on reading systems will only improve over time. 
  
  I'd be curious what screen dimensions this issue is happening in. This is an anomaly that I personally am fine with mobile phone users experiencing if width is 600 or less.