Thank you everyone for the translation work you have done so far, and hopefully will do in the future! I have created a single file for the documentation translations, rather than having to create a component for every page for the read-the-docs documentation. I have done my best to copy all the existing translations from the old individual components into the new single component - I apologise if I have missed any. Any questions, please ask! The strings should be pretty stable now, as version 1.0 is in beta release.

Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary OpenREM GPL-3.0-or-later 0 0 0 0 0 0 0
Read The Docs Documentation GPL-3.0-or-later 0 0 0 0 2,738 0 0
Web Interface GPL-3.0-or-later 0 0 0 0 155 0 0

Overview

Project website openrem.org
Instructions for translators

https://docs.openrem.org/en/latest/translations.html
Project maintainers User avatar edmcdonagh
Language English
Language code en
Text direction Left to right
Number of speakers 1,728,900,209
10 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 3,870 50,421 325,333
Approved 0% 0 0% 0 0% 0
Waiting for review 0% 0 0% 0 0% 0
Translated 100% 3,870 100% 50,421 100% 325,333
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 3,870 100% 50,421 100% 325,333
Failing checks 74% 2,893 77% 39,322 75% 246,204
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 254 changes 0 changes 3,720 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
DecJanFebMarAprMayJunJulAugSepOctNov

Quick numbers

50,421
Hosted words
3,870
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar edmcdonagh

Resource updated
The “openrem/locale/django.pot” file was changed. a year ago
User avatar None

Source string added
If you need more than one DICOM Store server, to listen on a different port for example, copy the whole ``orthanc_1`` section in ``docker-compose.yml`` and paste it after the ``orthanc_1`` block. Rename to ``orthanc_2``
a year ago
User avatar edmcdonagh

Resource updated
The “docs/_build/gettext/docs.pot” file was changed. a year ago
User avatar None

String updated in the repository
If you need more than one DICOM Store server, to listen on a different port for example, copy the whole ``orthanc_1`` section in ``docker-compose.yml`` and paste it after the ``orthanc_1`` block. Rename to ``orthanc_2``.
If you need more than one DICOM Store server, to listen on a different port for example, copy the whole ``orthanc_1`` section in ``docker-compose.yml`` and paste it after the ``orthanc_1`` block. Rename to ``orthanc_2``.
a year ago
User avatar edmcdonagh

Resource updated
File “docs/_build/gettext/docs.pot” was added. a year ago
User avatar None

Resource updated
File “docs/_build/gettext/docs.pot” was added. a year ago
User avatar None

String updated in the repository
Ensure the the following lines are updated for the name of your server and the names of your signed certificate and key:
Ensure the the following lines are updated for the name of your server and the names of your signed certificate and key:
a year ago
User avatar None

String updated in the repository
There are two conf files in ``nginx-conf/conf.d`` - the default one is ``openrem.conf``. There is an alternative one named ``openrem-secure.conf.example``. Edit the second file as required, then rename them both so the secure version is the only one to have a ``.conf`` ending.
There are two conf files in ``nginx-conf/conf.d`` - the default one is ``openrem.conf``. There is an alternative one named ``openrem-secure.conf.example``. Edit the second file as required, then rename them both so the secure version is the only one to have a ``.conf`` ending.
a year ago
User avatar None

String updated in the repository
Once you have a signed certificate, place it and the key in ``nginx-conf/certs``, where it will be available in the Nginx container at ``/etc/ssl/private``.
Once you have a signed certificate, place it and the key in ``nginx-conf/certs``, where it will be available in the Nginx container at ``/etc/ssl/private``.
a year ago
User avatar None

String updated in the repository
It is likely that within your institution there will be a corporate trusted root certificate and a mechanism of getting certificates you generate for your servers signed by that root certificate. How to generate a certificate signing request (CSR) and private key are beyond the scope of these documents, but this blog post was helpful when we were learning how to do this at our institution: https://www.endpoint.com/blog/2014/10/30/openssl-csr-with-alternative-names-one
It is likely that within your institution there will be a corporate trusted root certificate and a mechanism of getting certificates you generate for your servers signed by that root certificate. How to generate a certificate signing request (CSR) and private key are beyond the scope of these documents, but this blog post was helpful when we were learning how to do this at our institution: https://www.endpoint.com/blog/2014/10/30/openssl-csr-with-alternative-names-one
a year ago
Browse all changes for this language