Manos Stoumpos

@dylannalex I've actually finished the Email one, though Date is yet to be made. You can have a go at it, it first needs some thought on the design though....

@dylannalex Looks great, good job! As for the formats, I suggest that we follow [this notation](https://en.wikipedia.org/wiki/Date_format_by_country#Table_coding). That way we can have all lowercase while at the same time we can...

> About what @alansun17904 said, I'd avoid date time values for now, since I consider it would be better to have a Date class for matching only dates and a...

> About default formats, it is impractical to hardcode all the 48 different combinations. What about adding an static method Date.date_formats() to compute all different format combinations. I think the...

Looks good! Don't worry about documentation, I can do this later. A few points: - Make sure you do (cl.AnyDigit() - "0") in "mm" and "dd" so a match with...

@dylannalex Played around with the class and it looks great. Good job. Since both "Email" and "Date" are done, I'm closing this issue.

Hey there, Sure the more the better! I am keeping this issue open so I'll remember to include this in the next version!

@sungreong Hi again! I am looking at this [Korean character set](https://memory.loc.gov/diglib/codetables/9.3.html) and I am noticing that some of these characters are missing from your RegEx. I don't know Korean, so...

Closing this issue as Korean class has been added. If something's wrong with it you can open a new issue.

Hey there, and thank you for expressing your interest! I'm certainly planning on adding a CONTRIBUTING file for the project so people can report bugs, propose modifications/additions, open pull requests...