nls: Mark more strings and add translations #193
Conversation
| "PO-Revision-Date: 2024-01-24 16:12-0600\n" | ||
| "Last-Translator: none <no-one@nowhere.net>\n" | ||
| "Last-Translator: ChatGPT\n" | ||
| "Language: pt_BR\n" |
There was a problem hiding this comment.
@ph2708 What do you think of ChatGPT's translations?
|
|
|
I suppose there's no point to this until the layout is changed to account for the variable width of the translated strings. |
|
@andy5995 you can keep this open! I think supporting variable length strings is something to support sooner rather than later. We should just continue to improve the existing UI system for now to unblock improvements, until someone has time to support an alternative. I did not find a nice alternative yet. Supporting variable length strings is relatively trivial in complexity, however it is a lot of grunt work... :) I migrated a lot of the UI already - just have to call the appropriate Surface::getStringWidth/Height when creating your surface. At some point we should have a "TextSurface" that auto sets up its width and supports line wrapping - maybe that is something that can be done sooner or later. |
|
Ok, I'll have to recreate the branch |
|
Oh, a button to restore... |
|
Progress to unblock this here: #214 |
andy5995
force-pushed
the
mark-strings
branch
from
cb3e6a8
to
c767bab
Compare
andy5995
force-pushed
the
mark-strings
branch
from
c767bab
to
1d3dac3
Compare
No description provided.