Difference between revisions of "Talk:HXT"
(need help for weird line breaks) |
(reports isXText→isText correction) |
||
| Line 8: | Line 8: | ||
I am unable to fix the weird line breaks, e.g., "are a very BREAK powerful and sometimes a more elegant" [[User:K001|K001]] 09:51, 1 February 2011 (UTC) |
I am unable to fix the weird line breaks, e.g., "are a very BREAK powerful and sometimes a more elegant" [[User:K001|K001]] 09:51, 1 February 2011 (UTC) |
||
| + | |||
| + | 4 years later, I have corrected incorrect uses of isXText to isText (they are in section 6), while retaining correct uses of isXText (they are in section 4). P.S. Do not worry about wrong paragraph breaks and missing paragraph breaks, they are caused by nearby <hask>s, they are here to stay. See [[MigratingWikiContent]], compare source code and result. |
||
| + | |||
| + | -- [[User:Treblacy|Treblacy]] 02:05, 1 February 2012 (UTC) |
||
Latest revision as of 02:05, 1 February 2012
Oh crap. I couldn't get the examples to work, as the isText in the DOM module requires a string argument. I replaces isText with isXText, but I now realize that the .Arrow module recycles many of the names from DOM for its own purposes, so I may have been to uncritically revising things. Could somebody who groks HXT please revise my revision, and roll back any incorrectnesses I may have introduced?
--Ketil 11:38, 31 May 2007 (UTC)
Ketil: Are you talking about isText, or hasText?
--BMeph 18:14, 14 September 2007 (UTC)
I am unable to fix the weird line breaks, e.g., "are a very BREAK powerful and sometimes a more elegant" K001 09:51, 1 February 2011 (UTC)
4 years later, I have corrected incorrect uses of isXText to isText (they are in section 6), while retaining correct uses of isXText (they are in section 4). P.S. Do not worry about wrong paragraph breaks and missing paragraph breaks, they are caused by nearby <hask>s, they are here to stay. See MigratingWikiContent, compare source code and result.
-- Treblacy 02:05, 1 February 2012 (UTC)