Item11556: $n newline format token doesn't seem to be expanded consistently in SEARCH formats
Current State: Confirmed
Released In: n/a
Target Release: n/a
The docco says Use $n() if followed by alphanumeric character.
detectable, given that the following char is not alphanumeric, its a
is rendered as
for some inane reason.
Mind you, It can't be that hard to detect that there's an unexpanded $ in there and work backwards until we get it.
"form.name ~ 'BlogPostForm'"
format="---+++ [[$web.$topic][$formfield(Title)]] $nby $formfield(Author) $n$formfield(Summary)$n $n$n$n$web"
Number of topics: 0
the right approach is to either make the detection cleverer, by sorting the list of tokens by length, then replacing the longest first, matching greedily, but that has a small chance of tripping up someone that relies on the quirk produced by the code we have.
To work out if that is a reasonable worry, it'll be worth testing on a number of older releases - as we re-jiggered how the processing was done a few times, which may have resulted in different corner cases.
if that approach does not fly, then we should start by replacing all
tokens that are not followed by and alphanum with
. that way at least the
cases will not be broken.
- 24 Feb 2012