Kimmax
commented
6 years ago Yes there is, but 1) why 2) why alphanumeric characters?
Closed cozyplanes closed 6 years ago
Kimmax
commented
6 years ago Yes there is, but 1) why 2) why alphanumeric characters?
cozyplanes
commented
6 years ago Thats the only characters supported by comfortaa
Others become that question mark in tofu
Kimmax
commented
6 years ago Is there a way to prevent creating banners when the following characters is written in subtext?
cozyplanes
commented
6 years ago So in frontend, when unsupported character is typed in the subtext input field, show some error by js maybe, and when there is an unsupported character sent to the api directly, throw exception
cozyplanes
commented
6 years ago Or did i understood wrong?
jonasgeiler
commented
6 years ago So front and back-end?
jonasgeiler
commented
6 years ago I could do a little front-end check and display it like the user not found error. But it should be done in the back-end too!
Kimmax
commented
6 years ago Yeah @CozyPlanes basically said throw an error if the characters listed are in the text Whatever I would say we allow alphanumeric, point, comma and (), don't really need more in my opinion Catch these client side, I'll do on the backend
jonasgeiler
commented
6 years ago But there are some that do actually work. Like the nums and punctuation marks.
Is there a way to prevent creating the banner when any character not included in Comfortaa is being used? This are the characters included in Comfortaa:
If this isn't possible in the html / js , I should implement somehow in the backend
@Skayo @Kimmax