= Description =

Describe the bug...
The subscript markup, `see reference,,44,,` (produces "see reference,,44,,") works great in most cases.  But there are certain places where it totally screws up.  Esp. when trying to produce subscripts in mathematical excerpts (where "indexing" is displayed as a subscripted ''i,j'', for examlpe, rather than programming language custom of [i][j] or [i,j].

== Steps to reproduce ==
Place the following markup in your text...
{{{
T1 is cv,,1,0,, pointer to cv,,1,1,, pointer to ··· cv,,1,n−1,, pointer to cv,,1,n,, T
}}}
... and this is what you get:

T1 is cv,,1,0,, pointer to cv,,1,1,, pointer to ··· cv,,1,n−1,, pointer to cv,,1,n,, T

''Pretty much it looks like most of what I __didn't__ want subscripted is a subscript, and what I __did__ want subscripted was normal text.''

Hmmm... I also just noticed that in the code box, the `-` in `n-1` shows up as a solid rectangle.  Anyone else see this?

 . I don't see the code box rectangle in firefox -- ReimarBauer <<DateTime(2008-06-09T13:23:33+0200)>>



== Example ==
So that this bug report still makes sense after a possible fix, I'm attaching a screen shot:

{{attachment:subscript_img.jpg}}

== Component selection ==

markup parsing or HTML rendering

== Details ==

## If a traceback is not available, please fill in the details here:
|| '''!MoinMoin Version''' || this wiki (version 1.7) dev. ||
|| '''Client OS''' || Windows XP ||
|| '''Browser''' || Internet Explorer 6.0.2900.2185 ||

== Workaround ==
 * Don't use comma(s) in subscripted text.
 * Don't use subscript text longer than 40 chars.

= Discussion =
The subscript parsing before the fix was broken for cases when you have a comma in the subscript or when your subscript text is longer than 40 chars. It could lead to some subscript starts being ignored and the intended subscript end being used as a ''start'' of some unintended subscript range (that unintentionally ''ended'' at some other subscript start).


= Plan =
## This part is for Moin``Moin developers:

 * Priority: 
 * Assigned to:
 * Status: fixed by http://hg.moinmo.in/moin/1.7/rev/56e6073b2e23 - please test it. If the fixed regex has less problems, we should backport this to 1.6.

----
## If you are a moin core developer, replace the category to Category* in these cases:
## Category MoinMoinNoBug - if this is not a bug.
## Category MoinMoinBugConfirmed - if you can confirm the bug on current code.
## Category MoinMoinBugFixed - after the bug is fixed in current code.
CategoryMoinMoinBugFixed