Contest name renderer

[zen0wu]

Contest name renderer

[wookayin]

In my humble opinion, I'd prefer to respect the contest name provided by arena as-is.

[vexorian]

It would be an optional thing.

[zen0wu]

In fact, I've implemented this function. An abbr string renderer by ${XXX;string(abbr)}. It can transform Single Round Match to SRM. Do you think this is enough?

[vexorian]

It seems it works. Have you considered making it remove special characters? Some TCO matches have ' on them.

[zen0wu]

About the special characters you mentioned, do you think just removing them should be enough?
Then it would have a hard-coded special characters list, because controlling which characters are removed in the parameters of the renderer may not be a realistic solution.

This is not a simple problem if we want to cover more situations, because the user may have various thoughts about how to normalise the name. I think we should bring more consideration into this problem. For example, from Single Round Match 123, user may want SRM123, or SRM 123, or srm123. The SRM 123 may not be achievable by now.

[vexorian]

Hence why my first idea was a special renderer :)

TCO matches are rare, so I think I can live with just the abbvr renderer.

On Thu, Nov 14, 2013 at 8:01 AM, Shiva Wu [email protected] wrote:

About the special characters you mentioned, do you think just removing
them should be enough?
Then it would have a hard-coded special characters list, because
controlling which characters are removed in the parameters of the renderer
may not be a realistic solution.

This is not a simple problem if we want to cover more situations, because
the user may have various thoughts about how to normalise the name. I think
we should bring more consideration into this problem. For example, from Single
Round Match 123, user may want SRM123, or SRM 123, or srm123. The SRM 123may not be achievable by now.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/65#issuecomment-28478572
.

[vexorian]

hmnn a small issue is that it abbreviates TCO11 into "T".

[zen0wu]

OK, so the rules should be "ignoring the abbreviation when this token is all uppercase OR digits". Is this enough?

[vexorian]

That's probably it, if you want to. As I said TCO matches are rare so I can live with this.