-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Case Sensitive / Capital Characters #27
Comments
Adding a I'll update the database to use camel-cased keys. |
Could you please elaborate this use case bit? |
I know the value could be converted to the desired case before accessing the database, but we don't really know the use-case of the database yet. If a developer wants to get the data for |
@Mottie From my point of view we're currently doing everything that is necessary to get mark.js rolled out with the diacritics integration. If we do not have use cases for keeping |
What do we do about Edit: I set these as lower case and removed the title and uppercase entries. |
Please review. |
Currently we have an output like e.g.:
In order to keep the behavior of mark.js' regular expression creation we need to differentiate between capital and non-capital characters. For above mentioned example I could imagine an output like:
So, a new property
capital
was added andtitleCase
as well asupperCase
was removed. For the opposite -- the capital character:it could be:
What do you think @Mottie?
Btw.: I've noticed that the equivalents generation is inconsistent. We have always used camelCase (e.g.
"languageNative"
) but in the equivalents part we have e.g.html_decimal
.The text was updated successfully, but these errors were encountered: