Snicker Comments
-
- Master Bludit
- Posts: 106
- Joined: Tue Dec 25, 2018 8:07 pm
- Been thanked: 3 times
Hellow,
I'm really sorry for the long wait and troubles. Can you please send me your cs_CZ.json file?
I tested this on my own and it worked without any problems (changing Bludit to "Čeština" using cs, cs_CZ as locale value, with an own created cs_CZ.json snicker-language file). I guess there are some issues on your translation file directly.
Thanks for your patience.
Sincerely,
Sam.
I'm really sorry for the long wait and troubles. Can you please send me your cs_CZ.json file?
I tested this on my own and it worked without any problems (changing Bludit to "Čeština" using cs, cs_CZ as locale value, with an own created cs_CZ.json snicker-language file). I guess there are some issues on your translation file directly.
Not really, I'm using the same language system as Bludit, just adapted to be string-secure and in a plugin-based context to prevent overwriting of existing strings. It's also easier for the translation tool I'm using for my plugins, but that's just a side effect.
Thanks for your patience.
Sincerely,
Sam.
-
- Master Bludit
- Posts: 106
- Joined: Tue Dec 25, 2018 8:07 pm
- Been thanked: 3 times
Hello,
I've already sent you the valid Czech `cs_CZ.json` language file directly via E-Mail (8th of February), this took a bit longer since I didn't update my E-Mail address here on the Bludit Forums (So I didn't see the mail, I've fixed it now). Sorry for that.
I've sent it to you again using the right E-Mail address.
The issue was, your JSON document was not valid, thus Bludit skipped it completely. JSON uses a really strict syntax, a missing comma, a not-escaped character or anything else will destroy the document completely.
Please use a JSON Linter / Validator such as
https://jsonlint.com/
https://jsonformatter.curiousconcept.com/
or write your language files in a Syntax-Checking Editor like
https://atom.io/
Thanks, sorry for waiting.
Sincerely,
Sam.
I've already sent you the valid Czech `cs_CZ.json` language file directly via E-Mail (8th of February), this took a bit longer since I didn't update my E-Mail address here on the Bludit Forums (So I didn't see the mail, I've fixed it now). Sorry for that.
I've sent it to you again using the right E-Mail address.
The issue was, your JSON document was not valid, thus Bludit skipped it completely. JSON uses a really strict syntax, a missing comma, a not-escaped character or anything else will destroy the document completely.
Please use a JSON Linter / Validator such as
https://jsonlint.com/
https://jsonformatter.curiousconcept.com/
or write your language files in a Syntax-Checking Editor like
https://atom.io/
Thanks, sorry for waiting.
Sincerely,
Sam.
-
- Master Bludit
- Posts: 106
- Joined: Tue Dec 25, 2018 8:07 pm
- Been thanked: 3 times
Hellow,
you're right, that's really confusing. The answer field applies to the Captcha of course, the second is the action button to answer to a comment.
I'll rename this in a future update.
Thanks.
Sincerely,
Sam.
PS.: https://github.com/pytesNET/snicker/issues/32
you're right, that's really confusing. The answer field applies to the Captcha of course, the second is the action button to answer to a comment.
I'll rename this in a future update.
Thanks.
Sincerely,
Sam.
PS.: https://github.com/pytesNET/snicker/issues/32
Hello Sam,
one small improvement - line 199:
And please be in the next update Subscription, Registration and Email notification?
thanks
one small improvement - line 199:
Code: Select all
"Written by <b>%s<\/b>",
thanks