Okay, I actually put in a fixlogstrings thing into Parser-3.0, but it's currently not activated due to political reasons (rophy thinks it's bad karma).
It's very similar to SW_FixLogStrings, only a bit faster.
Basically, the reason it'd be bad to update is that if some other third-party parser read the global strings, it was fixed, and the event run, said parser wouldn't read it possibly. This is solved, of course, by running the fix before anything else. So, it has the potential to break other addons, but if it isn't done, then some strings are ambiguous and the parsing is fucked anyway.
I dont think I'm the only one who agree an addon should avoid breaking other addons whenever possible.
With an external FixLogStrings, if you want to fix your combat log, you use it; if you don't want, don't use it, nothing breaks for not using it, no change required except adding OptionalDeps.
I don't see why it should be included in Parser-3.0, when Parser-3.0 needs nothing from FixLogStrings to work.
Sure, the same can be done in Parser-3.0 and adding OptionalDeps to all addons, but if everyone think including the fix in their own addon is a good idea, then SWStats will have an inline FixLogString, ParserLib has an inline FixLogString, Parser-3.0 has an inline FixLogString, along with 100 other addons which parse combat logs, now who should load first?
I don't think "an addon should not break other addon whenever possible" is poltical,
"if you don't follow my standard, I kill you" looks more political to me.