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.

Source strings

3,653 Strings 100%
Browse Translate
49,253 Words 100%
317,593 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
3,653 49,253 317,593
All strings Browse Translate Zen
3,653 49,253 317,593
Read-only strings Browse Translate Zen
2,738 38,462 240,501
Strings with any failing checks Browse Translate Zen
3 141 838
Failing check: Unpluralised Browse Translate Zen
19 245 1,523
Failing check: Ellipsis Browse Translate Zen
5 8 50
Failing check: Multiple failing checks Browse Translate Zen
2,737 38,461 240,494
Failing check: Long untranslated Browse Translate Zen

Other components

Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Web Interface GPL-3.0 0 0 0 0 155 0 0
Browse all components

Overview

Project website openrem.org
Instructions for translators

https://docs.openrem.org/en/latest/translations.html
Project maintainers User avatar edmcdonagh
Translation license GNU General Public License v3.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://bitbucket.org/openrem/openrem/src/develop/
Repository branch develop
Last remote commit Merge remote-tracking branch 'origin/develop' into develop da0dfc2c
User avatar edmcdonagh authored 3 weeks ago
Last commit in Weblate Added translation using Weblate (Russian) 58ed8223
User avatar gfbdrgng authored 5 months ago
Weblate repository https://hosted.weblate.org/git/openrem/read-the-docs-documentation/
File mask docs/locales/*/LC_MESSAGES/docs.po
Translation file Download docs/_build/gettext/docs.pot
Last change None
Last author None
a week ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 3,653 49,253 317,593
Translated 100% 3,653 100% 49,253 100% 317,593
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 3,653 100% 49,253 100% 317,593
Failing checks 74% 2,738 78% 38,462 75% 240,501
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 3,657 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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

49,253
Hosted words
3,653
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 None

Source string added

  1. OpenREM
  2. Read The Docs Documentation
  3. English
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

  1. OpenREM
  2. Read The Docs Documentation
  3. English
The “docs/_build/gettext/docs.pot” file was changed. a year ago
User avatar None

String updated in the repository

  1. OpenREM
  2. Read The Docs Documentation
  3. English
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

  1. OpenREM
  2. Read The Docs Documentation
  3. English
File “docs/_build/gettext/docs.pot” was added. a year ago
User avatar None

Resource updated

  1. OpenREM
  2. Read The Docs Documentation
  3. English
File “docs/_build/gettext/docs.pot” was added. a year ago
User avatar None

String updated in the repository

  1. OpenREM
  2. Read The Docs Documentation
  3. English
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

  1. OpenREM
  2. Read The Docs Documentation
  3. English
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

  1. OpenREM
  2. Read The Docs Documentation
  3. English
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

  1. OpenREM
  2. Read The Docs Documentation
  3. English
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
User avatar None

String updated in the repository

  1. OpenREM
  2. Read The Docs Documentation
  3. English
It is advisable to add an SSL certificate to the web server even though it might only be accessible within an institution. There are several reasons for this, but one main one is that over time web browsers will give more and more warnings about entering passwords into non-HTTPS websites.
It is advisable to add an SSL certificate to the web server even though it might only be accessible within an institution. There are several reasons for this, but one main one is that over time web browsers will give more and more warnings about entering passwords into non-HTTPS websites.
a year ago
Browse all translation changes