Currently developing a Brazillian Portuguese translation for Pathfinder 2e, I noticed a couple of things that could be changed in the main system to make translation easier and more complete:
Avoid using strings that combine other strings unless it's strictly necessary, as it messes with sentence ordering. For example: the spellcasting entries are currently Type + School + Spells. In English, Innate Arcane Spells is the correct wording, but when translating the terms individually, it becomes Inato Arcano Spells, when the correct translation would be Magias Arcanas Inatas; currently not achievable.
The font being used for headers (Nodesto Caps Condensed) does not support special characters such as á, á, ã, ç, etc. If you try to use one of those, it changes back to the default font only for that character.
Some words and terms are currently not part of the translation sheet. I probably won't be able to remember and list every single one of them, but here are the ones I noticed:
Currency names
The word Spell on the spellcasting entries
Roll names on the chat. For example: Attack Roll, Check, Save Check, etc.
Spell trait names. Equipment and Feats are using the translated traits correctly, and I see the translated traits for Spells on the trait selection dropdown and details, but when I expand a spell in the spellbook and look at the trait squares, they're still the English versions.
In GitLab by @danielrbs on Apr 19, 2020, 22:14
Currently developing a Brazillian Portuguese translation for Pathfinder 2e, I noticed a couple of things that could be changed in the main system to make translation easier and more complete:
Avoid using strings that combine other strings unless it's strictly necessary, as it messes with sentence ordering. For example: the spellcasting entries are currently Type + School + Spells. In English, Innate Arcane Spells is the correct wording, but when translating the terms individually, it becomes Inato Arcano Spells, when the correct translation would be Magias Arcanas Inatas; currently not achievable.
The font being used for headers (Nodesto Caps Condensed) does not support special characters such as á, á, ã, ç, etc. If you try to use one of those, it changes back to the default font only for that character.
Some words and terms are currently not part of the translation sheet. I probably won't be able to remember and list every single one of them, but here are the ones I noticed: