Talk:Commatizing numbers: Difference between revisions

m
→‎Layout - non breakinging space: changed spelling of "source" to "sources".
(→‎Ambiguous task spec. Oddly specific for some things while it glosses over others completely.: added comments, corrected spelling of "parameters" and "numeric".)
m (→‎Layout - non breakinging space: changed spelling of "source" to "sources".)
 
(6 intermediate revisions by 2 users not shown)
Line 40:
 
:: If there is something specific concerning what is "glossed over", I would be appreciative if they would be stated or expressed.   Addressing those specifics is what makes a better and clearer defined Rosetta Code task (rather than leave the concerns unsaid and guessed about).   I suspect the hardest part of this task is the locating/indentifying of the start and end of a numeric string (including numbers in scientific notation of any kind or persuasion ... or not) within a larger string (that is, a number with embellishments or window dressing). -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 06:00, 9 June 2014 (UTC)
 
== Layout - non breakinging space ==
 
FYI A non breaking space NBSP has total no meaning if it is surrounded by normal (breaking) spaces. More then one space makes the layout ugly and is not an common practice. There are more elegant ways to do so. Think how it will look in an other environment, browser etc.
Cheers --[[User:Siskus|Siskus]] ([[User talk:Siskus|talk]]) 06:56, 9 June 2014 (UTC)
 
: NBSP has a meaning: (one use is) it introduces a true blank that is non-compressible (multiple blanks or superfluous blanks are normally condensed to a single blank).   A double blank at sentence end and before/after certain clauses and around highlighted words aren't ugly and serve to make the text more readable and/or identifiable --- the whole purpose is to make the sentence or text clearer.   Whether or not there are more elegant ways to do so, it ''is'' the method that I use.   It doesn't matter what method is used, as long as the end product (the text) has the number of blanks that I intended to be viewed.   It is a common practice in composing text to have a double blank after a the end of a sentence, but it isn't universally followed.   Some editors use a full blank + ½ blank.   I don't know of another way to specify double blanks at sentence end (on Rosetta Code), but I know it isn't accomplished by removing the nbsp HTML keyword.   I use the nbsp keyword to make the text easy to read and understand, that's the whole purpose of composing sentences and text. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 07:26, 9 June 2014 (UTC)
 
: There is a pretty good Wikipedia entry on   [http://en.wikipedia.org/wiki/Sentence_spacing Sentence spacing]   which does a pretty good explanation on the pros and cons of the number of blanks at end-of-sentence.   More and more digital sources (Wiki for one) are apparently leaning to a one-blank sentence end, but as the Wiki article states, the few recent direct studies produced inconclusive results.   My belief is that double blanks at end-of-sentence helps readability and understanding (especially when used with highlighted text), and in no way makes it ugly.   I'm in favor of anything that makes it easier to understand or read.   A double-blank sentence end is a cheap thing to implement. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 07:46, 9 June 2014 (UTC)
 
== Table of contents ==
 
Where is the table of contents I think the author has screwed up something. Like a program you must be very exact in HTML or wikitext. I already found a </sup[[)]].
Cheers --[[User:Siskus|Siskus]] ([[User talk:Siskus|talk]]) 07:03, 9 June 2014 (UTC)
 
: Sorry, but you can't just say that I screwed up the table of contents. &nbsp; The table of contents (TOC) isn't built until some predefined number of entries (==headers==) are created (I believe the threshold is four entries). &nbsp; There is a way to force a table-of-contents, however. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 07:08, 9 June 2014 (UTC)