Details
-
Type: Improvement
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Component/s: None
-
Labels:None
Description
We should update the translator to reject translations containing strings that are pretty exclusive to malicious code. The translator should reject the translation and give the user a warning. Illegal terms include:
- <?php
- <script
Also,
- var1 (or var2, var3, etc.) should only ever exist to be translated properly to %1$s, %2$s, etc. If they end up being var1, var2, var3 in the translation, then this should be an error too
Activity
Jonathan Reissmueller
created issue -
Tyson Phillips (Inactive)
made changes -
Field | Original Value | New Value |
---|---|---|
Description |
We should update the translator to reject translations containing strings that are pretty exclusive to malicious code. The translator should reject the translation and give the user a warning. Illegal terms include:
* <?php * <script * |
We should update the translator to reject translations containing strings that are pretty exclusive to malicious code. The translator should reject the translation and give the user a warning. Illegal terms include:
* <?php * <script Also, * var1 (or var2, var3, etc.) should only ever exist to be translated properly to %1$s, %2$s, etc. If they end up being var1, var2, var3 in the translation, then this should be an error too |