Wrong original text?

Hi Anders,

Thank you for the suggestion. After talking with the team, we decided to go with the following:

Multiple user identities are available and the select account prompt is not available in silent signin scenario.

What is your preferred process if I find other (for me) wired original texts?
(I'm translating to Danish)

Flag them here or if you have any questions this is the place to ask them.

Thank you for translating RDM, the RDM & RDM Danish community is forever grateful.

Best regards,

Thank you - that makes sense.

I will make a post at some point with my questions :-)

Only 73% to go :-D

That is a great start. Here some motivation to help get you to the end (read below).

Please let us know when you're about 80% so we can start the process of including Danish in the official builds.

Best regards,

And if you are a most valuable contributor, we have some special prizes for you: $500 and a Remote Desktop Manager Enterprise License!

https://blog.devolutions.net/2021/11/remote-desktop-manager-is-now-available-in-japanese/

You will get a little pre-Christmas gift of some original texts that I have questions about / corrections for - of cause, based on my opinion and lack of context :)

Msg Ressouces

AnErrorOccuredWhileReadingTheAzureMFAFile
"An error occurred while reading the azure MFA file"
Should Azure be with big A?

AnUnexpectedErrorOccuredTryingToConnectToPassPortal
"An unexpected error occurred trying to connect to passportal."
What is "passportal" - is it a product? Should it be with big P

ApplicationNameMustBeAlphaNumeric
"The application name must contains alpha numeric characters or dash"
Would it be better with "may only contain"

AtLeast1ConnectionTypeMustBeChecked
"At least 1 connection type must be checked"
Would it be better with "one" instead of "1" (just my openinion)

ConnectionInfoNotProvided
"ConnectionInfo was not provided."
Should there be a space between Connection and Info?

CouldNotFindTheFolderX
Could not find the folder "{0}".
Should the double quotes be single quotes? Most places it's single quotes.

DoYouReallyWantToDeleteThisEvent
"Do your really want to delete this event?"
Should be 'you' and not 'your'

Wow, thank Anders for the valuable feedback.

AnErrorOccuredWhileReadingTheAzureMFAFile
"An error occurred while reading the azure MFA file"
Should Azure be with big A?

Fixed also fixed InvalidAzureMFAFileFormat => "Invalid Azure MFA file format"

AnUnexpectedErrorOccuredTryingToConnectToPassPortal
"An unexpected error occurred trying to connect to passportal."
What is "passportal" - is it a product? Should it be with big P

Yes, Passportal by N-able, fixed

ApplicationNameMustBeAlphaNumeric
"The application name must contains alpha numeric characters or dash"
Would it be better with "may only contain"

Fixed new value "The application name may only contain alpha numeric characters or dashes." <= added "es" to dash

AtLeast1ConnectionTypeMustBeChecked
"At least 1 connection type must be checked"
Would it be better with "one" instead of "1" (just my openinion)

The entire value is kind of odd. It's used in the Spiceworks Import wizard. I changed it to "At least one connection type must be checked." We could use something like "Please select a connection type."

ConnectionInfoNotProvided
"ConnectionInfo was not provided."
Should there be a space between Connection and Info?

No, ConnectionInfo is an internal class(object) name. Not sure why this string is translated since in theory it is debug information.

CouldNotFindTheFolderX
Could not find the folder "{0}".
Should the double quotes be single quotes? Most places it's single quotes.

Good observation, we use '{0}' 107 times and "{0}" 69 times. I will need to analysis further before doing this change to make sure can be changed without issue.

DoYouReallyWantToDeleteThisEvent
"Do your really want to delete this event?"
Should be 'you' and not 'your'

Typo, fixed

Hi again,
Not so much progress with Danish - a couple of hundreds translations or so. But here are some questions about origional texts. I think I will do this as a monthly summary to delivery it in batches:

Msg Ressouces

FailedToConnectToTheDataSourcesVPN
" Failed to connect to the data source's VPN"
Leading space should be removed?

FailedToGetChildGroupsOfActiveDirectoryGroupX
"Failed to get child groups of ActiveDirectory group {0}"
Should be Active Directory in two words.

FailedToGetFullNameOffice365UserX
"Failed to get fullname of Office365 user {0}"
Should be Office 365 in two words or maybe even Microsoft 365.

FailedToGetOffice365TokenForGraph
"Failed to get Office365 token for Graph API"
Should be Office 365 in two words or maybe even Microsoft 365.

FailedToGetOffice365TokenForSync
"Failed to get Office365 token for sync"
Should be Office 365 in two words or maybe even Microsoft 365.

FailedToGetOffice365TokenForUserX
"Failed to get Office365 token for user: {0}"
Should be Office 365 in two words or maybe even Microsoft 365.

FailedToPublishConfigurationForGatewayX
"Failed to publish configuration for Gateway: "{0}""
FailedToPublishRevocationListForGatewayX
"Failed to publish revocation list for gateway: "{0}""
Gateway has different case in these two. Should be same case.

GroupNotFoundOnDomain
"Group not found on domain"
Should this have been "in domain" - might just be me that have used this the wrong way all my life :)



UI Resources

mnuContextProperties
"P&roperties"
Probably should be "Properties" or is the & some special system marker for keyboard shortcut?

