And if you're not the one who typed the text? We quote things that we didn't type, we code block code we didn't type... surely its not unfathomable the desire to up-case or down-case a list of hashes, a list of IDs, a list of file names, etc., that you're just pasting in and not typing in real time.
Do you mind sharing any specifics on what leads to the summarization as "unfortunately?" Wouldn't moving the JavaScript to the end of the page just give us the chance to see the un-transformed text, before then seeing the transformed text, by not transforming it until after the document was completed? And when the duplicate IDs never actually exist within the DOM because the code addresses this point, is there still even an issue there? Thanks.
[lower]{TEXT;postFilter=strtolower}[/lower]
[lower]{TEXT;postFilter=strtolower #createParagraphs=true}[/lower]
preFilter=
or postFilter=
) over the value, the line breaks are removed.[lower]{TEXT}[/lower]
<span style="text-transform: lowercase;">{TEXT}</span>
styles/your_style/theme/common.css
and use that instead within the html replacement: <span class="lower">{TEXT}</span>
Code: Select all
.lower {
text-transform: lowercase;
}
Yeah, I fell into that hole, too. They already clarified the existence of the CSS solution in their top post, and the intention to use this alternative solution instead. I've been assuming "original text is not modified" means (for them) there is some importance to the page content actually being the modified text; e.g. some particular scenario or platform in which a cut-n-paste or other action would continue to get the original non-CSS-transformed text instead of the intended modification to the text.