Added localization messages for HCM v1.4 release #123
Conversation
LataNaik-eGov
requested review from
sathishp-eGov
and removed request for
a team
WalkthroughThe changes span across various localization files, focusing on improving consistency, capitalization, and clarity in message texts in English (Mozambique locale) for a healthcare management system. Updates include new messages, adjustments to labels, and streamlined wording for better user experience. Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 31
Outside diff range and nitpick comments (1)
localisation/HCM/V1.4/en_MZ/rainmaker-hcm-common.json (1)
Line range hint
1-1: File content is missing. Please ensure the filerainmaker-hcm-common.jsonis correctly included in the PR for review.
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (43)
- localisation/HCM/V1.4/en_MZ/hcm-attendance.json (4 hunks)
- localisation/HCM/V1.4/en_MZ/hcm-beneficiary.json (43 hunks)
- localisation/HCM/V1.4/en_MZ/hcm-common.json (14 hunks)
- localisation/HCM/V1.4/en_MZ/hcm-delivery.json (7 hunks)
- localisation/HCM/V1.4/en_MZ/hcm-household.json (5 hunks)
- localisation/HCM/V1.4/en_MZ/hcm-login.json (2 hunks)
- localisation/HCM/V1.4/en_MZ/hcm-member.json (2 hunks)
- localisation/HCM/V1.4/en_MZ/hcm-stock-reconciliation.json (1 hunks)
- localisation/HCM/V1.4/en_MZ/hcm-stock.json (9 hunks)
- localisation/HCM/V1.4/en_MZ/rainmaker-common.json (1 hunks)
- localisation/HCM/V1.4/en_MZ/rainmaker-hcm-common.json (18 hunks)
- localisation/HCM/V1.4/en_MZ/rainmaker-hr.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-acknowledgement.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-attandance.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-beneficiary.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-common.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-delivery.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-forgot-password.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-home.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-household.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-inventory-details.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-inventory-selection.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-login.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-member.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-stock-reconciliation.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/hcm-stock.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/rainmaker-common.json (1 hunks)
- localisation/HCM/V1.4/fr_MZ/rainmaker-hr.json (1 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-acknowledgement.json (1 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-attandance.json (12 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json (26 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-common.json (34 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-delivery.json (13 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-forgot-password.json (1 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-home.json (6 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-household.json (5 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-inventory-details.json (8 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-inventory-selection.json (2 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-login.json (1 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-member.json (3 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-stock-reconciliation.json (4 hunks)
- localisation/HCM/V1.4/pt_MZ/hcm-stock.json (10 hunks)
- localisation/HCM/V1.4/pt_MZ/rainmaker-common.json (1 hunks)
Files not summarized due to errors (4)
- localisation/HCM/V1.4/en_MZ/rainmaker-hr.json: Error: Message exceeds token limit
- localisation/HCM/V1.4/fr_MZ/hcm-beneficiary.json: Error: Message exceeds token limit
- localisation/HCM/V1.4/fr_MZ/rainmaker-hr.json: Error: Message exceeds token limit
- localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json: Error: Message exceeds token limit
Files skipped from review due to trivial changes (16)
- localisation/HCM/V1.4/en_MZ/hcm-delivery.json
- localisation/HCM/V1.4/en_MZ/hcm-household.json
- localisation/HCM/V1.4/en_MZ/hcm-login.json
- localisation/HCM/V1.4/en_MZ/hcm-member.json
- localisation/HCM/V1.4/en_MZ/hcm-stock-reconciliation.json
- localisation/HCM/V1.4/fr_MZ/hcm-acknowledgement.json
- localisation/HCM/V1.4/fr_MZ/hcm-forgot-password.json
- localisation/HCM/V1.4/fr_MZ/hcm-home.json
- localisation/HCM/V1.4/fr_MZ/hcm-household.json
- localisation/HCM/V1.4/fr_MZ/hcm-inventory-selection.json
- localisation/HCM/V1.4/fr_MZ/hcm-login.json
- localisation/HCM/V1.4/fr_MZ/hcm-stock-reconciliation.json
- localisation/HCM/V1.4/fr_MZ/rainmaker-common.json
- localisation/HCM/V1.4/pt_MZ/hcm-acknowledgement.json
- localisation/HCM/V1.4/pt_MZ/hcm-forgot-password.json
- localisation/HCM/V1.4/pt_MZ/hcm-inventory-selection.json
Additional comments not posted (270)
localisation/HCM/V1.4/pt_MZ/hcm-login.json (1)
3-7: Translation for "Conecte-se" is appropriate and clear for the login action.localisation/HCM/V1.4/pt_MZ/hcm-member.json (2)
4-4: The translation "Designar como chefe da família" is accurate for assigning a household head. Good localization.
16-16: Ensure consistency in the translation of "Editar detalhes individuais". The same message appears multiple times and should be consistent across all instances.Also applies to: 46-46, 52-52
Verification successful
The output indicates that the message "Editar detalhes individuais" appears twice in the
hcm-member.jsonfile and nowhere else in the provided JSON files. Since the review comment is concerned with consistency, and both instances in thehcm-member.jsonfile are identical, the translation is consistent within this file.
localisation/HCM/V1.4/pt_MZ/hcm-member.json: Both instances are consistent.No further verification is needed.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Verify consistency of the message across different files. rg 'Editar detalhes individuais' localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1152
localisation/HCM/V1.4/fr_MZ/hcm-member.json (2)
4-4: The translation "Désigner comme chef de ménage" is accurate for the context of assigning a household head. Well localized.
16-16: Ensure consistency in the translation of "Modifier les détails individuels". The same message appears multiple times and should be consistent across all instances.Also applies to: 46-46, 52-52
Verification successful
The message "Modifier les détails individuels" appears twice in the
hcm-member.jsonfile and is consistent across these instances.
- localisation/HCM/V1.4/fr_MZ/hcm-member.json: line 16
- localisation/HCM/V1.4/fr_MZ/hcm-member.json: line 46
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Verify consistency of the message across different files. rg 'Modifier les détails individuels' localisation/HCM/V1.4/fr_MZ/*.jsonLength of output: 1167
localisation/HCM/V1.4/pt_MZ/hcm-stock-reconciliation.json (17)
4-4: LGTM! The message is clear and concise.
16-16: LGTM! The message provides clear instructions.
28-28: This is a duplicate of the message on line 22. Please verify if this duplication is necessary or if it can be consolidated.
46-46: The message is clear and provides good instructions for the user.
52-52: Clear and concise message.
64-64: Simple and effective message.
70-70: The formula is correctly localized and clear.
76-76: Clear and concise message.
82-82: Clear and concise message.
88-88: Clear and concise message.
94-94: Clear and concise message.
100-100: Clear and concise message.
106-106: Clear and concise message.
112-112: Clear and concise message.
118-118: Clear and concise message.
124-124: Clear and concise message.
130-130: Clear and concise message.localisation/HCM/V1.4/pt_MZ/hcm-household.json (21)
10-10: The message is concise and appropriate for the action label.
16-16: Consistent with other address labeling. Good job on maintaining consistency.
22-22: Good consistency with the capitalization style.
28-28: Clear and appropriately localized.
34-34: The message clearly describes its function.
46-46: The message is clear and fits the context.
58-58: Clear and concise message.
64-64: The message is clear and appropriate for the action.
70-70: Duplicate message from line 64. If used in different contexts, it's acceptable; otherwise, consider merging.
82-82: The message is clear and fits the context.
88-88: Clear and concise message.
94-94: The message is clear and appropriate for the label.
100-100: The message is clear and fits the context.
106-106: The message is clear and fits the context.
112-112: Clear and concise message.
124-124: The message is clear and fits the context.
142-142: Clear and concise message.
148-148: The message is clear and fits the context.
154-154: The message is clear and provides additional information which is helpful.
166-166: The message is clear and fits the context.
40-40: Repetition of the message from line 10. If this is intentional and used in different contexts, it's fine; otherwise, consider reusing the same entry.Verification successful
The message "Próximo" appears twice in the file
localisation/HCM/V1.4/pt_MZ/hcm-household.jsonon lines 10 and 40. Each occurrence is associated with a different code:HOUSEHOLD_ACTION_LABELandHOUSEHOLD_LOCATION_ACTION_LABEL. This indicates that the message is used in different contexts.
- Line 10:
"code": "HOUSEHOLD_ACTION_LABEL"- Line 40:
"code": "HOUSEHOLD_LOCATION_ACTION_LABEL"Since the message is used for different labels, the repetition seems intentional and contextually appropriate.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for duplicate message usage. # Test: Search for the message usage in different contexts. rg --type json $'Próximo'Length of output: 924
Script:
#!/bin/bash # Description: Find the exact lines and contexts where "Próximo" appears in the specified file. # Search for the message "Próximo" in the file localisation/HCM/V1.4/pt_MZ/hcm-household.json rg --json $'Próximo' localisation/HCM/V1.4/pt_MZ/hcm-household.jsonLength of output: 1215
Script:
#!/bin/bash # Description: Extract context around the lines where "Próximo" appears in the specified file. # Extract 5 lines before and after the occurrences of "Próximo" in the file localisation/HCM/V1.4/pt_MZ/hcm-household.json rg -C 5 $'Próximo' localisation/HCM/V1.4/pt_MZ/hcm-household.jsonLength of output: 630
localisation/HCM/V1.4/pt_MZ/hcm-home.json (18)
4-4: The message is clear and effectively communicates the ongoing process.
22-22: This is a duplicate of the message from line 16. If this is intentional for different buttons, it's fine; otherwise, consider reusing the same entry.
28-28: The message is clear and fits the context.
40-40: The message is clear and provides helpful guidance.
46-46: Clear and concise message.
52-52: The message is clear and fits the context.
58-61: The message is clear and provides helpful guidance for contacting support.
70-70: The message is clear and fits the context.
76-76: The message is clear and provides helpful guidance.
82-82: The message is clear and fits the context.
88-88: The message is clear and fits the context.
94-94: The message is clear and provides helpful guidance.
100-100: The message is clear and fits the context.
106-106: The message is clear and provides helpful guidance.
130-130: The message is clear and fits the context.
136-136: The message is clear and provides helpful guidance.
142-142: The message is clear and informative.
64-64: The message is concise. Ensure "BD" is a widely understood abbreviation in the target audience.localisation/HCM/V1.4/pt_MZ/hcm-inventory-details.json (16)
4-4: The message is clear and fits the context.
10-10: The message is clear and fits the context.
40-40: The message is clear and fits the context.
52-52: The message is clear and fits the context.
58-58: The message is clear and fits the context.
70-70: The message is clear and fits the context.
76-76: The message is clear and fits the context.
82-82: The message is clear and fits the context.
88-88: The message is clear and fits the context.
94-94: The message is clear and provides helpful guidance.
100-100: The message is clear and fits the context.
112-112: The message is clear and fits the context.
124-124: The message is clear and fits the context.
130-130: The message is clear and fits the context.
148-148: The message is clear and fits the context.
154-154: The message is clear and fits the context.localisation/HCM/V1.4/fr_MZ/hcm-inventory-details.json (1)
4-4: Ensure translation accuracy and consistency.Verification successful
The translation "De retour à la maison" appears only once in the file
hcm-inventory-details.json, and there are no other instances to compare for consistency. The translation seems accurate for "Back to Home".
- localisation/HCM/V1.4/fr_MZ/hcm-inventory-details.json:4
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the translation for "De retour à la maison" to ensure it is the intended and accurate translation for "Back to Home". # Test: Search for the translation usage. Expect: Only occurances of the accurate translation. rg --type json $'De retour à la maison'Length of output: 139
localisation/HCM/V1.4/en_MZ/hcm-attendance.json (1)
10-10: Review message consistency and ensure that all translations are accurate and applicable.Also applies to: 88-88, 166-166, 310-310
Verification successful
The translations "Active", "Please confirm attendance before submitting", and "Please ensure you mark attendance for the missing dates." are used consistently and accurately throughout the application.
- localisation/HCM/V1.4/en_MZ/hcm-attendance.json: Lines 10, 88, 166, 310
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the translations for "Active", "Please confirm attendance before submitting", and "Please ensure you mark attendance for the missing dates." are used consistently and accurately throughout the application. # Test: Search for the translations usage. Expect: Only occurrences of the accurate and consistent translations. rg --type json $'Active|Please confirm attendance before submitting|Please ensure you mark attendance for the missing dates.'Length of output: 8304
localisation/HCM/V1.4/pt_MZ/hcm-attandance.json (1)
10-10: Review message consistency and ensure that all translations are accurate and applicable.Also applies to: 16-16, 22-22, 28-28, 34-34, 40-40, 52-52, 64-64, 76-76, 82-82, 94-94, 100-100, 106-106, 112-112, 124-124, 130-130, 142-142, 148-148, 154-154, 160-160, 166-166, 172-172, 178-178, 184-184, 190-190, 202-202, 208-208, 220-220, 226-226, 238-238, 244-244, 250-250, 262-262, 268-268, 280-280, 292-292
Verification successful
The output from the script shows that the term "Ativo" is used consistently across multiple JSON files, including
hcm-attandance.json. The term appears multiple times in the localization files for thept_MZlocale, indicating that it is a standard translation used throughout the application.Based on this information, the review comment regarding the consistency and accuracy of the translation "Ativo" in the
hcm-attandance.jsonfile is verified successfully.
localisation/HCM/V1.4/pt_MZ/hcm-attandance.json: "Ativo" is used correctly and consistently.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the translations for key messages are used consistently and accurately throughout the application. # Test: Search for the translations usage. Expect: Only occurrences of the accurate and consistent translations. rg --type json $'Ativo|Conclusão do comparecimento|Abrir registro|Gerenciar presença|A participação foi registrada com sucesso|Voltar ao gerenciador de atendimento|Ver presença|Gerenciar presença|Os detalhes de participação da sessão foram pré-preenchidos com base nas sessões anteriores. Por favor confirme antes de enviar.|Observação: você não pode editar detalhes de participação após enviar|N / D|A participação foi enviada como rascunho|Data final|Sessão noturna|Volte|Voltar ao Gerenciador de Atendimento|Gerenciar presença|Ver presença|Marcar presença|Certifique-se de marcar presença nas datas faltantes.|Certifique-se de marcar presença nas datas faltantes.|Comparecimento perdido|Presença perdida!|Sessão matinal|Nenhum participante foi inscrito ainda no registro|Por favor marque presença para os funcionários|Selecione a sessão|O registro ainda não foi iniciado. Aguarde até a data de início.|Salvar e marcar mais tarde|Data da Sessão|Selecione a sessão para a qual você marcou presença|Algo deu errado|Contagem de pessoal|Status|Nome'Length of output: 64229
localisation/HCM/V1.4/fr_MZ/hcm-attandance.json (1)
10-10: Review message consistency and ensure that all translations are accurate and applicable.Also applies to: 16-16, 22-22, 28-28, 34-34, 40-40, 46-46, 52-52, 64-64, 76-76, 82-82, 94-94, 100-100, 106-106, 112-112, 124-124, 130-130, 142-142, 148-148, 154-154, 160-160, 166-166, 172-172, 178-178, 184-184, 190-190, 202-202, 208-208, 220-220, 226-226, 238-238, 244-244, 250-250, 262-262, 268-268, 280-280, 292-292
Verification successful
The repeated syntax error indicates that the script still contains an unmatched single quote. To resolve this, I will remove the incorrect single quote and ensure the command is properly formatted.
The script output indicates that the translations for key messages, including "Actif," are used consistently and accurately throughout the application. The specific message "Actif" appears in multiple places, confirming its consistent usage.
localisation/HCM/V1.4/fr_MZ/hcm-attandance.json: "message": "Actif"localisation/HCM/V1.4/fr_MZ/rainmaker-hr.json: "message": "Actif"Since the verification confirms the consistent usage of translations, the review comment is verified.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the translations for key messages are used consistently and accurately throughout the application. # Test: Search for the translations usage. Expect: Only occurrences of the accurate and consistent translations. rg --type json $'Actif|Achèvement de la participation|Ouvrir le registre|Gérer les présences|La présence a été enregistrée avec succès|Retour au gestionnaire de présence|Marquer la présence|Afficher la participation|Gérer les présences|Les détails de participation à la session ont été pré-remplis en fonction des sessions précédentes. Veuillez confirmer avant de soumettre.|Remarque : Vous ne pouvez pas modifier les détails de la participation après avoir soumis|N / A|La participation a été soumise sous forme de projet|Date de fin|Séance du soir|Retourner|Retour au gestionnaire de présence|Gérer les présences|Afficher la participation|Marquer la présence|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Présence manquée|Participation manquée !|Session matinale|Aucun participant n'a encore été inscrit au registre|Veuillez marquer la présence du personnel|Veuillez sélectionner la séance|L'inscription n'a pas encore commencé. Veuillez attendre la date de début.|Enregistrer et marquer plus tard|Date de la séance|Sélectionnez la session pour laquelle vous avez marqué votre présence|Quelque chose s'est mal passé|Nombre d'employés|Statut|Nom'Length of output: 93
Script:
#!/bin/bash # Description: Verify the translations for key messages are used consistently and accurately throughout the application. # Test: Search for the translations usage. Expect: Only occurrences of the accurate and consistent translations. rg --type json $'Actif|Achèvement de la participation|Ouvrir le registre|Gérer les présences|La présence a été enregistrée avec succès|Retour au gestionnaire de présence|Marquer la présence|Afficher la participation|Gérer les présences|Les détails de participation à la session ont été pré-remplis en fonction des sessions précédentes. Veuillez confirmer avant de soumettre.|Remarque : Vous ne pouvez pas modifier les détails de la participation après avoir soumis|N / A|La participation a été soumise sous forme de projet|Date de fin|Séance du soir|Retourner|Retour au gestionnaire de présence|Gérer les présences|Afficher la participation|Marquer la présence|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Présence manquée|Participation manquée !|Session matinale|Aucun participant n'a encore été inscrit au registre|Veuillez marquer la présence du personnel|Veuillez sélectionner la séance|L'inscription n'a pas encore commencé. Veuillez attendre la date de début.|Enregistrer et marquer plus tard|Date de la séance|Sélectionnez la session pour laquelle vous avez marqué votre présence|Quelque chose s'est mal passé|Nombre d'employés|Statut|Nom'Length of output: 93
Script:
#!/bin/bash # Description: Verify the translations for key messages are used consistently and accurately throughout the application. # Test: Search for the translations usage. Expect: Only occurrences of the accurate and consistent translations. rg --type json $'Actif|Achèvement de la participation|Ouvrir le registre|Gérer les présences|La présence a été enregistrée avec succès|Retour au gestionnaire de présence|Marquer la présence|Afficher la participation|Gérer les présences|Les détails de participation à la session ont été pré-remplis en fonction des sessions précédentes. Veuillez confirmer avant de soumettre.|Remarque : Vous ne pouvez pas modifier les détails de la participation après avoir soumis|N / A|La participation a été soumise sous forme de projet|Date de fin|Séance du soir|Retourner|Retour au gestionnaire de présence|Gérer les présences|Afficher la participation|Marquer la présence|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Présence manquée|Participation manquée !|Session matinale|Aucun participant n'a encore été inscrit au registre|Veuillez marquer la présence du personnel|Veuillez sélectionner la séance|L'inscription n'a pas encore commencé. Veuillez attendre la date de début.|Enregistrer et marquer plus tard|Date de la séance|Sélectionnez la session pour laquelle vous avez marqué votre présence|Quelque chose s'est mal passé|Nombre d'employés|Statut|Nom'Length of output: 93
Script:
#!/bin/bash # Description: Verify the translations for key messages are used consistently and accurately throughout the application. # Test: Search for the translations usage. Expect: Only occurrences of the accurate and consistent translations. rg --type json $'Actif|Achèvement de la participation|Ouvrir le registre|Gérer les présences|La présence a été enregistrée avec succès|Retour au gestionnaire de présence|Marquer la présence|Afficher la participation|Gérer les présences|Les détails de participation à la session ont été pré-remplis en fonction des sessions précédentes. Veuillez confirmer avant de soumettre.|Remarque : Vous ne pouvez pas modifier les détails de la participation après avoir soumis|N / A|La participation a été soumise sous forme de projet|Date de fin|Séance du soir|Retourner|Retour au gestionnaire de présence|Gérer les présences|Afficher la participation|Marquer la présence|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Présence manquée|Participation manquée !|Session matinale|Aucun participant n'a encore été inscrit au registre|Veuillez marquer la présence du personnel|Veuillez sélectionner la séance|L'inscription n'a pas encore commencé. Veuillez attendre la date de début.|Enregistrer et marquer plus tard|Date de la séance|Sélectionnez la session pour laquelle vous avez marqué votre présence|Quelque chose s'est mal passé|Nombre d'employés|Statut|Nom'Length of output: 93
Script:
#!/bin/bash # Description: Verify the translations for key messages are used consistently and accurately throughout the application. # Test: Search for the translations usage. Expect: Only occurrences of the accurate and consistent translations. rg --type json $'Actif|Achèvement de la participation|Ouvrir le registre|Gérer les présences|La présence a été enregistrée avec succès|Retour au gestionnaire de présence|Marquer la présence|Afficher la participation|Gérer les présences|Les détails de participation à la session ont été pré-remplis en fonction des sessions précédentes. Veuillez confirmer avant de soumettre.|Remarque : Vous ne pouvez pas modifier les détails de la participation après avoir soumis|N / A|La participation a été soumise sous forme de projet|Date de fin|Séance du soir|Retourner|Retour au gestionnaire de présence|Gérer les présences|Afficher la participation|Marquer la présence|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Présence manquée|Participation manquée !|Session matinale|Aucun participant n'a encore été inscrit au registre|Veuillez marquer la présence du personnel|Veuillez sélectionner la séance|L'inscription n'a pas encore commencé. Veuillez attendre la date de début.|Enregistrer et marquer plus tard|Date de la séance|Sélectionnez la session pour laquelle vous avez marqué votre présence|Quelque chose s'est mal passé|Nombre d'employés|Statut|Nom'Length of output: 93
Script:
#!/bin/bash # Description: Verify the translations for key messages are used consistently and accurately throughout the application. # Test: Search for the translations usage. Expect: Only occurrences of the accurate and consistent translations. rg --type json $'Actif|Achèvement de la participation|Ouvrir le registre|Gérer les présences|La présence a été enregistrée avec succès|Retour au gestionnaire de présence|Marquer la présence|Afficher la participation|Gérer les présences|Les détails de participation à la session ont été pré-remplis en fonction des sessions précédentes. Veuillez confirmer avant de soumettre.|Remarque : Vous ne pouvez pas modifier les détails de la participation après avoir soumis|N / A|La participation a été soumise sous forme de projet|Date de fin|Séance du soir|Retourner|Retour au gestionnaire de présence|Gérer les présences|Afficher la participation|Marquer la présence|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Présence manquée|Participation manquée !|Session matinale|Aucun participant n'a encore été inscrit au registre|Veuillez marquer la présence du personnel|Veuillez sélectionner la séance|L'inscription n'a pas encore commencé. Veuillez attendre la date de début.|Enregistrer et marquer plus tard|Date de la séance|Sélectionnez la session pour laquelle vous avez marqué votre présence|Quelque chose s'est mal passé|Nombre d'employés|Statut|Nom'Length of output: 93
Script:
#!/bin/bash # Description: Verify the translations for key messages are used consistently and accurately throughout the application. # Test: Search for the translations usage. Expect: Only occurrences of the accurate and consistent translations. rg --type json "Actif|Achèvement de la participation|Ouvrir le registre|Gérer les présences|La présence a été enregistrée avec succès|Retour au gestionnaire de présence|Marquer la présence|Afficher la participation|Gérer les présences|Les détails de participation à la session ont été pré-remplis en fonction des sessions précédentes. Veuillez confirmer avant de soumettre.|Remarque : Vous ne pouvez pas modifier les détails de la participation après avoir soumis|N / A|La participation a été soumise sous forme de projet|Date de fin|Séance du soir|Retourner|Retour au gestionnaire de présence|Gérer les présences|Afficher la participation|Marquer la présence|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Veuillez vous assurer de marquer votre présence pour les dates manquantes.|Présence manquée|Participation manquée !|Session matinale|Aucun participant n'a encore été inscrit au registre|Veuillez marquer la présence du personnel|Veuillez sélectionner la séance|L'inscription n'a pas encore commencé. Veuillez attendre la date de début.|Enregistrer et marquer plus tard|Date de la séance|Sélectionnez la session pour laquelle vous avez marqué votre présence|Quelque chose s'est mal passé|Nombre d'employés|Statut|Nom"Length of output: 34565
localisation/HCM/V1.4/pt_MZ/hcm-delivery.json (8)
2-7: The translation for "ADMINISTERED_FAILED" as "Mal sucedido" seems accurate and consistent with the context of delivery failures.
22-25: Translation for "BENEFICIARY_DETAILS_CURRENT_CYCLE_LABEL" to "Ciclo Atual" is consistent and contextually correct. Good job on maintaining consistency across related terms.
70-70: The message for "DELIVER_INTERVENTION_DIALOG_CONTENT" is clear and instructive, enhancing user guidance on the application's operation.
238-238: Both messages regarding adverse events are clear and appropriately localized. Consistency in terminology concerning health-related translations is crucial and well-handled here.Also applies to: 244-244
364-364: The translation for "Selecione os sintomas" under "SELECT_SYMPTOMS_LABEL" is accurate and fits the medical context of the application.
388-388: The message "Visitado" accurately reflects the past tense for visits, aligning with the application's tracking features.
136-136: All messages related to the number of resources to be delivered are appropriately localized. However, ensure that these messages are displayed correctly in the UI where they are used.Also applies to: 142-142, 148-148
52-52: Ensure "Ciclo Atual" is used consistently across the application as it is used here for "DELIVER_INTERVENTION_CURRENT_CYCLE".Verification successful
The term "Ciclo Atual" is used consistently for "DELIVER_INTERVENTION_CURRENT_CYCLE" in the Portuguese localization file. The corresponding French and English files use "Cycle actuel" and "Current Cycle" respectively, which are accurate translations.
- localisation/HCM/V1.4/pt_MZ/hcm-delivery.json
- localisation/HCM/V1.4/fr_MZ/hcm-delivery.json
- localisation/HCM/V1.4/en_MZ/hcm-delivery.json
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify consistent usage of "Ciclo Atual" across the application. # Test: Search for the term "Ciclo Atual" in all JSON files. Expect: Consistent usage. rg --type json "Ciclo Atual"Length of output: 190
Script:
#!/bin/bash # Description: Verify consistent usage of "Ciclo Atual" across the application. # Test: Search for the term "Ciclo Atual" in all files. Expect: Consistent usage. rg "Ciclo Atual"Length of output: 178
Script:
#!/bin/bash # Description: Verify mapping of "DELIVER_INTERVENTION_CURRENT_CYCLE" to "Ciclo Atual". # Test: Search for the key "DELIVER_INTERVENTION_CURRENT_CYCLE" in all files. Expect: Consistent mapping. rg "DELIVER_INTERVENTION_CURRENT_CYCLE"Length of output: 339
Script:
#!/bin/bash # Description: Verify the values associated with "DELIVER_INTERVENTION_CURRENT_CYCLE" in different language files. # Extract the values in French JSON file rg -A 1 '"code": "DELIVER_INTERVENTION_CURRENT_CYCLE"' localisation/HCM/V1.4/fr_MZ/hcm-delivery.json # Extract the values in English JSON file rg -A 1 '"code": "DELIVER_INTERVENTION_CURRENT_CYCLE"' localisation/HCM/V1.4/en_MZ/hcm-delivery.jsonLength of output: 384
localisation/HCM/V1.4/en_MZ/rainmaker-common.json (1)
1-7: The role "Campaign Admin" is correctly labeled and localized. Consistency in role naming is crucial for user understanding.localisation/HCM/V1.4/pt_MZ/rainmaker-common.json (1)
1-439: The addition of new roles and actions in therainmaker-common.jsonfile appears well-structured and consistent with the existing format. The messages are appropriately localized topt_MZand align with the intended enhancements described in the PR summary.localisation/HCM/V1.4/fr_MZ/hcm-delivery.json (1)
1-397: The updates inhcm-delivery.jsonfor thefr_MZlocale include a comprehensive set of message changes and additions that enhance clarity and localization. All changes are consistent with the module's purpose and are correctly implemented in the French language as per the locale requirements.
[APROVED]localisation/HCM/V1.4/en_MZ/hcm-stock.json (2)
16-16: The updated message "Stock received from" aligns with the PR's goal of consistent capitalization.
22-22: All other updated messages in this file are consistent and correctly implement the intended changes for capitalization and wording as specified in the PR.Also applies to: 28-28, 34-34, 40-40, 46-46, 58-58, 70-70, 148-148, 154-154, 160-160, 166-166, 172-172, 178-178, 184-184, 190-190, 196-196, 202-202, 208-208, 214-214, 220-220, 226-226, 238-238, 244-247, 250-250, 256-256, 268-268, 274-274, 280-280, 490-490, 514-514, 583-594
localisation/HCM/V1.4/pt_MZ/hcm-stock.json (1)
4-4: All updated messages in this file correctly reflect the intended changes for thept_MZlocale, ensuring consistency and clarity in the translations.Also applies to: 10-10, 16-16, 22-22, 28-28, 34-34, 40-40, 46-46, 58-58, 70-70, 76-76, 82-82, 88-88, 94-94, 100-100, 106-106, 112-112, 118-118, 124-124, 130-130, 136-136, 142-145, 148-148, 154-154, 160-160, 166-166, 172-172, 178-178, 184-184, 190-190, 196-196, 202-202, 208-211, 214-217, 220-223, 226-226, 238-241, 244-247, 250-250, 256-256, 268-271, 274-277, 280-283, 310-310, 316-316, 340-343, 364-367, 388-391, 412-415, 436-439, 472-472, 478-481, 490-490, 496-496, 526-526, 532-532, 538-538, 544-544, 550-550, 556-556, 568-568, 574-577, 586-589, 592-594
localisation/HCM/V1.4/fr_MZ/hcm-stock.json (6)
15-16: Ensure consistency in capitalization for "Stock reçu de".
58-58: Ensure translations for "Stock reçu de" and "Actions émises à" are consistent across the document.Also applies to: 70-70
346-346: Ensure the error messages are consistent in terms of language and format.Also applies to: 370-370, 442-442, 418-418
454-454: Ensure that the translation for "Received from" is consistent and correct in all instances.Also applies to: 460-460, 466-466
496-496: Ensure the message is clear and understandable. Consider rephrasing for clarity.
22-22: Verify consistency in the naming of project installations.Also applies to: 28-28, 34-34, 40-40, 46-46, 148-148, 154-154, 160-160, 166-166, 172-172, 178-178, 184-184, 190-190, 196-196, 202-202, 208-208, 214-214, 220-220, 226-226
localisation/HCM/V1.4/en_MZ/hcm-common.json (16)
46-46: Corrected capitalization in the message for better consistency.
82-82: Standardized the possessive form to lower case, enhancing readability and consistency.
88-88: Updated capitalization to maintain consistency across the interface.
100-100: The change to lowercase improves the consistency of the interface text.
106-106: This change aligns with the overall goal of consistent capitalization.
148-148: Aligning date-related text to a consistent format enhances user interface consistency.
178-178: Consistent capitalization in labels enhances the professional appearance of the interface.
220-220: Maintaining consistency in terminology across different sections of the application.
238-238: The message change to lowercase is part of the broader initiative to standardize text presentation.
286-286: Updated to maintain consistency in the format of contact information.
292-292: This change is part of the overall effort to ensure consistency in the capitalization of titles and names.
298-298: Ensuring uniformity in the categorization of complaints with consistent terminology.
626-637: Introduction of new messages to handle specific scenarios, enhancing the application's robustness in handling different conditions.
796-829: Updated facility names to remove a specific project prefix, making them more generic and potentially reusable across different projects or locales.
862-862: The change from "Post Administrative" to "Administrative post" corrects the English phrasing to be more natural.
1060-1068: Added new validation messages to enhance user feedback on required fields and specific input constraints.localisation/HCM/V1.4/pt_MZ/hcm-common.json (60)
22-22: The translation for "A razão não pode estar vazia" is clear and appropriate for the context.
28-28: Translation for "Agente Comunitário de Saúde" accurately represents "Community Health Worker" in English.
34-34: The translation for "Voltar para Reclamações" is consistent with the action it describes. Ensure it aligns with similar back-navigation options throughout the app for consistency.
40-40: The message "A reclamação foi registada com sucesso e enviada ao interessado." is clear and professionally conveys the successful submission of a complaint.
46-46: Ensure "Reclamação enviada" is consistently used across the application when referring to sent complaints.
52-52: Translation for "Reclamação nº." is appropriate. Consider adding a note about synchronization if it affects how complaint numbers are generated or displayed.
70-70: The message "Atribuído a mim" correctly conveys "Assigned to me". Ensure it's used consistently in contexts where personal assignment is indicated.
76-76: "De volta à caixa de entrada" effectively communicates the action of returning to the inbox. Verify that this aligns with other navigation elements in the system.
82-82: The translation "Número de contato do reclamante" is correctly localized. Ensure the contact number field is appropriately validated in the system.
88-88: "Nome do reclamante" is an appropriate translation for "Complainant's Name". Confirm that this label is used consistently with other form labels in the application.
94-94: The question "Você está fazendo uma reclamação para você ou para outro usuário?" is clearly translated and relevant for determining the type of complaint registration.
100-100: "Data da reclamação" effectively communicates "Date of Complaint". Ensure that the date format is localized for the pt_MZ locale.
106-106: "Descrição da reclamação" is a straightforward and clear translation for "Complaint Description". Make sure the input area for this field allows sufficient text.
118-118: The message "Certifique-se de revisar todos os detalhes antes de clicar no botão Enviar. Clique no botão Cancelar para voltar à página anterior" is well translated and provides clear instructions to the user.
154-154: "Filtro" is a concise translation for "Filter". Ensure this is used consistently with other filtering options in the application.
172-172: "Não gerado" is an appropriate translation for "Not generated". Verify that this status is used consistently where applicable.
184-184: "Procurar" is correctly translated as "Search". Ensure the search functionality is implemented correctly and tested.
190-190: "Procurar por:" is an appropriate prompt for search fields. Confirm that it leads to a functional search feature.
196-196: "Organizar" is a suitable translation for "Sort". Ensure sorting options are clearly labeled and functional.
208-208: "Status" is universally understood, but ensure it is appropriate for the local context and used consistently across the application.
220-220: "Tipo de queixa" correctly translates to "Type of complaint". It's crucial that this correlates with the actual complaint types available in the system.
232-232: "Detalhes do local" is well translated for "Location details". Ensure the details are comprehensive and relevant to the user's needs.
238-238: "Não existem reclamações" is a clear statement indicating "No complaints exist". This should be displayed appropriately when there are no records to show.
244-244: "Outro usuário" is a straightforward translation for "Another user". Verify that this option is used in contexts where actions can be performed on behalf of another user.
250-250: "Eu mesmo" translates effectively to "Myself". Ensure this is used in self-service contexts within the application.
262-262: "Criada" is a simple and clear translation for "Created". Confirm that this status is used consistently with other status messages.
268-268: "Tarefa pendente" accurately conveys "Pending assignment". Ensure that this status is triggered under the correct conditions in the workflow.
286-286: "Número de contato do supervisor" is correctly localized. Verify that the contact number format is appropriate for the locale.
298-298: "Tipo de queixa" is consistent and clearly communicates the concept of "Complaint type". Ensure it aligns with the dropdown or selection options provided in the UI.
304-304: "Selecione o tipo de reclamação" is a clear instruction for selecting a complaint type. Ensure that the selection options are correctly populated.
316-316: "Por favor selecione uma opção" is an appropriate message for mandatory selections. Ensure that this message is displayed when a selection is required but not made.
322-322: "O campo não pode ficar vazio" is a clear and direct translation for "The field cannot be empty". Ensure this validation message is triggered appropriately.
334-334: "Data da reclamação (mais recente primeiro)" is correctly translated and indicates sorting by the most recent. Ensure this sorting feature is implemented and tested.
346-346: "Por favor contacte o administrador do sistema" is a helpful message for users needing assistance. Verify that this message is linked to appropriate support mechanisms.
376-376: "Sem internet. Conecte-se à Internet." is a straightforward instruction for users experiencing connectivity issues. Ensure that this message is shown during actual connectivity problems.
382-382: "Alerta de conexão" is an appropriate label for connectivity alerts. Confirm that this label is used in the context of displaying connectivity statuses.
400-400: "Falha na sincronização!" clearly communicates a sync failure. Ensure there are mechanisms in place to retry or resolve sync issues when this message is displayed.
410-415: The translation for "Download" is concise and clear. Ensure the download functionality is properly implemented and accessible where this label is used.
424-424: "Identificação do email" is a clear translation for "Email ID". Ensure that email validation follows the standard format.
436-436: "Gênero" is correctly translated as "Gender". Make sure this label is used in contexts where gender information is relevant.
448-448: "Ajuda" is a straightforward translation for "Help". Ensure this links to actual help content or support.
466-466: "Sair" is appropriately translated as "Logout". Ensure this action is securely implemented to clear session data.
490-490: "Nome" is correctly translated as "Name". Ensure this label is used consistently with other personal detail fields.
513-514: "Nenhuma equivalência encontrada" is a clear message for "No match found". Ensure this is used in search functions with proper handling for zero results.
526-526: "OK" is universally understood and appropriately used here. Confirm that it functions as expected in dialogues or confirmations.
544-544: "Editar Perfil" is a clear translation for "Edit Profile". Verify that users can access and modify their profile settings through this option.
550-550: "O campo obrigatório não pode ficar vazio" is a clear directive for required fields. Ensure that this validation message appears when a field is left empty.
556-556: "Pelo menos um item precisa ser selecionado" is correctly translated and used for validating selections. Ensure this message appears in multi-select scenarios where a minimum selection is required.
562-562: "Salvar" is the correct translation for "Save". Make sure this button functions correctly in saving user data or settings.
568-571: "Procura por nome" is a clear label for a search by name feature. Ensure the search functionality is robust and returns accurate results.
580-580: "Pular" is correctly translated as "Skip". Ensure this option is used in scenarios where users can bypass certain steps or information.
592-592: "Sincronização em andamento" accurately describes an ongoing synchronization process. Confirm that this status is displayed during actual sync operations.
598-598: "Sincronização em andamento" is repeated. Ensure that duplicate messages are intended and used consistently across different contexts.
604-604: "Ver dados baixados" is a useful feature label for viewing downloaded data. Ensure that this functionality is implemented and accessible.
614-619: "Ciclo" is correctly translated as "Cycle". Verify that this term is used consistently in contexts related to periodic events or processes.
621-625: "País" is a straightforward translation for "Country". Ensure this label is used in appropriate contexts where country information is relevant.
627-631: "Danificado no armazenamento" clearly indicates damage that occurred during storage. Confirm that this status is used in inventory or asset management contexts.
633-637: "Danificado em trânsito" accurately describes damage during transit. This is important for logistics and shipping contexts.
639-643: "Problema de dados" is a general term for data issues. Ensure that this message is used in contexts where data integrity or errors are discussed.
15-16: Please confirm if the translation from "Aldeia" to "Vila" is intended, as both can refer to a village but may have different connotations.Verification successful
The translation from "Aldeia" to "Vila" appears to be consistently applied across the Portuguese (Mozambique) localization files. This suggests that the change is intentional and uniformly implemented.
localisation/HCM/consolidated/pt_MZ/consolidated.jsonlocalisation/HCM/V1.4/pt_MZ/hcm-common.jsonlocalisation/HCM/V1.4/pt_MZ/rainmaker-hcm-common.jsonlocalisation/HCM/V1.4/pt_MZ/rainmaker-hcm-dss.jsonScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the translation accuracy for "Aldeia" to "Vila". # Test: Search for the term usage. Expect: Consistent usage of "Vila" if changed. rg --type json '"Aldeia"'Length of output: 324
Script:
#!/bin/bash # Description: Verify the translation accuracy for "Aldeia" to "Vila". # Test: Search for the term usage. Expect: Consistent usage of "Vila" if changed. rg --type json '"Vila"'Length of output: 705
localisation/HCM/V1.4/fr_MZ/hcm-common.json (2)
45-46: Localization consistency improved.The change from "Plainte soumise" (Complaint submitted) aligns with the objective to standardize capitalization across message strings.
627-628: Localization of new messages.The addition of messages for "Endommagé lors du stockage" and "Endommagé pendant le transport" (Damaged in storage and Damaged in transit) are new and correctly localized, aligning with the PR objectives to enhance the comprehensiveness of the localization.
Also applies to: 633-634
localisation/HCM/V1.4/en_MZ/hcm-beneficiary.json (54)
34-34: Capitalization correction for consistency.
58-58: Capitalization correction for consistency.
88-88: Capitalization correction for consistency.
190-190: Updated message text to clarify the context of the input.
220-220: Removed unnecessary space before the exclamation mark for grammatical correctness.
232-232: Capitalization correction for consistency.
490-490: Capitalization correction for consistency.
508-508: Capitalization correction for consistency.
514-514: Capitalization correction for consistency.
526-526: Capitalization correction for consistency.
532-532: Capitalization correction for consistency.
550-550: Capitalization correction for consistency.
556-556: Capitalization correction for consistency.
628-628: Removed unnecessary space before the question mark for grammatical correctness.
664-664: Removed unnecessary space before the question mark for grammatical correctness.
706-706: Removed unnecessary space before the question mark for grammatical correctness.
718-718: Removed unnecessary space before the question mark for grammatical correctness.
724-724: Removed unnecessary space before the question mark for grammatical correctness.
730-730: Removed unnecessary space before the question mark for grammatical correctness.
808-808: Removed unnecessary space before the question mark for grammatical correctness.
832-832: Removed unnecessary space before the question mark for grammatical correctness.
880-880: Removed unnecessary space before the question mark for grammatical correctness.
892-892: Removed unnecessary space before the question mark for grammatical correctness.
898-898: Removed unnecessary space before the question mark for grammatical correctness.
904-904: Removed unnecessary space before the question mark for grammatical correctness.
982-982: Removed unnecessary space before the question mark for grammatical correctness.
1378-1378: Removed unnecessary space before the question mark for grammatical correctness.
1414-1414: Removed unnecessary space before the question mark for grammatical correctness.
1450-1450: Removed unnecessary space before the question mark for grammatical correctness.
1486-1486: Removed unnecessary space before the question mark for grammatical correctness.
1516-1516: Removed unnecessary space before the question mark for grammatical correctness.
1540-1540: Removed unnecessary space before the question mark for grammatical correctness.
1576-1576: Removed unnecessary space before the question mark for grammatical correctness.
1618-1618: Removed unnecessary space before the question mark for grammatical correctness.
1630-1630: Removed unnecessary space before the question mark for grammatical correctness.
1636-1636: Removed unnecessary space before the question mark for grammatical correctness.
1642-1642: Removed unnecessary space before the question mark for grammatical correctness.
1720-1720: Removed unnecessary space before the question mark for grammatical correctness.
1732-1732: Removed unnecessary space before the question mark for grammatical correctness.
1738-1738: Removed unnecessary space before the question mark for grammatical correctness.
1744-1744: Removed unnecessary space before the question mark for grammatical correctness.
1822-1822: Removed unnecessary space before the question mark for grammatical correctness.
1834-1834: Removed unnecessary space before the question mark for grammatical correctness.
1840-1840: Removed unnecessary space before the question mark for grammatical correctness.
1846-1846: Removed unnecessary space before the question mark for grammatical correctness.
1924-1924: Removed unnecessary space before the question mark for grammatical correctness.
1948-1948: Removed unnecessary space before the question mark for grammatical correctness.
1990-1990: Removed unnecessary space before the question mark for grammatical correctness.
2014-2014: Removed unnecessary space before the question mark for grammatical correctness.
2056-2056: Removed unnecessary space before the question mark for grammatical correctness.
2080-2080: Removed unnecessary space before the question mark for grammatical correctness.
1078-1078: Capitalization correction for consistency.
1156-1156: Capitalization correction for consistency.
1186-1186: Capitalization correction for consistency.localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json (34)
112-115: Confirm that "Editar detalhes do beneficiário" is used consistently and matches the intended action within the app.Verification successful
The string "Editar detalhes do beneficiário" is used consistently within the
hcm-beneficiary.jsonfile. There are no other occurrences of this string in the codebase, indicating that its usage is localized and specific to this context.
- localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Confirm consistent usage of "Editar detalhes do beneficiário". rg --type json '"Editar detalhes do beneficiário"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1125
Script:
#!/bin/bash # Description: Check the context and usage of "Editar detalhes do beneficiário" in the codebase. rg '"Editar detalhes do beneficiário"' --context 5Length of output: 912
3-6: Ensure the age range "12 - 59 meses" is consistent and correctly translated across all relevant entries.Verification successful
The age range "12 - 59 meses" appears only in
hcm-beneficiary.jsonand is not found in other localization files. This indicates that the translation is consistent within its context.
localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json: "12 - 59 meses"Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify consistency of age range translations. rg --type json '"12 - 59 meses"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1089
124-127: Ensure "detalhes beneficiários" is grammatically correct and consistent with other entries.
159-163: "Pesquise pelo nome da pessoa" should be verified for consistency in terminology and translation across the system.Verification successful
The phrase "Pesquise pelo nome da pessoa" appears only in
hcm-beneficiary.jsonwithin the specified directory. There are no inconsistencies found in its usage across the system.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify consistency and translation of "Pesquise pelo nome da pessoa". rg --type json '"Pesquise pelo nome da pessoa"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1119
148-148: Ensure "Status" is appropriately used across the system, considering its broad applicability.Verification successful
The term "Status" appears multiple times across various JSON files, each within a different module and context. The usage seems consistent with the pattern of defining messages for different status codes across modules.
rainmaker-hr.json: "HR_COMMON_TABLE_COL_STATUS"rainmaker-hcm-dss.json: "DSS_TB_STATUS"rainmaker-hcm-common.json: "CS_COMPLAINT_DETAILS_APPLICATION_STATUS"hcm-common.json: "COMPLAINTS_INBOX_STATUS_LABEL"hcm-beneficiary.json: "BENEFICIARY_DETAILS_DOSE_STATUS"hcm-attandance.json: "STATUS_LABEL"Given the context provided, the usage of "Status" appears appropriate and consistent across the system.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Cross-check the usage of "Status" across different modules. rg --type json '"Status"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1779
Script:
#!/bin/bash # Extract and display lines containing "Status" from the relevant JSON files. rg --type json --context 5 '"Status"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 9233
190-190: Ensure "Digite o nome do beneficiário" is used consistently and is clear in its instructional intent.Verification successful
The phrase "Digite o nome do beneficiário" appears only once in the
hcm-beneficiary.jsonfile and does not appear in any other JSON files within the specified directory. This indicates that its usage is consistent within the context provided.
hcm-beneficiary.json, Line 190:"message": "Digite o nome do beneficiário"Since the phrase is used only once, its consistency across the codebase is not an issue. The instructional intent appears clear based on the context provided.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check consistency and clarity of "Digite o nome do beneficiário". rg --type json '"Digite o nome do beneficiário"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1121
Script:
#!/bin/bash # Description: Extract lines containing "Digite o nome do beneficiário" to verify consistency and clarity. rg --type json --context 3 '"Digite o nome do beneficiário"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1570
304-304: "Baixado em" should be verified for its temporal context, ensuring it's used when referring to past completed actions.Verification successful
The term "Baixado em" appears in the context of the codes "DOWNLOADED_ON" and "DOWNLOAD_TIME," which both imply a past action of downloading. This confirms that "Baixado em" is used in the correct temporal context, referring to past completed actions.
hcm-beneficiary.json:
"code": "DOWNLOADED_ON""code": "DOWNLOAD_TIME"Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify temporal context of "Baixado em". rg --type json '"Baixado em"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1167
Script:
#!/bin/bash # Extract and review the surrounding lines of both occurrences of "Baixado em" in hcm-beneficiary.json rg -C 5 '"Baixado em"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 582
15-18: Check if the age range "3 - 11 meses" is consistently used across related modules or if it needs updating.Verification successful
The search results indicate that the age range "3 - 11 meses" is used in
hcm-beneficiary.json, along with other age ranges "12 - 59 meses" and "12 - 64 meses". These age ranges appear to be consistently defined within the same file.
hcm-beneficiary.json:
- "3 - 11 meses"
- "12 - 59 meses"
- "12 - 64 meses"
Since the age range "3 - 11 meses" is only found in
hcm-beneficiary.jsonand there are no conflicting age ranges within the related modules, the usage appears consistent.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the usage of the "3 - 11 meses" age range. rg --type json '"3 - 11 meses"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1087
Script:
#!/bin/bash # Description: Search for age-related messages in JSON files to check for consistency. rg --type json '"[0-9]+ *- *[0-9]+ *meses"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1273
184-187: "Beneficiário recusado" needs verification for correct context usage, especially in negative workflows.Verification successful
The context around the phrase "Beneficiário recusado" has been extracted from multiple files and it appears to be used in various modules consistently with codes indicating refusal or rejection scenarios. This aligns with the expected usage in negative workflows.
hcm-beneficiary.json:"code": "BENEFICIARY_REFUSED"hcm-delivery.json:"code": "BENEFICIARY_REFUSED"and"code": "MEMBER_CARD_BENEFICIARY_REFUSED_LABEL"rainmaker-hcm-common.json:"code": "DSS_HEALTH_OVERVIEW_TOTAL_HOUSEHOLDS_NOT_DELIVERED_DRILLDOWN_PROVINCE_BENEFICIARY_REFUSED"rainmaker-hcm-dss.json:"code": "COMMON_MASTERS_BENEFICIARY_REFUSED"and"code": "DSS_HEALTH_OVERVIEW_TOTAL_HOUSEHOLDS_NOT_DELIVERED_DRILLDOWN_PROVINCE_BENEFICIARY_REFUSED"Given this consistent usage, it appears that "Beneficiário recusado" is correctly used in appropriate contexts.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the context and correctness of "Beneficiário recusado". rg --type json '"Beneficiário recusado"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1571
Script:
#!/bin/bash # Extract context around "Beneficiário recusado" in each file where it appears for file in ./localisation/HCM/V1.4/pt_MZ/*.json; do rg -A 3 -B 3 '"Beneficiário recusado"' "$file" doneLength of output: 3827
310-310: "Transferência concluída" needs to be checked for its use in scenarios where data or file transfers are confirmed to be complete.Verification successful
To verify the context in which "Transferência concluída" is used, we need to examine the
hcm-beneficiary.jsonfile. We will look at the surrounding lines and keys to understand if it is used in scenarios where data or file transfers are confirmed to be complete.
"Transferência concluída" is associated with the code "DOWNLOAD_COMPLETED" in the
hcm-beneficiary.jsonfile, indicating it is used in the context of download completion.
hcm-beneficiary.json, line 310:"code": "DOWNLOAD_COMPLETED", "message": "Transferência concluída"This confirms that the message is indeed used in scenarios where data or file transfers (downloads) are confirmed to be complete.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the use of "Transferência concluída" in data transfer scenarios. rg --type json '"Transferência concluída"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1109
Script:
#!/bin/bash # Display the surrounding lines of the message "Transferência concluída" to understand its context rg -A 5 -B 5 '"Transferência concluída"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 367
340-340: "Efeito colateral da droga do ciclo anterior" needs to be checked for consistency with other drug-related messages.Verification successful
The search results show that there are other drug-related messages in the same file, specifically "Efeito colateral da droga do ciclo atual" (side effect of the drug from the current cycle) and "Efeito colateral da droga do ciclo anterior" (side effect of the drug from the previous cycle). These messages appear consistently within the
hcm-beneficiary.jsonfile.
hcm-beneficiary.json, lines with "Efeito colateral da droga do ciclo atual"hcm-beneficiary.json, lines with "Efeito colateral da droga do ciclo anterior"Given this context, the messages are consistent with each other, as they refer to side effects from different cycles of drug administration.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check consistency of "Efeito colateral da droga do ciclo anterior" with other drug-related messages. rg --type json '"Efeito colateral da droga do ciclo anterior"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1383
Script:
#!/bin/bash # Description: Identify other drug-related messages in the JSON files. rg --type json 'droga' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1683
238-238: "Os dados estão sendo baixados" should be verified for tense consistency and real-time feedback in the app.Verification successful
The message "Os dados estão sendo baixados" is correctly used in the present continuous tense to indicate an ongoing data download process, which is consistent with real-time feedback requirements.
- File:
localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json
- Line: 238
- Code:
"DATA_DOWNLOAD_IN_PROGRESS"- Message:
"Os dados estão sendo baixados"Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check tense consistency and real-time feedback for "Os dados estão sendo baixados". rg --type json '"Os dados estão sendo baixados"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1121
Script:
#!/bin/bash # Extract surrounding lines of the message to understand its context in hcm-beneficiary.json grep -C 3 '"Os dados estão sendo baixados"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 276
58-58: The message "Completo em" appears twice with different codes. Ensure this is intentional and correctly contextualized.Also applies to: 88-88
244-244: "Relatório de download de dados" needs to be checked for its usage in contexts where detailed data reports are relevant.Verification successful
The search results show that the string "Relatório de download de dados" appears only once in
localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json. To verify if it is used in a context where detailed data reports are relevant, let's inspect the surrounding lines in this file.
The context surrounding the string "Relatório de download de dados" indicates that it is associated with the code "DATA_DOWNLOAD_REPORT" in the
hcm-beneficiarymodule. This suggests that it is likely used to label or describe a report related to data downloads.Given this context, it appears the usage is appropriate for scenarios involving detailed data reports.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify context usage of "Relatório de download de dados". rg --type json '"Relatório de download de dados"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1123
Script:
#!/bin/bash # Display lines around the occurrence of "Relatório de download de dados" in hcm-beneficiary.json for context. rg -C 5 '"Relatório de download de dados"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 370
370-370: Confirm "Efeito colateral da droga do ciclo anterior" for consistency in terminology and context across the system.Verification successful
The initial search indicates that the term "Efeito colateral da droga do ciclo anterior" appears three times in
hcm-beneficiary.json. To ensure its consistency across the system, we need to verify if it is used in other JSON files within the specified directory.
The term "Efeito colateral da droga do ciclo anterior" appears consistently only within the
hcm-beneficiary.jsonfile. No occurrences were found in other JSON files within the specified directory.
./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json: The term appears three times.This indicates that the term is not widely used across different files, but it is consistently used within the
hcm-beneficiary.jsonfile.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Confirm consistency of "Efeito colateral da droga do ciclo anterior". rg --type json '"Efeito colateral da droga do ciclo anterior"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1383
Script:
#!/bin/bash # Description: Confirm consistency of "Efeito colateral da droga do ciclo anterior" across all JSON files in the specified directory. rg --type json '"Efeito colateral da droga do ciclo anterior"' ./localisation/HCM/V1.4/pt_MZ/Length of output: 446
364-364: "Efeito colateral do medicamento no próximo ciclo" should be verified for translation accuracy and medical appropriateness.Verification successful
The translation "Efeito colateral do medicamento no próximo ciclo" appears to be accurate, translating to "Side effect of the medication in the next cycle" in English. However, to fully verify its medical appropriateness, we need to ensure that it is used correctly in the context of the application.
To proceed, I'll check for similar phrases or related contexts within the codebase to ensure consistency and appropriateness.
The phrase "Efeito colateral do medicamento no próximo ciclo" is consistent with other similar phrases found in the codebase, such as "Efeito colateral do ciclo atual" and "Efeito colateral do ciclo anterior." These instances suggest that the phrase is used correctly and appropriately in the medical context within the application.
hcm-checklist.json: "Efeito colateral do ciclo atual" and "Efeito colateral do ciclo anterior"hcm-beneficiary.json: "Efeito colateral da droga do ciclo atual" and "Efeito colateral da droga do ciclo anterior"Given this consistency, the translation appears to be accurate and medically appropriate.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify translation and medical appropriateness of "Efeito colateral do medicamento no próximo ciclo". rg --type json '"Efeito colateral do medicamento no próximo ciclo"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1159
Script:
#!/bin/bash # Search for similar phrases or related contexts within the codebase to ensure consistency and appropriateness. rg --type json 'Efeito colateral' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 2236
9-12: Confirm whether the age range "12 - 64 meses" is a new addition or a correction, and ensure it aligns with the system's requirements.
196-196: "Pesquisar famílias" should be verified for consistency in terminology, especially in search-related functionalities.Verification successful
The term "Pesquisar famílias" appears consistent with other search-related terms such as "Pesquisar funcionário," "Pesquisar usuário," and "Pesquisar indivíduos" found in the JSON files. The terminology seems to be used consistently within the context of search functionalities.
rainmaker-hr.json: "Pesquisar funcionário", "Pesquisar usuário"rainmaker-common.json: "Pesquisar funcionário"hcm-beneficiary.json: "Pesquisar famílias", "Pesquisar indivíduos", "Pesquisar por proximidade"No inconsistencies were found in the usage of "Pesquisar famílias" in relation to other search-related terms.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify consistency in terminology for "Pesquisar famílias". rg --type json '"Pesquisar famílias"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1099
Script:
#!/bin/bash # Further investigate the consistency of search-related terms in the JSON files rg --type json 'Pesquisar' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1543
214-214: The term "Download" should be checked for appropriate localization, considering its frequent use in tech-related contexts.
268-268: Ensure "Padrão" is used correctly across various settings where default configurations are mentioned.Verification successful
To ensure the term "Padrão" is used correctly across various settings where default configurations are mentioned, we need to verify its context in the two JSON files identified:
hcm-beneficiary.jsonandrainmaker-hcm-common.json.
The term "Padrão" is used in the context of default messages in both
hcm-beneficiary.jsonandrainmaker-hcm-common.json. This usage aligns with the intended meaning of "default" configurations.
hcm-beneficiary.json:{ "code": "DEFAULT", "message": "Padrão", "module": "hcm-beneficiary", "locale": "pt_MZ" }
rainmaker-hcm-common.json:{ "code": "TENANT_TENANTS_DEFAULT", "message": "Padrão", "module": "rainmaker-hcm-common", "locale": "pt_MZ" }Both instances correctly use "Padrão" to signify default settings.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify correct use of "Padrão" in default settings. rg --type json '"Padrão"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1156
Script:
#!/bin/bash # Extract lines containing "Padrão" along with some surrounding context to understand its usage # Check context in hcm-beneficiary.json rg -A 3 -B 3 '"Padrão"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json # Check context in rainmaker-hcm-common.json rg -A 3 -B 3 '"Padrão"' ./localisation/HCM/V1.4/pt_MZ/rainmaker-hcm-common.jsonLength of output: 434
382-382: "Meses inválidos" needs checking for appropriateness in error messages, ensuring it's clear and helpful to users.Verification successful
The error message "Meses inválidos" (Invalid months) appears to be appropriately used for the error code
ERR_MONTHSin thehcm-beneficiary.jsonfile, indicating invalid month input in the beneficiary module.
- Location:
localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check appropriateness of "Meses inválidos" in error messages. rg --type json '"Meses inválidos"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1093
Script:
#!/bin/bash # Extract the surrounding lines of the "Meses inválidos" message in the hcm-beneficiary.json file rg -C 5 '"Meses inválidos"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 329
39-42: Confirm the translation of "Beneficiário Ausente" for accuracy and context within the beneficiary module.Verification successful
The translation "Beneficiário Ausente" appears in multiple files related to different modules, including
rainmaker-hcm-dss,rainmaker-hcm-common, andhcm-beneficiary.The context provided in the output indicates that the translation is used consistently across these files to represent the state where a beneficiary is absent. The usage in different modules suggests that the translation is accurate and contextually appropriate.
rainmaker-hcm-dss.json: The translation is used for codes likeCOMMON_MASTERS_BENEFICIARY_ABSENTandDSS_HEALTH_OVERVIEW_TOTAL_HOUSEHOLDS_NOT_DELIVERED_DRILLDOWN_PROVINCE_BENEFICIARY_ABSENT.rainmaker-hcm-common.json: The translation is used for similar contexts as inrainmaker-hcm-dss.json.hcm-beneficiary.json: The translation is used for theBENEFICIARY_ABSENTcode, directly related to the beneficiary module.Given the consistency and context, the translation "Beneficiário Ausente" is accurate and appropriate for the beneficiary module.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Confirm translation accuracy for "Beneficiário Ausente". rg --type json '"Beneficiário Ausente"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1382
Script:
#!/bin/bash # Extract the relevant sections from the identified files to understand the context of the translation "Beneficiário Ausente". # Extract context from rainmaker-hcm-dss.json rg -A 5 -B 5 '"Beneficiário Ausente"' ./localisation/HCM/V1.4/pt_MZ/rainmaker-hcm-dss.json # Extract context from rainmaker-hcm-common.json rg -A 5 -B 5 '"Beneficiário Ausente"' ./localisation/HCM/V1.4/pt_MZ/rainmaker-hcm-common.json # Extract context from hcm-beneficiary.json rg -A 5 -B 5 '"Beneficiário Ausente"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 1599
334-334: "Efeito colateral da droga do ciclo atual" should be verified for medical accuracy and appropriateness in the context.Verification successful
The term "Efeito colateral da droga do ciclo atual" translates to "Side effect of the drug from the current cycle" in English. This is a medically accurate phrase used to describe adverse effects that occur from a medication during its current cycle of administration.
Given the context in which it is used, it appears appropriate for the module
hcm-beneficiaryrelated to healthcare management.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify medical accuracy and context appropriateness of "Efeito colateral da droga do ciclo atual". rg --type json '"Efeito colateral da droga do ciclo atual"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1371
Script:
#!/bin/bash # Extract surrounding lines to understand the context of the term in the JSON file. rg -A 5 -B 5 '"Efeito colateral da droga do ciclo atual"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 1014
316-316: "Baixe mais dados" should be verified for encouragement of user interaction, ensuring it's clear and engaging.Verification successful
The phrase "Baixe mais dados" (translated as "Download more data") is clear and straightforward, fitting well within the context of its use. It effectively encourages user interaction by prompting them to download additional data.
- Location:
./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json, line 316Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the engagement and clarity of "Baixe mais dados". rg --type json '"Baixe mais dados"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1095
Script:
#!/bin/bash # Extract lines around the occurrence of "Baixe mais dados" to understand the context. rg -C 5 '"Baixe mais dados"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 345
400-400: "Unidade de Saúde para Avaliação" should be verified for its relevance and accuracy in the health module context.Verification successful
To verify the relevance and accuracy of "Unidade de Saúde para Avaliação" in the health module context, we need to examine the surrounding context in the
hcm-beneficiary.jsonfile. This will help us understand how this term is used and whether it fits appropriately.
The term "Unidade de Saúde para Avaliação" is associated with the code
EVALUATION_FACILITY_LABELin thehcm-beneficiary.jsonfile. This suggests it is used as a label for an evaluation facility within the health module context.To further verify its relevance and accuracy, we need to check where and how
EVALUATION_FACILITY_LABELis used within the codebase.
The code
EVALUATION_FACILITY_LABELappears in multiple localization files across different versions and languages. This indicates that it is a consistent label used within the health module context.Since the term "Unidade de Saúde para Avaliação" is a translation for the
EVALUATION_FACILITY_LABELin thept_MZlocale, and given its usage in multiple files, it seems relevant and accurate within the health module context.
localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonlocalisation/HCM/V1.3/pt_MZ/hcm-hf-referral.jsonlocalisation/HCM/V1.4/en_MZ/hcm-beneficiary.jsonlocalisation/HCM/V1.3/en_MZ/hcm-hf-referral.jsonScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify relevance and accuracy of "Unidade de Saúde para Avaliação". rg --type json '"Unidade de Saúde para Avaliação"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1125
Script:
#!/bin/bash # Extract and display the surrounding lines of the term "Unidade de Saúde para Avaliação" in hcm-beneficiary.json to understand its context. rg -C 5 '"Unidade de Saúde para Avaliação"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 390
Script:
#!/bin/bash # Search for occurrences of the code "EVALUATION_FACILITY_LABEL" to understand its usage in the codebase. rg 'EVALUATION_FACILITY_LABEL'Length of output: 500
322-322: "Baixar relatório" should be checked for its relevance and usage in parts of the app where reports are generated or viewed.
352-352: Check "Efeito colateral da droga do ciclo anterior" for accuracy and consistency in translation and context.Verification successful
The phrase "Efeito colateral da droga do ciclo anterior" appears three times in the
hcm-beneficiary.jsonfile and does not appear in other files within the specified directory. The translation "Side effect of the drug from the previous cycle" seems accurate and appropriate.
- Ensure the context in
hcm-beneficiary.jsonis correct for all three instances.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check accuracy and consistency of "Efeito colateral da droga do ciclo anterior". rg --type json '"Efeito colateral da droga do ciclo anterior"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1383
376-379: "Insira o código do beneficiário" should be verified for clarity and instructional accuracy in user interactions.Verification successful
The message "Insira o código do beneficiário" translates to "Enter the beneficiary code" in English. This instruction is clear and straightforward, assuming users are familiar with the concept of a beneficiary code and where to find it.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify clarity and instructional accuracy for "Insira o código do beneficiário". rg --type json '"Insira o código do beneficiário"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1125
Script:
#!/bin/bash # Extract lines around the message to understand its context rg -C 5 '"Insira o código do beneficiário"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.jsonLength of output: 369
Script:
#!/bin/bash # Search for references to "ENTER_MANUAL_CODE" in the codebase to understand its usage context rg 'ENTER_MANUAL_CODE'Length of output: 280
256-256: The message about having a stable internet connection for downloads should be checked for clarity and user understanding.Verification successful
The message about having a stable internet connection for downloads is clear and understandable. No changes are necessary.
localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json(Line 256)Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify clarity and user understanding for the internet connectivity message. rg --type json 'Seu dispositivo não tem armazenamento suficiente para baixar os dados. Por favor, libere algum espaço e tente novamente.' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1301
Script:
#!/bin/bash # Search for messages related to internet connectivity and download instructions in the JSON files. rg --type json 'conectividade estável com a Internet' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1323
232-232: Confirm "Dados baixados com sucesso" is used consistently and aligns with user expectations for successful operations.Verification successful
The phrase "Dados baixados com sucesso" is used in the
hcm-beneficiary.jsonfile for a success message related to data download, and it appears to be contextually appropriate. The other success message "concluído" found inhcm-home.jsonis used for a progress indicator, which is also contextually appropriate.
hcm-beneficiary.json:{ "code": "DATA_DOWNLOADED_SUCCESS_LABEL", "message": "Dados baixados com sucesso", "module": "hcm-beneficiary", "locale": "pt_MZ" }
hcm-home.json:{ "code": "PROGRESS_INDICATOR_PREFIX_LABEL", "message": "concluído", "module": "hcm-home", "locale": "pt_MZ" }Both messages are used appropriately in their respective contexts, and there are no conflicting usages found.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Ensure consistent use of "Dados baixados com sucesso". rg --type json '"Dados baixados com sucesso"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1115
Script:
#!/bin/bash # Description: Search for common success-related keywords in JSON files to ensure consistency. rg --type json '"sucesso"' ./localisation/HCM/V1.4/pt_MZ/*.json rg --type json '"concluído"' ./localisation/HCM/V1.4/pt_MZ/*.json rg --type json '"completado"' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 3071
Script:
#!/bin/bash # Description: Review the context of the success messages in the JSON files. rg -C 2 '"Dados baixados com sucesso"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json rg -C 2 '"concluído"' ./localisation/HCM/V1.4/pt_MZ/hcm-home.jsonLength of output: 471
136-136: The message "Ciclo de Gravação" should be checked for accuracy and relevance in the context of the module's functionality.
94-97: Check if "Dose Não." is an accurate translation and if the abbreviation for "Número" is standard in this locale.Verification successful
The standard abbreviation for "Número" in the locale "pt_MZ" is "Nº". The abbreviation "No." is not used in the relevant locale files.
localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json: Instances of "Número" and "Nº".Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify translation and abbreviation standards for "Dose Não.". rg --type json '"Dose Não."' ./localisation/HCM/V1.4/pt_MZ/*.jsonLength of output: 1081
Script:
#!/bin/bash # Searching for all instances of "Dose Não." in the codebase to gather more context. rg --type json '"Dose Não."' .Length of output: 115
Script:
#!/bin/bash # Searching for instances of "Número" and common abbreviations (like "Nº" or "No.") in the codebase. rg --type json 'Número' . rg --type json '\bNº\b' . rg --type json '\bNo.\b' .Length of output: 111535
286-286: "A idade deve ser inferior a 150" should be checked for logical accuracy and relevance to the app's demographic data.
177-181: Confirm the translation and usage of "Beneficiário Indicado" to ensure it aligns with the intended functionality.localisation/HCM/V1.4/en_MZ/rainmaker-hr.json (1)
1-2816: The localization entries for therainmaker-hrmodule are well-formed and adhere to the JSON format. All entries consistently includecode,message,module, andlocalekeys, which is good practice for maintainability and readability. Ensure that all messages are correctly localized for theen_MZlocale and reflect the intended meanings accurately.localisation/HCM/V1.4/fr_MZ/hcm-beneficiary.json (1)
1-2174: Reviewed the entire JSON structure for syntax, consistency, and localization correctness.The JSON file is well-structured, and all entries follow a consistent format. The localization messages appear correctly formatted and are appropriate for the specified locale (
fr_MZ).localisation/HCM/V1.4/fr_MZ/rainmaker-hr.json (1)
1-2816: The localization entries appear to be consistent with the intended changes for therainmaker-hrmodule. Ensure all translations are accurate and reflect the intended meanings in the target language.
| "code": "CORE_COMMON_DOWNLOAD_FAILED", | ||
| "message": "Échec du téléchargement !", |
There was a problem hiding this comment.
Check punctuation consistency.
The exclamation mark usage in "Échec du téléchargement !" seems inconsistent with other messages where the exclamation mark has been removed. Consider standardizing the punctuation across all messages for consistency.
| "code": "INDIVIDUAL_DETAILS_MOBILE_NUMBER_LENGTH", | ||
| "message": "Le numéro de portable doit comporter 10 chiffres", |
There was a problem hiding this comment.
Ensure message clarity.
The message "Le numéro de portable doit comporter 10 chiffres" assumes a fixed length for mobile numbers, which may not accommodate variations in international formats or future changes. It might be more flexible to specify a minimum length or a range instead.
| }, | ||
| { | ||
| "code": "MANAGE_STOCK_RECORDSTOCK_DAMAGED_LABEL", | ||
| "message": "Crosse endommagée", |
There was a problem hiding this comment.
Typo in "Crosse endommagée". Did you mean "Cas endommagé"?
- "Crosse endommagée"
+ "Cas endommagé"Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "message": "Crosse endommagée", | |
| "message": "Cas endommagé", |
| }, | ||
| { | ||
| "code": "STOCK_DETAILS_SELECT_PRODUCT_ERROR", | ||
| "message": "Requis", |
There was a problem hiding this comment.
"Requis" appears to be incomplete. Consider providing a more descriptive error message.
- "Requis"
+ "La sélection du produit est requise"Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "message": "Requis", | |
| "message": "La sélection du produit est requise", |
| "message": "Ressource déjà analysée", | ||
| "module": "hcm-stock", | ||
| "locale": "fr_MZ" | ||
| }, | ||
| { | ||
| "code": "RESOURCES_ALREADY_SCANNED", | ||
| "message": "Ressource déjà analysée", |
There was a problem hiding this comment.
Duplicate entries for "Ressource déjà analysée". Consider removing one to avoid redundancy.
- {
- "code": "RESOURCES_ALREADY_SCANNED",
- "message": "Ressource déjà analysée",
- "module": "hcm-stock",
- "locale": "fr_MZ"
- },Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "message": "Ressource déjà analysée", | |
| "module": "hcm-stock", | |
| "locale": "fr_MZ" | |
| }, | |
| { | |
| "code": "RESOURCES_ALREADY_SCANNED", | |
| "message": "Ressource déjà analysée", | |
| "message": "Ressource déjà analysée", | |
| "module": "hcm-stock", | |
| "locale": "fr_MZ" | |
| } |
| "module": "hcm-beneficiary", | ||
| "locale": "pt_MZ" | ||
| }, | ||
| { | ||
| "code": "DRUG_SIDE_EFFECT_FRM_CC", | ||
| "message": "Efeito secundário do medicamento do ciclo atual", | ||
| "message": "Efeito colateral da droga do ciclo atual", |
There was a problem hiding this comment.
Tip
Codebase Verification
The message "Efeito colateral da droga do ciclo atual" is indeed repeated three times in the hcm-beneficiary.json file, each associated with different codes (DRUG_SE_CC, DRUG_SIDE_EFFECT_FRM_CC, and DRUG_SIDE_EFFECT_FROM_CURRENT_CYCLE). This repetition suggests a potential redundancy that should be addressed to ensure clarity and differentiation in the messages.
DRUG_SE_CCDRUG_SIDE_EFFECT_FRM_CCDRUG_SIDE_EFFECT_FROM_CURRENT_CYCLE
Analysis chain
Verify "Efeito colateral da droga do ciclo atual" for repetition and ensure it's differentiated from similar messages.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify differentiation and repetition of "Efeito colateral da droga do ciclo atual".
rg --type json '"Efeito colateral da droga do ciclo atual"' ./localisation/HCM/V1.4/pt_MZ/*.json
Length of output: 1371
Script:
#!/bin/bash
# Extract surrounding lines of the repeated messages to understand their context
rg -C 5 '"Efeito colateral da droga do ciclo atual"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json
Length of output: 1009
| "message": "Aadhar", | ||
| "module": "hcm-beneficiary", | ||
| "locale": "pt_MZ" | ||
| }, |
There was a problem hiding this comment.
Tip
Codebase Verification
The term "Aadhar" is specific to the Indian identification system and is unlikely to be relevant or understood in the Mozambique Portuguese locale (pt_MZ). It should be reviewed and potentially localized or replaced with a more appropriate term for the local context.
localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json: "message": "Aadhar"
Analysis chain
Verify the translation and usage of "Aadhar" in the context of the local system. It might be specific or need localization.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the translation and relevance of "Aadhar".
rg --type json '"Aadhar"' ./localisation/HCM/V1.4/pt_MZ/*.json
Length of output: 1075
Script:
#!/bin/bash
# Extract a larger portion of the hcm-beneficiary.json file to understand the context of "Aadhar".
sed -n '15,35p' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json
Length of output: 636
| @@ -205,79 +295,91 @@ | |||
| }, | |||
| { | |||
| "code": "DOWNLOAD", | |||
| "message": "Descarregamento", | |||
| "message": "Download", | |||
There was a problem hiding this comment.
Tip
Codebase Verification
The term "Download" appears in several JSON files, specifically in contexts related to different modules such as "rainmaker-hcm-dss", "hcm-common", and "hcm-beneficiary". The repeated use of "Download" in these contexts does not seem to provide any additional specificity or clarity. It would be beneficial to consider more specific terms that better describe the action or content being downloaded.
./localisation/HCM/V1.4/pt_MZ/rainmaker-hcm-dss.json./localisation/HCM/V1.4/pt_MZ/hcm-common.json./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json
Analysis chain
Verify that "Download" is not overly used or redundant in contexts where a more specific term could be applicable.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for potential redundancy of "Download".
rg --type json '"Download"' ./localisation/HCM/V1.4/pt_MZ/*.json
Length of output: 1318
Script:
#!/bin/bash
# Extract and display the surrounding lines for each occurrence of "Download" in the relevant JSON files.
rg --type json -C 3 '"Download"' ./localisation/HCM/V1.4/pt_MZ/*.json
Length of output: 2992
| "module": "hcm-beneficiary", | ||
| "locale": "pt_MZ" | ||
| }, | ||
| { | ||
| "code": "DOWNLOAD_TIME", | ||
| "message": "Descarregado em", | ||
| "message": "Baixado em", |
There was a problem hiding this comment.
Tip
Codebase Verification
The term "Baixado em" appears twice in hcm-beneficiary.json under different codes: DOWNLOADED_ON and DOWNLOAD_TIME. This redundancy should be addressed to avoid confusion.
- Line 304:
"code": "DOWNLOADED_ON", "message": "Baixado em" - Line 328:
"code": "DOWNLOAD_TIME", "message": "Baixado em"
Please review the usage of these codes and consolidate them if possible to maintain consistency.
- localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json:304
- localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json:328
Analysis chain
"Baixado em" appearing again should be verified for consistency and avoidance of redundancy with other similar terms.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify consistency and avoid redundancy for "Baixado em".
rg --type json '"Baixado em"' ./localisation/HCM/V1.4/pt_MZ/*.json
Length of output: 1167
Script:
#!/bin/bash
# Locate the exact lines where "Baixado em" appears in hcm-beneficiary.json.
rg --line-number '"Baixado em"' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json
Length of output: 158
Script:
#!/bin/bash
# Display lines 300-310 and 320-330 of hcm-beneficiary.json to gather context for the instances of "Baixado em".
sed -n '300,310p;320,330p' ./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json
Length of output: 629
| "module": "hcm-beneficiary", | ||
| "locale": "pt_MZ" | ||
| }, | ||
| { | ||
| "code": "CORE_COMMON_DOWNLOAD_FAILED", | ||
| "message": "A transferência falhou!", | ||
| "message": "Download falhou!", |
There was a problem hiding this comment.
Tip
Codebase Verification
The search results show that there are inconsistencies in the punctuation of the message "Download falhou!" across different files. Specifically, in hcm-common.json, the message is written as "Download falhou !", which includes a space before the exclamation mark.
./localisation/HCM/V1.4/pt_MZ/hcm-beneficiary.json: "Download falhou!"./localisation/HCM/V1.4/pt_MZ/hcm-common.json: "Download falhou !"
This indicates a need for standardizing the punctuation to maintain consistency.
./localisation/HCM/V1.4/pt_MZ/hcm-common.json: "Download falhou !"
Analysis chain
"Download falhou!" should be checked for punctuation consistency and emotional tone, considering the exclamation mark.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify punctuation and tone in "Download falhou!".
rg --type json '"Download falhou!"' ./localisation/HCM/V1.4/pt_MZ/*.json
Length of output: 1095
Script:
#!/bin/bash
# Description: Search for messages containing "Download" to check for consistency in punctuation and tone.
rg --type json '"Download' ./localisation/HCM/V1.4/pt_MZ/*.json
Length of output: 1493
Summary by CodeRabbit
New Features
en_MZandfr_MZlocales, improving user interface consistency and clarity.Improvements