On 1/16/07, Les Bessant <[EMAIL PROTECTED]> wrote:
Found this behaviour with the betas (it may precede them, but I didn't look
too closely before).
All posts imported from my live 2.0.x installation into a test site using
2.1.
I have a number of custom smilies, all defined in wp-config.php. As I often
string several together, not all their translations have spaces in. In fact,
hardly any do. Most are of the form ':rant:' with the surrounding colons
being enough to ensure they are only translated when I want them to.
This all works as expected in 2.0.x.
In 2.1, I find that translation does not happen unless there are spaces
around the string to be translated. So a smiley at the beginning of a
comment tends not to be translated, two in a row don't get translated, and
those inserted straight after words or punctuation don't get translated.
I found this: http://trac.wordpress.org/ticket/2444 in trac - I'm not a
coder, so I have little chance of working out what it means, but it looks
like it might be related.
Is this behaviour expected[1] or is it something that can be changed
[1] Or "by design" as Microsoft like to say about annoying "features" ;-)
Hi Les,
By implementation ;-)
I recall Nazgul working in this area. I think that ticket resulted in
another bug. I recall him describing it as surprisingly tricky.
Interpretting smiles:) in strings not at the start or end of a line or
surrounded by space is awkward, though of the form:rant: would
probably not be.
Cheers,
Lloyd
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
