This Pull Request aim to fix several translation issues in GUI Portuguese language support, addressing the translation issues I mentioned here: #507
Changes Made:
Fixed all Portuguese strings mapped in the fastflix/data/languages.yaml file.
Changed the string "Portuguese" to "Portuguese (Brazilian)" in fastflix/widgets/settings.py to accurately represent the language variant.
Known Issues:
Despite the progress made in the translation, as mentioned in the issue ticket, there are yet a few outstanding issues require attention, since they affect other languages as well:
Profiles Menu > Current Profile Settings:
All the key fields from this window does exist in the YAML file and I have already translated each of them, but the fields aren't showing the correct mapped strings after changing the GUI language in the settings menu like the rest of the GUI.
Help > About:
The following strings also are not mapped in the YAML file: "Conversion suites", "Encoders", "Supporting libraries", "Packaged with".
In the following image, there are in green 2 examples of correctly mapped strings in comparison.
Main Page > Advanced > Frame Rate section:
The "vsync" string is entirely in lowercase. I refrained from fixing this since the YAML file resolves this keyword in all languages also to 'vsync' equally and in lowercase. I think that modifying it could potentially break other parts of the application that rely on the mapping for this specyfic keyword. If it isn't the case, I would rename it to appear as 'VSync' in the GUI.
Main Page > Advanced > VBV section:
The VBV section's title mapping is split into the "Video Buffering" and "Verifier" mappings in the YAML file resulting in "Video Buffering Verifier (VBV)" in the GUI, also I have not found the last part "(VBV)" there...
Due to the fragmented mapping, it became challenging to provide an accurate translation for this field, because in pt-BR it should be "Verificador de Buffer de Vídeo (VBV)", but I have no way to put in correct order since the YAML is probably joined inside the code. The splitted translation in the YAML results in an "understandable", but still strange "Buffer de Vídeo Verificador (VBV)" pt-BR text to a native speaker, I kept this way for now but I'm documenting the problem so that in the future It could be useful to make optimizations in the languages string mapping.
Main Page > Advanced > VBV section:
The text at the end of this section is not mapped in the YAML file.
When mapped, the pt-BR translation should be "Ambos precisam estar preenchidos para serem habilitados".
Main Page > Encoding Queue > Priority:
This dropdown's values are not mapped in the YAML file.
Main Page > Encoding Queue > After Conversion:
This dropdown's values are not mapped in the YAML file.
Details
For more detailed description of these known issues and prints, please refer to #507
This Pull Request aim to fix several translation issues in GUI Portuguese language support, addressing the translation issues I mentioned here: #507
Changes Made:
Known Issues:
Despite the progress made in the translation, as mentioned in the issue ticket, there are yet a few outstanding issues require attention, since they affect other languages as well:
Profiles Menu > Current Profile Settings:
All the key fields from this window does exist in the YAML file and I have already translated each of them, but the fields aren't showing the correct mapped strings after changing the GUI language in the settings menu like the rest of the GUI.
Help > About:
The following strings also are not mapped in the YAML file: "Conversion suites", "Encoders", "Supporting libraries", "Packaged with". In the following image, there are in green 2 examples of correctly mapped strings in comparison.
Main Page > Advanced > Frame Rate section:
The "vsync" string is entirely in lowercase. I refrained from fixing this since the YAML file resolves this keyword in all languages also to 'vsync' equally and in lowercase. I think that modifying it could potentially break other parts of the application that rely on the mapping for this specyfic keyword. If it isn't the case, I would rename it to appear as 'VSync' in the GUI.
Main Page > Advanced > VBV section:
The VBV section's title mapping is split into the "Video Buffering" and "Verifier" mappings in the YAML file resulting in "Video Buffering Verifier (VBV)" in the GUI, also I have not found the last part "(VBV)" there... Due to the fragmented mapping, it became challenging to provide an accurate translation for this field, because in pt-BR it should be "Verificador de Buffer de Vídeo (VBV)", but I have no way to put in correct order since the YAML is probably joined inside the code. The splitted translation in the YAML results in an "understandable", but still strange "Buffer de Vídeo Verificador (VBV)" pt-BR text to a native speaker, I kept this way for now but I'm documenting the problem so that in the future It could be useful to make optimizations in the languages string mapping.
Main Page > Advanced > VBV section:
The text at the end of this section is not mapped in the YAML file. When mapped, the pt-BR translation should be "Ambos precisam estar preenchidos para serem habilitados".
Main Page > Encoding Queue > Priority:
This dropdown's values are not mapped in the YAML file.
Main Page > Encoding Queue > After Conversion:
This dropdown's values are not mapped in the YAML file.
Details
For more detailed description of these known issues and prints, please refer to #507
Thank you!