Hello,

I've fixed most of the above (removed spacing, put a space between Office and 365, set Gateway with capitals to better fit other areas of RDM).

For the domain preposition, it turns out that neither in nor on would be quite accurate as the phrasing isn't actually accurate, however it is a generically accepted cultural term (whether we use "in" or "on"), so we won't change it at this time.

For the properties, when the & is used this way, it underscores the following letter when displayed.

Regards,

Hi Jafran,
Thank you for the explination about the &, maybe it should be added into Devolutions Localizer (remotedesktopmanager.com) so people are aware of this.
Will collect more questions for my next monthly update :-)
/Anders

Hello,

That's a good idea, I'll forward this request to the documentation team and see that it is it added.

Regards,

Hello,

As you suggested, I have added the ampersand ("&") information to the Devolutions Localizer topic. Thanks for bringing this to our attention!

Best regards,

Hi Jean-Sébasten,

Awesome, thanks!

/Anders

Hi - here are my Feburary notes

MsgResouurces

Imported
"imported"
Should this be capitalized?

InvalidWakeUpOnLANIPAddress
"Invalid wake up on LAN IP address."
I think you should write "Wake on LAN" (or Wake-on-LAN) here. "Wake up on LAN" is understandable but not the offical name.

InvitationStateForgotPasswordPleaseContactYourAdministratorToRequestAnInvitation
"We detected a forgot password or a lost your phone (unpaired). In order to regain access to this Hub, please contact your administrator to request a new invitation."
Remove double spaces between sentences

KeyIsNotASupportedFormat
"The key is not a supported format"
Maybe there should have been an "in" after "not"

LoadingChocolateyDetails
"Loading chocolatey details..."
chocolatey should be with capital C

LoadingData
"Loading Data..."
I'm thinking Data should not be capitlized?

LoadingImages
"Loading Images..."
I'm thinking Images should not be capitlized?

LogOutFailedX
"LogOut failed: {0}"
Should this have been "Logoff" (to follow messages in LogOffX and LogOffFromXSessions)?

LoggingOffX
"Logging Off {0}"
Should be "off", not capitalized

MacOSXLionDoesntSupportEmbeddedRDPConnection_Information
"Please upgrade your OS version to 10.8 or above or use the External display mode."
Remove double spaces between sentences after OS

MsgAndroid_MigratingEntriesFromX
"Migrating Entries From {0}"
Entries and from should not be capitalized

MustFillAllEmployeeAndAlarmCodeFieldInAlarmCodes
"You must fill all Employee and Alarm Code fields in Alarm Codes section."
"Employee" and "Alarm Code" should not be capitalized. Maybe the same for "Alarm Codes"?

MustFillAllLocationAndCodeFieldInDoorCodes
"You must fill all Location and Code fields in Door Codes section."
"Location" and "Code" should not be capitalized. Maybe the same for "Door Codes"?

NoDVLSInstanceFound
"No Devolutions Server Instance Found"
Instance and Found should not be capitalized

EditionIsDisabledWhenThePasswordIsHidden
"Edition is disabled when the password is hidden."
I think Edition should be Editing

NoIpRangeSelectedPleaseSelectOne
"No Ip Ranged were selected. Please select at least one."
Probably should be "No IP range selected"

OpeningConnection
"Opening Connection"
Connection should not be capitalized

OpeningConnectionPleaseWait
"Opening Connection. Please wait..."
Connection should not be capitalized

PamAccountPingFailAccountXIdY
"Pam account ping failed. Username: {0}', Id: '{1}'"
Pam should be PAM

PamSshCommandNotFound
"The ssh command could not be found."
Maybe SSH in all caps?

PinWasRevealed
"Pin was revealed"
Maybe Pin in all caps?

Hello,

Thanks again for bringing this to our attention.
I've fixed several (most) of your findings, I'll specify those are are exceptions below

MsgResources

Imported - This one is intended to be lower-case (same as Pasted), although we usually specify this in the resource name, it was missed this time around.
LogOutFailedX - This one is using this specific wording because it is used in messages related to 3rd parties using those terms. So it's intended.
EditionIsDisabledWhenThePasswordIsHidden - This seems to be an outdated resource, it will eventually be deleted.

Regards,

Hi - here are my March notes. I haven't been able to do as much progress this month and April will most likely also be a little slow :)

MsgResouurces

PromptBiometricToAccessSensitiveData
"Prompt biometric to access sensitive data after 30 seconds"
Could be a little better worded, if I understand it correct. My version:
"Require biometric authentication after 30 seconds to access sensitive data"

PropertyXArrayMustNotBeEmpty
"Property {0} Array must not be empty"
Maybe Array not capitalized

PublicKeyWasCopiedInTheClipboard
"Public key content copied to the Clipboard"
PublicKeyDataWasCopiedInTheClipboard
"Public key data was copied to the clipboard"
Either clipboard with captial C or lower c
Also, tried looking it up at Microsoft but getting different results (C or c)

RdiFileDoesNotExist
Rdi file does not exist.
Thinking RDI should be capitalized

Hello,

We've fixed all the capitalization to better fit our personal usage, but we've decided not to change the wording of the biometric resource for now.
Thanks for bringing this to our attention.

Regards,