• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Forwarded to devs Odd nl_NL translation in SSL It! module

Maarten

Golden Pleskian
Plesk Guru
Username:

TITLE

Odd nl_NL translation in SSL It! module

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

SSL It! Version 1.9.7-1337

Plesk Obsidian
Version 18.0.39 Update #1
CentOS Linux 7.9.2009 (Core)

PROBLEM DESCRIPTION

Open a subscription and click on "SSL/TLS Certificates"

Below Beveiligde componenten is a link to additional secured components:

en-US.php: "Show additional components to secure"

It's translated as:

nl-NL.php: "Toon de te beveiligen aanvullende componenten"

I would have expected:

"Toon de additionele componenten om te beveiligen"

STEPS TO REPRODUCE

Open a subscription and click on "SSL/TLS Certificates"

Below Beveiligde componenten is a link to additional secured components:

en-US.php: "Show additional components to secure"

It's translated as:

nl-NL.php: "Toon de te beveiligen aanvullende componenten"

ACTUAL RESULT

Open a subscription and click on "SSL/TLS Certificates"

Below Beveiligde componenten is a link to additional secured components:

nl-NL.php: "Toon de te beveiligen aanvullende componenten"

EXPECTED RESULT

Expected translation:

"Toon de additionele componenten om te beveiligen"

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
The NL translator's been our partner for over 15 years. He sells our products and knows them very well. So he's trustworthy. That's his opinion:

No, I would keep the original translation. The second one would be fine too, but it feels a bit literal. The first one sounds a bit better and is more in line with other translations. But I could live with either one.

So, leaving the original translation.
 
Back
Top