Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.
@@ -23,11 +23,9 @@ The “canonical” editor for PO files is [GNU Emacs](https://www.gnu.org/softw
...
@@ -23,11 +23,9 @@ The “canonical” editor for PO files is [GNU Emacs](https://www.gnu.org/softw
## Notes
## Notes
* The PO files also need to be transformed to Machine Object (MO) files that are then used by the [gettext](https://www.gnu.org/software/gettext/) library. This step is taken care of by GitLab CI. In other words, MO files should never be committed to GitLab.
* The PO files also need to be transformed to Machine Object (MO) files that are then used by the [gettext](https://www.gnu.org/software/gettext/) library. This step is taken care of by GitLab CI. In other words, MO files should never be committed to GitLab.
* The above procedure assumes that the (old version of) PO file already exists. The following command was used for creating the initial version:
* The above procedure assumes that the (old version of) PO file already exists. Its initial version can be created by
* Different date format for each of the two languages can be used via `locale_date_format` function from `common.R`. It returns the formatting string according to current `LC_TIME` locale (`%-d. %B %Y` for `cs`, `%B %-d, %Y` for `en` and as a fallback):
* Different date format for each of the two languages can be used via `locale_date_format` function from `common.R`. It returns the formatting string according to current `LC_TIME` locale (`%-d. %B %Y` for `cs`, `%B %-d, %Y` for `en` and as a fallback):