Closed (fixed)
Project:
Protected Submissions
Version:
8.x-1.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Jun 2020 at 06:44 UTC
Updated:
24 Jun 2020 at 19:19 UTC
Jump to comment: Most recent
Comments
Comment #2
altagrade commentedDear kaipipek,
Thanks for reporting the issue.
When introducing the language scripts into the module we used Unicode Character Ranges. You can view all the ranges starting from line136 of the protected_submissions.module file.
Unfortunately, nobody in our team speaks Japanese, so if the existing Unicode Character Ranges are not sufficient to cover all Japanese characters, then you have to either (1) submit a patch, or (2) run several tests to find and let us know which exact UTF range the blocked character belongs to and then we'll try to include it to the module. You can see similar issue on https://www.drupal.org/project/protected_submissions/issues/3130266
Comment #3
altagrade commentedAlso I noticed there is the following UTF range:
in the module. I am not sure if
Kangxiis the same asKanjiyou reported missing, but could you please enable that range and give another try?Comment #4
kaipipek commentedI enabled Kangxi, but it didn't help. I tested with just a random Japanese text from previous emails e.g. 菅原あゆみ or 規格 ジャバラタイプ and they were rejected.
How about the other issue I mentioned, translating the "Reject message" text?
Comment #5
altagrade commentedI've just pushed number of changes to dev. Could you please remove the modules' directory, run
git clone https://git.drupalcode.org/project/protected_submissions.gitand give another try? In particular, you can now translate the module's configuration texts and also post Japanese texts like 菅原あゆみ or 規格 ジャバラタイプ by choosing CJK, Hiragana, Kana, Katakana and Latin.Comment #6
kaipipek commentedI can confirm that we can now send the Japanese messages we have tested and also the configuration texts are being translated. Great work and thank you for the quick resolution!
Comment #7
altagrade commentedThanks for confirming. I will then mark this as fixed.