Skip to content
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

Update, sync and clean up language files; split [Press {button} to toggle gameplay] into two #1127

Merged
merged 5 commits into from
Jan 20, 2024

Conversation

Daaaav
Copy link
Contributor

@Daaaav Daaaav commented Jan 20, 2024

Changes:

  • [Press {button} to toggle gameplay] is now replaced by two strings: [Press {button} to unfreeze gameplay] and [Press {button} to freeze gameplay]
  • Synced language files, this hasn't been done since before we got some deliveries for 2.4, so there are a few languages which added apostrophes as ' instead of ' in the XML (which is not wrong, but it gives diff noise whenever there's a sync since VVVVVV writes them back as '...)
  • Added in-game mode indications (Indicate modes when loading in to gameplay #1096) to language files
  • Translated new strings to Dutch
  • Cleaned up outdated strings (these strings had been replaced over time and the original versions marked ***OUTDATED*** to allow for the original wordings to be reused by the translators who had only translated the original ones.)

Legal Stuff:

By submitting this pull request, I confirm that...

  • My changes may be used in a future commercial release of VVVVVV
  • I will be credited in a CONTRIBUTORS file and the "GitHub Friends"
    section of the credits for all of said releases, but will NOT be compensated
    for these changes

This is both easier for translators ("toggle" can be an annoying word)
and is useful in general because you can tell if gameplay is frozen
without having to have anything in the room that should normally be
moving but isn't.

I didn't follow the rule in lang/README-programmers.txt to keep the
original string around as ***OUTDATED*** in this case, since I know
only Arabic has it translated - we can just tell the Arabic translators
on Discord that this string was replaced.
This hasn't been done since before we got some deliveries for 2.4,
so there are a few languages which added apostrophes as ' instead of
' in the XML (which is not wrong, but it gives diff noise whenever
there's a sync since VVVVVV writes them back as '...)

Also, we never synced "[Press {button} to toggle gameplay]" across
language files (now two strings with unfreeze/freeze), but that was
also a pretty last-minute string as far as I remember. Arabic did have
it because that language was added after the string was added, so it
got copied from English. I don't think this one is that urgent to
translate into every language for 2.4.1 since it's pretty well hidden
for most people, and it's surrounded by things that have to be English,
so it's as if it's supposed to be like that. Let's just include these
with whatever the next batch of strings is.
These were not in the English or any other language files. They should
be though, so that they can be translated and generally kept track of.
These aren't urgent either, since we have proxy strings that are used
if these are untranslated.
These strings had been replaced over time and the original versions
marked ***OUTDATED*** to allow for the original wordings to be reused
by the translators who had only translated the original ones.
(See lang/README-programmers.txt.)

Now, these strings have all been updated in every language, so it's
time to clean them up!
@InfoTeddy InfoTeddy added the localization Implies 'required for 2.4' unless otherwise noted label Jan 20, 2024
@InfoTeddy InfoTeddy merged commit ebd4fa8 into TerryCavanagh:master Jan 20, 2024
3 checks passed
@Daaaav Daaaav deleted the sync-langfiles-2024-01-19 branch February 3, 2024 00:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
localization Implies 'required for 2.4' unless otherwise noted
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants