Conversation
Build artifacts:
|
|
Hi Johan, The previous PR was closed without merge. This new PR only adds: No changes were made to the English file. Please let me know if anything needs adjustment. Thank you! |
|
@cw-owasp Could you have a look at this? |
|
I will take a look |
|
Hi @SachinAditya I want to have a look through all of these, but we'll also encourage any other Hindi speaking volunteers to comment too. Hope you don't mind getting more eyes on it! Also, I had a look at the first card (VE2) and used G.Translate to reverse your text into English. The back translated text is: Brian may gather information about the underlying configuration, schema, logic, code, software, services, and infrastructure by examining the content of error messages, bad configurations, the presence of default installation files, old, test, backup, or copies of resources, or by exposing source code. versus the original: Brian can gather information about the underlying configurations, schemas, logic, code, software, services and infrastructure due to the content of error messages, or poor configuration, or the presence of default installation files or old, test, backup or copies of resources, or exposure of source code Are the differences which I've highlighted in bold, problems with the back translation, or are the plurals and the words "or" really missing? We use "can" in all the attacks to suggest the ability to do the attack, rather than "may" which almost suggest they are permitted to do so. |
|
Can versus May Example 2: G.Translate also suggests VE5 is "may", but it translates VE3 and VE4 as "can" which seem correct. Plural example 2: VE5 also seems to have "or the wrong encoding is being used" at the end rather than the plural "or the wrong encodings are being used" Are these just my G.Translate problems? |
|
Thank you for reviewing this carefully. In Hindi, the phrase “कर सकता है” is used consistently across all attack descriptions to indicate capability (equivalent to “can”), not permission. Google Translate sometimes renders this as “may,” but the intended meaning is “can.” Regarding plural forms, Hindi does not always explicitly distinguish plural nouns in the same structural way as English. However, the meaning includes plural concepts where the original text uses them. If needed, I am happy to slightly adjust wording to make the intended “can” meaning clearer in reverse translation. |
|
@SachinAditya Thank you very much for explaining. No need to change anything for G.Translate! I will review the rest of the cards now. One thing that will need changing though is to swap AZ9 and C9, which was recently changed in the EN version:
The cards were swapped suits due to feedback during playing the game. |
This PR adds a complete Hindi translation of the WebApp v3.0 cards.
Added:
Details:
This PR only introduces the Hindi translation file and does not modify any existing files.
Please let me know if any formatting or structural adjustments are required.