-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
verify correctness #32
Comments
same issue:
|
I am going to be going back to fix these manually, as there is an issue with a trailing space in XML that I was not aware of until after the first localizations were input. I'm going to do it manually after everything is finished. Verify version is correct is the correct terminology, it is not doing a task, it is stating something the user must do. |
In my language "verify" means "make sure [...] is correct". I thought English was the same. It's not really big of an issue, but as I'm looking at these anyway I'll mention everything catching my eye. |
That is what the string is meant to imply. You, the mod developer, need to manually look at the version, and determine if it is correct. If you mean verify sounds like saying make sure it is correct is correct, in english it's still proper. It could be conflated with things such as "Verify mod version [is valid]", for example (which this would detect automatically) so adding the is correct qualifier. |
I think it's what I meant. If you want to keep it for clarity, we're good. |
ME3TweaksModManager/MassEffectModManagerCore/modmanager/localizations/int.xaml
Line 273 in 57b730b
"Verifying correctness", both have the same meaning. A Hendiadys or similar linguistical construct.
The text was updated successfully, but these errors were encountered: