-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extracted the Tiberian Dawn mission objective strings #20265
Conversation
fbeb7cf
to
b24186c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a specific idea behind splitting some mission translations into their own files instead of having everything in cnc/languages/en.ftl
? (Having only a single file seems simpler to me.)
OpenRA.Mods.Common/Scripting/Properties/MissionObjectiveProperties.cs
Outdated
Show resolved
Hide resolved
I think we should keep one file for the main campaign missions, it will be easier for translators and for us to maintain. For skirmish gamemodes or perhaps even for openra unique missions we support translations could be in the maps themselves |
Not to forget that in the future once we get proper campaign UI we will need translations for those as well on the mod (not engine) level |
How does scoping for these mission-specific translation files work? Is there any? If yes, that would be the reason to keep them separate. If we combined them we'd likely need mission-specific prefixes on the string keys like -destroy-gdi-forces = Destroy all GDI forces.
+nod03-destroy-gdi-forces = Destroy all GDI forces. |
we would more likely just add comments, like it is in mods/cnc/languages/en.ftl -nod03-destroy-gdi-forces = Destroy all GDI forces.
+#nod03
+destroy-gdi-forces = Destroy all GDI forces. |
That will only work until we start getting conflicting objectives from multiple missions. |
Applying the #20207 concept would help with that. Though in theory multiple missions shouldn't collide, if they have different wording, since variable name is based on the wording, they will have different variable names |
That would likely work, but it neither foolproof nor clean. One would need to be scouring existing strings when adding a new one, finding an unused sequence of characters like trying to register an email account. |
It's the approach we've taken on engine-level translations. Linting could be added to check for duplicates |
b24186c
to
2bb587e
Compare
I went with the monolithic file structure similar to what we already have now. |
OpenRA.Mods.Common/Scripting/Properties/MissionObjectiveProperties.cs
Outdated
Show resolved
Hide resolved
7a14a4e
to
80db408
Compare
80db408
to
85f0f4b
Compare
2434cc8
to
ab57898
Compare
Could we do the |
ab57898
to
c676a3f
Compare
c676a3f
to
6c054d7
Compare
6c054d7
to
babf99d
Compare
b041288
to
e617b66
Compare
e617b66
to
35b8bfc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm otherwise.
35b8bfc
to
a0beb5d
Compare
and enhance the Fluent Lua interface.