Tags:
create new tag
view all tags
How about a shortcut for & ? I find it so useful I have defined strings of 1 to 10 of them:
  • Non-breaking spaces
    • Set s10 = %s9%  
      • .
      • . (See, I had to resort to indents to make a vertical ". . .").
      • .
    • Set s1 =  
If there were a 1 character shortcut for  , it could be used anywhere, not just the beginning of a line. Some examples:
  • After periods & colons if you are a typewriter refugee that thinks there should be 2 spacesbetween sentences.
  • Around the '*', '_', & '=' shortcuts when kerning is needed.
    • this might be more cleanly handled by using CSS to increase the right and left padding to the strong, em and code elements (then the user doesn't need to do anything at all).
  • In tables, if you think the verticals crowd the text too much for readablility.
  • Any other place in the middle of a line where kerning or tabbing is needed.
Sometimes I think it is a defect in HTML that it always ignores all spaces over 1 & that altering that behavior is so cumbersome.

It if were not so well entrenched, I would suggest '_' & that we use '/' for italics; but I am sure it is too late to consider changing.

-- RickArchibald - 08 Jan 2004

It would be better to be literal and not use shorthand at all. For examaple if the user types 5 spaces, the render module converts that to ' &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;' . Extending the idea, mulitple blank lines would be converted to empty paragraphs (<p> </p>)

-- MattWilkie - 09 Jan 2004

TWiki already preserves white space in =monospaced font text=, e.g. This text  has   more    and     more      spaces

-- PeterThoeny - 10 Mar 2004

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2004-03-10 - PeterThoeny
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.