machankura/mempool
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
mempool/frontend/src/locale/messages.nb.xlf

4361 lines
250 KiB
Plaintext
Raw Normal View History

Pulling from Transifex
2021-12-09 16:42:41 +04:00
<?xml version="1.0" ?><xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<file source-language="en-US" datatype="plaintext" original="ng2.template" target-language="nb">
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<body>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.alert.close" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Close</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Lukk</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/alert/alert.ts</context>
<context context-type="linenumber">77,80</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.carousel.slide-number" datatype="html">
Pull from transifex
2022-05-19 20:12:21 +04:00
<source> Slide <x id="INTERPOLATION" equiv-text="ext(value);"/> of <x id="INTERPOLATION_1" equiv-text="turn this._wrap"/> </source>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/carousel/carousel.ts</context>
<context context-type="linenumber">147,156</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Currently selected slide number read by screen reader</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.carousel.previous" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Previous</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Forrige</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/carousel/carousel.ts</context>
<context context-type="linenumber">174</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.carousel.next" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Next</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Neste</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/carousel/carousel.ts</context>
<context context-type="linenumber">195</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.datepicker.select-month" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Select month</source>
<target>Velg måned</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/datepicker/datepicker-navigation-select.ts</context>
<context context-type="linenumber">74</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/datepicker/datepicker-navigation-select.ts</context>
<context context-type="linenumber">74</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.datepicker.select-year" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Select year</source>
<target>Velg år</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/datepicker/datepicker-navigation-select.ts</context>
<context context-type="linenumber">74</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/datepicker/datepicker-navigation-select.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">74</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.datepicker.previous-month" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Previous month</source>
<target>Forrige måned</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/datepicker/datepicker-navigation.ts</context>
<context context-type="linenumber">69</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled new strings from transifex.
2020-12-09 01:17:22 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/datepicker/datepicker-navigation.ts</context>
<context context-type="linenumber">69</context>
Pulled new strings from transifex.
2020-12-09 01:17:22 +07:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.datepicker.next-month" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Next month</source>
<target>Neste måned</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/datepicker/datepicker-navigation.ts</context>
<context context-type="linenumber">69</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/datepicker/datepicker-navigation.ts</context>
<context context-type="linenumber">69</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.pagination.first" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>««</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>««</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/pagination/pagination.ts</context>
<context context-type="linenumber">247</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.pagination.previous" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>«</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>«</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/pagination/pagination.ts</context>
<context context-type="linenumber">264,266</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.pagination.next" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>»</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>»</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/pagination/pagination.ts</context>
<context context-type="linenumber">282,285</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.pagination.last" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>»»</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>»»</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/pagination/pagination.ts</context>
<context context-type="linenumber">301,303</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.pagination.first-aria" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>First</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Første</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/pagination/pagination.ts</context>
<context context-type="linenumber">318,320</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.pagination.previous-aria" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Previous</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Forrige</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/pagination/pagination.ts</context>
<context context-type="linenumber">333</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.pagination.next-aria" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Next</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Neste</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/pagination/pagination.ts</context>
<context context-type="linenumber">343,344</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.pagination.last-aria" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Last</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Siste</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/pagination/pagination.ts</context>
<context context-type="linenumber">354</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.progressbar.value" datatype="html">
Pull from transifex
2022-05-19 20:12:21 +04:00
<source><x id="INTERPOLATION" equiv-text="@Input() te"/></source>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/progressbar/progressbar.ts</context>
<context context-type="linenumber">59,63</context>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.HH" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>HH</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>TT</target>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">133,135</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.hours" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Hours</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Timer</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">154,155</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.MM" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>MM</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>MM</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">171,172</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.minutes" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Minutes</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Minutter</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">186,187</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.increment-hours" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Increment hours</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Øk timer</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">200</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.decrement-hours" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Decrement hours</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Reduser timer</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">219,222</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.increment-minutes" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Increment minutes</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Øk minutter</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">238,239</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.decrement-minutes" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Decrement minutes</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Reduser minutter</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">259,261</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.SS" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>SS</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>SS</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">277</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.seconds" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Seconds</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Sekunder</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">295</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.increment-seconds" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Increment seconds</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Øk sekunder</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">295</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.decrement-seconds" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Decrement seconds</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Reduser sekunder</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">295</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="ngb.timepicker.PM" datatype="html">
<source><x id="INTERPOLATION"/></source>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">295</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="ngb.timepicker.AM" datatype="html">
<source><x id="INTERPOLATION"/></source>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">295</context>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.toast.close-aria" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Close</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Lukk</target>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">node_modules/src/toast/toast.ts</context>
<context context-type="linenumber">106,109</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="729754dd19eb9ce0670b0aeb5a6ae60574c2c563" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Address</source>
<target>Adresse</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-address/bisq-address.component.html</context>
<context context-type="linenumber">2</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">3,5</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">shared.address</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="a9b87c3aa4731edee661c8287ef3aab71799c0b8" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Total received</source>
<target>Totalt mottatt</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-address/bisq-address.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">22</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">31,32</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">address.total-received</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f149942f271231be52f55589398967093382d96d" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Total sent</source>
<target>Totalt sendt</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-address/bisq-address.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">26</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-blocks/bisq-blocks.component.html</context>
<context context-type="linenumber">14,15</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">35,36</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">address.total-sent</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="7e69426bd97a606d8ae6026762858e6e7c86a1fd" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Balance</source>
<target>Balanse</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-address/bisq-address.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">30</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">40,41</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">address.balance</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="27387c2af5dcaf343a548feba821515f5dc00faa" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> transaction</source>
<target> <x id="INTERPOLATION" equiv-text="{{ i }}"/> transaksjon</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-address/bisq-address.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">50</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">51</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">190,191</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/blockchain-blocks/blockchain-blocks.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">22,23</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/mempool-blocks/mempool-blocks.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">21,22</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">shared.transaction-count.singular</note>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="14779b0ce4cbc4d975a35a8fe074426228a324f3" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> transactions</source>
<target> <x id="INTERPOLATION" equiv-text="{{ i }}"/> transaksjoner</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-address/bisq-address.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">51</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">52</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">191,192</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/blockchain-blocks/blockchain-blocks.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">23,24</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context context-type="sourcefile">src/app/components/mempool-blocks/mempool-blocks.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">22,23</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">shared.transaction-count.plural</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="bisq-address.component.browser-title" datatype="html">
<source>Address: <x id="INTERPOLATION" equiv-text="this.addressString"/></source>
<target>Adresse: <x id="INTERPOLATION" equiv-text="this.addressString"/></target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-address/bisq-address.component.ts</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context context-type="linenumber">43</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="70572fa5fe9d93f071fbb0f3556d86de39f9e4af" datatype="html">
<source>Block <x id="START_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;ng-container *ngTemplateOutlet=&quot;blockTemplateContent&quot;&gt;"/><x id="CLOSE_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;/ng-container&gt;"/></source>
<target>Blokk <x id="START_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;ng-container *ngTemplateOutlet=&quot;blockTemplateContent&quot;&gt;"/> <x id="CLOSE_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;/ng-container&gt;"/></target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.html</context>
<context context-type="linenumber">4</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled new strings from transifex.
2020-12-09 01:17:22 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">16,17</context>
Pulled new strings from transifex.
2020-12-09 01:17:22 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">shared.block-title</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="960cd598cbd85edb0a254ff3e59574d2c5cb888c" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Hash</source>
<target>Hash</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">19</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled new strings from transifex.
2020-12-09 01:17:22 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">82</context>
Pulled new strings from transifex.
2020-12-09 01:17:22 +07:00
</context-group>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">51,52</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">block.hash</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="07193288a0312875e18f38c3a2486b927a15520a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Timestamp</source>
<target>Tidspunkt</target>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">23</context>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">86</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">34,36</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">55,57</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">13,15</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/latest-blocks/latest-blocks.component.html</context>
<context context-type="linenumber">10,12</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">213,215</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">261,263</context>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">49,51</context>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">block.timestamp</note>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="6d0db947a91dc4884aefa858a27fc848530e6404" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Previous hash</source>
<target>Forrige hash</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">37</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">95</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction Previous Hash</note>
<note priority="1" from="meaning">block.previous_hash</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="bisq-block.component.browser-title" datatype="html">
<source>Block <x id="BLOCK_HEIGHT" equiv-text="block.height"/>: <x id="BLOCK_HASH" equiv-text="block.hash"/></source>
<target>Blokk <x id="BLOCK_HEIGHT" equiv-text="block.height"/> : <x id="BLOCK_HASH" equiv-text="block.hash"/></target>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-block/bisq-block.component.ts</context>
<context context-type="linenumber">89</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="6c2ae4f9da67155a00f8db40ac22315eeaff33e2" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>BSQ Blocks</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>BSQ-blokker</target>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-blocks/bisq-blocks.component.html</context>
<context context-type="linenumber">2,7</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq blocks header</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="179eb5c4a21ad324f75f723218a621d120e39d30" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Height</source>
<target>Høyde</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-blocks/bisq-blocks.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">12,14</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.html</context>
<context context-type="linenumber">22,24</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">11,12</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/difficulty-adjustments-table/difficulty-adjustments-table.component.html</context>
<context context-type="linenumber">5,7</context>
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/latest-blocks/latest-blocks.component.html</context>
<context context-type="linenumber">9,10</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">212,214</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">260,262</context>
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">112,113</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq block height header</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="a1daf43d26259bffdd5eb2d405c61583540b113b" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Confirmed</source>
<target>Bekreftet</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-blocks/bisq-blocks.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">13,15</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq block confirmed time header</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="add4cd82e3e38a3110fe67b3c7df56e9602644ee" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Transactions</source>
<target>Transaksjoner</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-blocks/bisq-blocks.component.html</context>
<context context-type="linenumber">15,18</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">81</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/bisq-master-page/bisq-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">34,36</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/latest-blocks/latest-blocks.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">12,16</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">28,32</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq block transactions title</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8a7b4bd44c0ac71b2e72de0398b303257f7d2f54" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Blocks</source>
<target>Blokker</target>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-blocks/bisq-blocks.component.ts</context>
<context context-type="linenumber">38</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/bisq-master-page/bisq-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">37,39</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">4,9</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/latest-blocks/latest-blocks.component.html</context>
<context context-type="linenumber">2,7</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/latest-blocks/latest-blocks.component.ts</context>
<context context-type="linenumber">39</context>
</context-group>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">35,37</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">38,40</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">88,90</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="6b2fdbdddef74630e1076d58786ca339a8c030f0" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Bisq Trading Volume</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Bisq handelsvolum</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-dashboard/bisq-dashboard.component.html</context>
<context context-type="linenumber">3,7</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<context context-type="linenumber">48,50</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq markets title</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="d3ad0babadabfa3e3b7f51637651822f3e56a7b1" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Markets</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Markeder</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-dashboard/bisq-dashboard.component.html</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context context-type="linenumber">20,21</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
<context context-type="linenumber">66,67</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq All Markets</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ece163b62f5e9b0b68a8d6a2d93e216318f557ba" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Bitcoin Markets</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Bitcoin Markeder</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-dashboard/bisq-dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">21,24</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
<context context-type="linenumber">67,71</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq Bitcoin Markets</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="32072c7fb0469aaf82d256a59b3e0d6ecce973b9" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Currency</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Valuta</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-dashboard/bisq-dashboard.component.html</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context context-type="linenumber">27</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
<context context-type="linenumber">73</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4d6ee53858628de558a18623894a03c8673bce9e" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Price</source>
<target>Pris</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-dashboard/bisq-dashboard.component.html</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context context-type="linenumber">28,29</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
<context context-type="linenumber">74,75</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-market/bisq-market.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">79,80</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">36</context>
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">78</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-trades/bisq-trades.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">5,6</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="b666c0101ab9ef128a75fdf05a43184a57de0cff" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Volume (7d)</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Volum (7d)</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-dashboard/bisq-dashboard.component.html</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context context-type="linenumber">29</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Trading volume 7D</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="faf7b6da436cb9342858ec551aecdab8052dbde6" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Trades (7d)</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Handler (7d)</target>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-dashboard/bisq-dashboard.component.html</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context context-type="linenumber">30</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
<context context-type="linenumber">75</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Trades amount 7D</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8d54d714a00023ea23b58d8642980ef41cea0cb3" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Latest Trades</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Siste handler</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-dashboard/bisq-dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">52,56</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
<context context-type="linenumber">99,101</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-market/bisq-market.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">59,61</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Latest Trades header</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="3f42ea126dba9186d89dffe43937f2b9c17858d6" datatype="html">
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<source>Bisq Price Index</source>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Bisq prisindeks</target>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
<context context-type="linenumber">9,11</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">bisq-dashboard.price-index-title</note>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="e32fd95e667cfcee9948135918a151a614d5d349" datatype="html">
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<source>Bisq Market Price</source>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Bisq markedspris</target>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<context context-type="linenumber">21,23</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">bisq-dashboard.market-price-title</note>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="97ff5554c708164d58b14e45072acbcbf9f4d137" datatype="html">
<source>View more »</source>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<context context-type="linenumber">92,97</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">101,108</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">33</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">43</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">54</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">65</context>
</context-group>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">139,144</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">dashboard.view-more</note>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="94731fb77c18c6d537337dddc3699f67a0587985" datatype="html">
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<source>Terms of Service</source>
<target>Bruksvilkår</target>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">111,113</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">357,361</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">181,183</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/docs/docs.component.html</context>
<context context-type="linenumber">42</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Terms of Service</note>
<note priority="1" from="meaning">shared.terms-of-service</note>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="8f3ac0544491bf048120928d39e02a6baeb0b278" datatype="html">
<source>Privacy Policy</source>
<target>Personvernerklæring</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-main-dashboard/bisq-main-dashboard.component.html</context>
<context context-type="linenumber">113,120</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">183,185</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.html</context>
<context context-type="linenumber">44</context>
</context-group>
<note priority="1" from="description">Privacy Policy</note>
<note priority="1" from="meaning">shared.privacy-policy</note>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f4ebbeea643a58f45e665e960b494b2ea30b87da" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Buy Offers</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Kjøp tilbud</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-market/bisq-market.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">73,74</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq Buy Offers</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="abf29235edbf341b6f626c315ff509f38fbf728a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Sell Offers</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Selg tilbud</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-market/bisq-market.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">74,77</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq Sell Offers</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="74d80a5b284beb81e8aeb3b8efca0f78cd4b7560" datatype="html">
<source>Amount (<x id="INTERPOLATION" equiv-text="{{ i }}"/>)</source>
<target>Beløp ( <x id="INTERPOLATION" equiv-text="{{ i }}"/> )</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-market/bisq-market.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">112,113</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-trades/bisq-trades.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">46,47</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Trade amount (Symbol)</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="2a30a4cdb123a03facc5ab8c5b3e6d8b8dbbc3d4" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>BSQ statistics</source>
<target>BSQ statistikk</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">2</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.ts</context>
<context context-type="linenumber">28</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">BSQ statistics header</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1cde02174ca8cc2cc0b18172cd2ec598aa82dcc7" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Existing amount</source>
<target>Eksisterende beløp</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context context-type="linenumber">12</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">54</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">BSQ existing amount</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="3218e6768d0d5fbc69d4931819e21451c89ba8ed" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Minted amount</source>
<target>Utstedt beløp</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">16</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">58</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">BSQ minted amount</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="32377aae07f946d943f9361c8e518f714988c619" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Burnt amount</source>
<target>Brent beløp</target>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">20</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">62</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">64,66</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transfers/bisq-transfers.component.html</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context context-type="linenumber">68</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">BSQ burnt amount</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="7882f2edb1d4139800b276b6b0bbf5ae0b2234ef" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Addresses</source>
<target>Adresser</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">24</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">66</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">39,40</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">63,65</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">338,340</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">349,352</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">BSQ addresses</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="fb5b5aec9a6add4912de64b7bbc55884cc7f8e3a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Unspent TXOs</source>
<target>Ubrukte TXOer</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">28</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">70</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">BSQ unspent transaction outputs</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="0f8a41c901cd606bd3389d8a022cee193264f20b" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Spent TXOs</source>
<target>Brukte TXOer</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">32</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">BSQ spent transaction outputs</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="b8552f7d0a57c0cc7e63eb57d3371ea35a8bbfd3" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Market cap</source>
<target>Markedsverdi</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">40</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-stats/bisq-stats.component.html</context>
<context context-type="linenumber">82</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">BSQ token market cap</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="2f933b826a570836cab04f683970a2d22068458c" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Date</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Dato</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-trades/bisq-trades.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">4,6</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="dfc2fb58e2a04ed944a4bd80f0a2087775134068" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Amount</source>
<target>Beløp</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-trades/bisq-trades.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">9,12</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">20,21</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">150,151</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="23b4db80cfba2937f6b087d8776cb5cd6725a16b" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Inputs</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Innganger</target>
Update from transifex.
2021-02-15 00:15:04 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction-details/bisq-transaction-details.component.html</context>
<context context-type="linenumber">7</context>
Update from transifex.
2021-02-15 00:15:04 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.inputs</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="93883f08c5e22b14770da46e1a5b724bab7d43fb" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Outputs</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Utganger</target>
Update from transifex.
2021-02-15 00:15:04 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction-details/bisq-transaction-details.component.html</context>
<context context-type="linenumber">11</context>
Update from transifex.
2021-02-15 00:15:04 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.outputs</note>
Update from transifex.
2021-02-15 00:15:04 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="21530115a661c0faac6906740c586118628c2d54" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Issued amount</source>
<target>Beløp som er utstedt</target>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction-details/bisq-transaction-details.component.html</context>
<context context-type="linenumber">15</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">47</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset issued amount</note>
<note priority="1" from="meaning">asset.issued-amount</note>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f61c6867295f3b53d23557021f2f4e0aa1d0b8fc" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Type</source>
<target>Type</target>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction-details/bisq-transaction-details.component.html</context>
Update from transifex.
2021-02-15 00:15:04 +07:00
<context context-type="linenumber">25</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.html</context>
<context context-type="linenumber">19,21</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">151,153</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
Update translation strings from Transifex
2020-12-05 02:39:50 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">239,241</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8fe73a4787b8068b2ba61f54ab7e0f9af2ea1fc9" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Version</source>
<target>Versjon</target>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction-details/bisq-transaction-details.component.html</context>
<context context-type="linenumber">29</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">147,148</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">230,232</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.version</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="b59ea65c89a5ae15b787d8318fdad9edd6fec243" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Transaction</source>
<target>Transaksjon</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
<context context-type="linenumber">6,10</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
<context context-type="linenumber">111,117</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">13,16</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">shared.transaction</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8e623d3cfecb7c560c114390db53c1f430ffd0de" datatype="html">
<source><x id="INTERPOLATION" equiv-text="confirmation&lt;/ng-template&gt; &lt;ng-template #confirmationPlural let-i i18n=&quot;shared.confirmation-count.plural|Transaction plural confir"/> confirmation</source>
<target> <x id="INTERPOLATION" equiv-text="confirmation&lt;/ng-template&gt; &lt;ng-template #confirmationPlural let-i i18n=&quot;shared.confirmation-count.plural|Transaction plural confir"/> bekreftelse</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">20,21</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transfers/bisq-transfers.component.html</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context context-type="linenumber">75,76</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">27,28</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">266,267</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction singular confirmation count</note>
<note priority="1" from="meaning">shared.confirmation-count.singular</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="bc5b0a2631f0b7bc71aaec6aa6f01af21f9a80d4" datatype="html">
<source><x id="INTERPOLATION" equiv-text="confirmations&lt;/ng-template&gt; &lt;/button&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class=&quot;clearfix&quot;&gt;&lt;/div&gt; &lt;div class=&quot;box tran"/> confirmations</source>
<target> <x id="INTERPOLATION" equiv-text="confirmations&lt;/ng-template&gt; &lt;/button&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class=&quot;clearfix&quot;&gt;&lt;/div&gt; &lt;div class=&quot;box tran"/> bekreftelser</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">21,22</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transfers/bisq-transfers.component.html</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context context-type="linenumber">76,77</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">28,29</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">267,268</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction plural confirmation count</note>
<note priority="1" from="meaning">shared.confirmation-count.plural</note>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="0d6ed649666c5cdcf12be0216d82051bba3614b0" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Included in block</source>
<target>Inkludert i blokk</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">43,45</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">58,60</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction included in block</note>
<note priority="1" from="meaning">transaction.included-in-block</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="885666551418fd59011ceb09d5c481095940193b" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Features</source>
<target>Funksjoner</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">49,51</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">70,73</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">128,131</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction features</note>
<note priority="1" from="meaning">transaction.features</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="e5026f6e33b13e7d8185288b9691d006a139d36d" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Fee per vByte</source>
<target>Avgift per vByte</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">69,71</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction fee</note>
<note priority="1" from="meaning">transaction.fee-per-vbyte</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4f8b2bb476981727ab34ed40fde1218361f92c45" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Details</source>
<target>Detaljer</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">89,92</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">155,159</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">204,209</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">316,322</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.details</note>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="31d8d7f29ddbd3f64d374a132ddacd5e4a0835a2" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Inputs &amp; Outputs</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Innganger &amp; Utganger</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">97,105</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">179,185</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">194,197</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">287,293</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction inputs and outputs</note>
<note priority="1" from="meaning">transaction.inputs-and-outputs</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="bisq.transaction.browser-title" datatype="html">
<source>Transaction: <x id="INTERPOLATION" equiv-text="this.txId"/></source>
<target>Transaksjon: <x id="INTERPOLATION" equiv-text="this.txId"/></target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transaction/bisq-transaction.component.ts</context>
<context context-type="linenumber">50</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.ts</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">114,113</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4d6066e445db90780e4b30ca93398be0b6567eda" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>BSQ Transactions</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>BSQ Transaksjoner</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.html</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="linenumber">2,5</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="94c248797dd2b6af49068cb49c3b4bc26bec6a16" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>TXID</source>
<target>TXID</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.html</context>
<context context-type="linenumber">18,19</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">152,153</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">149,150</context>
</context-group>
</trans-unit>
<trans-unit id="bfa87f9724434e4245b30f2bdd11d97477048cd1" datatype="html">
<source>Confirmed</source>
<target>Bekreftet</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.html</context>
<context context-type="linenumber">21,24</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">65,66</context>
Update from transifex.
2021-02-15 00:15:04 +07:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">Transaction Confirmed state</note>
<note priority="1" from="meaning">transaction.confirmed</note>
Update from transifex.
2021-02-15 00:15:04 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8411955056013208681" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Asset listing fee</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Gebyr for notering</target>
Update from transifex.
2021-02-15 00:15:04 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">31</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4096113720451832029" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Blind vote</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Blind stemme</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">32</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8029165479004970466" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Compensation request</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Kompensasjonsforespørsel</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">33</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="2303359202781425764" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Genesis</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Genesis</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">34</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">5,7</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1805880753357861573" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Irregular</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Uregelmessig</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">35</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1899519213652410949" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Lockup</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Lås</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">36</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="450749685636583691" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Pay trade fee</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Betal handelsavgift</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">37</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4844032232639560116" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Proof of burn</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Bevis for forbrenning</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">38</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="2011097393756618787" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Proposal</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Forslag</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">39</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="3275831985256202873" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Reimbursement request</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Refusjonsforespørsel</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">40</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1226904538495857889" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Transfer BSQ</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Overfør BSQ</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">41</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4545041448523656285" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Unlock</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Lås opp</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">42</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8694527859973232423" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Vote reveal</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Stemme avsløring</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">43</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="bisq-transactions.filter" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Filter</source>
<target>Filter</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">57,56</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="bisq-transactions.selectall" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Select all</source>
<target>Velg alle</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">58,56</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="bisq-transactions.unselectall" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Unselect all</source>
<target>Avmarker alle</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/bisq-transactions/bisq-transactions.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">59</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="bisq-graph-trades" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Trades</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Handler</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/bisq/lightweight-charts-area/lightweight-charts-area.component.ts</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context context-type="linenumber">90</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="bisq-graph-volume" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Volume</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Volum</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/bisq/lightweight-charts-area/lightweight-charts-area.component.ts</context>
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<context context-type="linenumber">91</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4b137ec8bf73a47063740b75c0c40d5fd3c48015" datatype="html">
Updated from transifex.
2021-06-22 10:57:44 -04:00
<source>The Mempool Open Source Project</source>
Update from transifex.
2021-07-06 20:05:59 +03:00
<target>Åpen kildekode-prosjektet The Mempool</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">12,13</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.about-the-project</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="8a4411dcb4da0aa489ec367bf2a3ec289e07a86e" datatype="html">
<source>Our mempool and blockchain explorer for the Bitcoin community, focusing on the transaction fee market and multi-layer ecosystem, completely self-hosted without any trusted third-parties.</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">13,17</context>
</context-group>
</trans-unit>
<trans-unit id="8d0b91c3b649c0237734a2c27585ed0409451523" datatype="html">
<source>Become a sponsor ❤️</source>
<target>Bli en sponsor ❤️</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">33,34</context>
</context-group>
<note priority="1" from="description">about.become-a-sponsor</note>
</trans-unit>
<trans-unit id="1abb54fd13f529707c73db97625cd18c7c8cbb09" datatype="html">
<source>Navigate to <x id="START_LINK" ctype="x-a" equiv-text="&lt;a href=&quot;https://mempool.space/sponsor&quot; target=&quot;_blank&quot;&gt;"/>https://mempool.space/sponsor<x id="CLOSE_LINK" ctype="x-a" equiv-text="&lt;/a&gt;"/> to sponsor</source>
<target>Gå til <x id="START_LINK" ctype="x-a" equiv-text="&lt;a href=&quot;https://mempool.space/sponsor&quot; target=&quot;_blank&quot;&gt;"/> https://mempool.space/sponsor <x id="CLOSE_LINK" ctype="x-a" equiv-text="&lt;/a&gt;"/> for å sponse</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">34</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
<context context-type="linenumber">10</context>
</context-group>
<note priority="1" from="description">about.navigate-to-sponsor</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="a24b1c6a9c4334ba204e4cec2dd9f32ea33d043f" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Enterprise Sponsors 🚀</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Bedriftssponsorer 🚀</target>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">38,41</context>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.sponsors.enterprise.withRocket</note>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="a46e9bc519dc1c320d48635e924d444364845ca8" datatype="html">
Updating translations from transifex.
2021-03-07 20:13:39 +07:00
<source>Community Sponsors ❤️</source>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<target>Samfunnssponsorer ❤️</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">159,162</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.sponsors.withHeart</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="673e6c47e6dffb3860102581b7fe7e534929e308" datatype="html">
<source>Self-Hosted Integrations</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">173,175</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">about.self-hosted-integrations</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="11564b903fa784898b90f4166c2f42b77bbb82ac" datatype="html">
<source>Wallet Integrations</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">207,209</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">about.wallet-integrations</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="020cce975a5d7e0cc0f4578903358459d693e4bb" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Community Alliances</source>
<target>Samfunnsallianser</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">257,259</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.alliances</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="d5a535ddb26ae8cb056325715af27bb1b4008c14" datatype="html">
<source>Project Translators</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">273,275</context>
</context-group>
<note priority="1" from="description">about.translators</note>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="2dd9b8a8997a6b57413ca3cd32dd38cef9fa39c2" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Project Contributors</source>
<target>Bidragsytere til prosjektet</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">287,289</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</context-group>
<note priority="1" from="description">about.contributors</note>
</trans-unit>
<trans-unit id="3d395b07b1f87656ed773adcbb3daf8e00c08779" datatype="html">
<source>Project Members</source>
<target>Prosjektmedlemmer</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">299,301</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.project_members</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="d177262e3a43b2a7221183812daf0ada97659436" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Project Maintainers</source>
<target>Prosjektvedlikeholdere</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">312,314</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.maintainers</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="004b222ff9ef9dd4771b777950ca1d0e4cd4348a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>About</source>
<target>Om</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/about/about.component.ts</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">39</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/bisq-master-page/bisq-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">46,49</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">52,55</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">50,53</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="address-label.multisig" datatype="html">
<source>Multisig <x id="multisigM" equiv-text="m"/> of <x id="multisigN" equiv-text="n"/></source>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/address-labels/address-labels.component.ts</context>
<context context-type="linenumber">121</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="04ffd930e7a2dc086c952a3a51b42c836bf21cc1" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Unconfidential</source>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<target>Ukonfidensielt</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">23,24</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">address.unconfidential</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="714e34125b3343df73f19ec800b43be95217d5d4" datatype="html">
<source><x id="INTERPOLATION" equiv-text="of {{ txCount | number }} transaction&lt;/ng-template&gt;"/> of <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/> transaction</source>
<target> <x id="INTERPOLATION" equiv-text="of {{ txCount | number }} transaction&lt;/ng-template&gt;"/> av <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/> transaksjon</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">60,61</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">X of X Address Transaction</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="0f6ada0cfb60aefd8f77f8a22349850ce186d666" datatype="html">
<source><x id="INTERPOLATION" equiv-text="of {{ txCount | number }} transactions&lt;/ng-template&gt; &lt;/h2&gt;"/> of <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/> transactions</source>
<target> <x id="INTERPOLATION" equiv-text="of {{ txCount | number }} transactions&lt;/ng-template&gt; &lt;/h2&gt;"/> av <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/> transaksjoner</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">61,62</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">X of X Address Transactions (Plural)</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f094f67fbe759cdbeb2ea14455634bbe5cc6375d" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Error loading address data.</source>
<target>Lasting av adressedata feilet.</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">132,134</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">address.error.loading-address-data</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="49cef95661d86f4341788ce40068d58801adc6e6" datatype="html">
<source><x id="START_ITALIC_TEXT" ctype="x-i" equiv-text="There many transactions on this address, more than your backend can handle. See more on &lt;a href=&quot;/docs/faq#a"/>There many transactions on this address, more than your backend can handle. See more on <x id="START_LINK" ctype="x-a" equiv-text="&lt;a href=&quot;/docs/faq#address-lookup-issues&quot;&gt;"/>setting up a stronger backend<x id="CLOSE_LINK" ctype="x-a" equiv-text="&lt;/a&gt;"/>.<x id="CLOSE_ITALIC_TEXT" ctype="x-i" equiv-text="&lt;/i&gt;"/><x id="LINE_BREAK" ctype="lb"/><x id="LINE_BREAK" ctype="lb"/> Consider viewing this address on the official Mempool website instead: </source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">137,140</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Electrum server limit exceeded error</note>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="30751732ff4b8f6ddb2a906e0173072ac29d412a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Confidential</source>
<target>Konfidensielt</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">156,158</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/amount/amount.component.html</context>
<context context-type="linenumber">6,9</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/asset-circulation/asset-circulation.component.html</context>
<context context-type="linenumber">2,4</context>
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">163</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">274,276</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">157,158</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">shared.confidential</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="address.component.browser-title" datatype="html">
<source>Address: <x id="INTERPOLATION" equiv-text="this.addressString"/></source>
<target>Adresse: <x id="INTERPOLATION" equiv-text="this.addressString"/></target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/address/address.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">78</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f8c91b77ad53ccd0f6adb4a6ea3a0f5c3329688b" datatype="html">
<source>Asset</source>
<target>Ressurs</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">3</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset page title</note>
<note priority="1" from="meaning">asset</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="cff1428d10d59d14e45edec3c735a27b5482db59" datatype="html">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<source>Name</source>
<target>Navn</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">23</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">4,6</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">29,31</context>
</context-group>
<note priority="1" from="description">Asset name header</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8f301d45550dcb7dec91cc1fdc1f65f13c6a2892" datatype="html">
<source>Precision</source>
<target>Presisjon</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">27</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset precision</note>
<note priority="1" from="meaning">asset.precision</note>
</trans-unit>
<trans-unit id="80475fc1bf22ded644db203c43a075f623c527d4" datatype="html">
<source>Issuer</source>
<target>Utsteder</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">31</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset issuer</note>
<note priority="1" from="meaning">asset.issuer</note>
</trans-unit>
<trans-unit id="e357dfd9e8685f17a862680cd98fe4aa2e068d28" datatype="html">
<source>Issuance TX</source>
<target>Utstedelse TX</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">35</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset issuance TX</note>
<note priority="1" from="meaning">asset.issuance-tx</note>
</trans-unit>
<trans-unit id="c5b2c0d65b8fd12ebf8c0d79f562703776fc954e" datatype="html">
<source>Pegged in</source>
<target>Pegged inn</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">39</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset pegged-in amount</note>
<note priority="1" from="meaning">asset.pegged-in</note>
</trans-unit>
<trans-unit id="8f5d6ce525a24b049fee47f9b2d8447cca97ccc8" datatype="html">
<source>Pegged out</source>
<target>Pegged ut</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">43</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset pegged-out amount</note>
<note priority="1" from="meaning">asset.pegged-out</note>
</trans-unit>
<trans-unit id="e21556753a442f3d474ccfed50cd3f60bec18fe3" datatype="html">
<source>Burned amount</source>
<target>Beløp som er brent</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">51</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset burned amount</note>
<note priority="1" from="meaning">asset.burned-amount</note>
</trans-unit>
<trans-unit id="1990b8bef8f205a7d1b821aa4f979cc9f4fe179d" datatype="html">
<source>Circulating amount</source>
<target>Sirkulerende beløp</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">55</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">59</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset circulating amount</note>
<note priority="1" from="meaning">asset.circulating-amount</note>
</trans-unit>
<trans-unit id="c3360a933cb312b395d276a2b865214cf832df58" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ (transactions?.length | number) || '?' }}"/> of <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/> </source>
<target> <x id="INTERPOLATION" equiv-text="{{ (transactions?.length | number) || '?' }}"/> av <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/></target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">80</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">asset.M_of_N</note>
</trans-unit>
<trans-unit id="d2a84740e76b7220516a9f10644e4b3bdabdb833" datatype="html">
<source>Peg In/Out and Burn Transactions</source>
<target>Peg inn / ut og brenn transaksjoner</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">81</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid native asset transactions title</note>
</trans-unit>
<trans-unit id="fcbd3315aa10b59ba6ef383c6f16ace6c9d53b71" datatype="html">
<source>Issuance and Burn Transactions</source>
<target>Utstedelse og forbrennings transaksjoner</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">82</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Default asset transactions title</note>
</trans-unit>
<trans-unit id="ef5ac12104751b93b03c16f64d4c3a4341dce89c" datatype="html">
<source>Error loading asset data.</source>
<target>Lasting av ressursdata feilet.</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">152</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">asset.error.loading-asset-data</note>
</trans-unit>
<trans-unit id="asset.component.asset-browser-title" datatype="html">
<source>Asset: <x id="INTERPOLATION" equiv-text="this.assetString"/></source>
<target>Eiendel: <x id="INTERPOLATION" equiv-text="this.assetString"/></target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/asset/asset.component.ts</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">75</context>
</context-group>
</trans-unit>
<trans-unit id="e3f9fda25b281496fe296fb7e8228f59b50983ad" datatype="html">
<source>Group of <x id="INTERPOLATION" equiv-text="{{ group.assets.length | number }}"/> assets</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/asset-group/asset-group.component.html</context>
<context context-type="linenumber">8,9</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets-featured/assets-featured.component.html</context>
<context context-type="linenumber">9,10</context>
</context-group>
</trans-unit>
<trans-unit id="ee8f8008bae6ce3a49840c4e1d39b4af23d4c263" datatype="html">
<source>Assets</source>
<target>Ressurser</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
<context context-type="linenumber">3</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.ts</context>
<context context-type="linenumber">42</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.ts</context>
<context context-type="linenumber">44</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">46,48</context>
</context-group>
<note priority="1" from="description">Assets page header</note>
</trans-unit>
<trans-unit id="d06e27f7453fcf29134f9e61533ea4eb4b890f5f" datatype="html">
<source>Featured</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
<context context-type="linenumber">9</context>
</context-group>
</trans-unit>
<trans-unit id="dfc3c34e182ea73c5d784ff7c8135f087992dac1" datatype="html">
<source>All</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
<context context-type="linenumber">13</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">64,70</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">149,151</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">172,174</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">429,431</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">455,457</context>
</context-group>
</trans-unit>
<trans-unit id="aef0d676b15fdae8cb70fc3b089cce7399fde9da" datatype="html">
<source>Search asset</source>
<target>Søk ressurs</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
<context context-type="linenumber">19</context>
</context-group>
<note priority="1" from="description">Search Assets Placeholder Text</note>
</trans-unit>
<trans-unit id="99ee4faa69cd2ea8e3678c1f557c0ff1f05aae46" datatype="html">
<source>Clear</source>
<target>Fjern</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
<context context-type="linenumber">21</context>
</context-group>
<note priority="1" from="description">Search Clear Button</note>
</trans-unit>
<trans-unit id="4ad173c0e4010b1f25bf58e96a383edc1b59cd80" datatype="html">
<source>Ticker</source>
<target>Ticker</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">5,6</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">30,31</context>
</context-group>
<note priority="1" from="description">Asset ticker header</note>
</trans-unit>
<trans-unit id="465c39daa2b644679d73a451043622f1610a2084" datatype="html">
<source>Issuer domain</source>
<target>Utsteder-domene</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">6,9</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">31,34</context>
</context-group>
<note priority="1" from="description">Asset Issuer Domain header</note>
</trans-unit>
<trans-unit id="d5e7c95d7c8920ae0a384e3fffb14776b1e203f4" datatype="html">
<source>Asset ID</source>
<target>Ressurs-ID</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">7,10</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">32,36</context>
</context-group>
<note priority="1" from="description">Asset ID header</note>
</trans-unit>
<trans-unit id="52686df280be57a57e1e9ecf5786499b147e0e90" datatype="html">
<source>Error loading assets data.</source>
<target>Feil ved innlasting av ressursdata.</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">48,53</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">Asset data load error</note>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
<trans-unit id="2b34680062c4aed90c4d846eab42d6e99501b783" datatype="html">
<source>Offline</source>
<target>Offline</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/bisq-master-page/bisq-master-page.component.html</context>
<context context-type="linenumber">7,8</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">8,9</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
<context context-type="linenumber">8,9</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">master-page.offline</note>
</trans-unit>
<trans-unit id="c5d46228bea3555d65c705bad40be80f8798a113" datatype="html">
<source>Reconnecting...</source>
<target>Kobler til igjen...</target>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/bisq-master-page/bisq-master-page.component.html</context>
<context context-type="linenumber">8,13</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">9,14</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
<context context-type="linenumber">9,14</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">master-page.reconnecting</note>
</trans-unit>
<trans-unit id="9daedf013e87630c4e0a9123dc62e5bbf15a59ad" datatype="html">
<source>Layer 2 Networks</source>
<target>Lag 2-nettverk</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/bisq-master-page/bisq-master-page.component.html</context>
<context context-type="linenumber">21,22</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">22,23</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
<context context-type="linenumber">22,23</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">master-page.layer2-networks-header</note>
</trans-unit>
<trans-unit id="f65253954b66e929a8b4d5ecaf61f9129f8cec64" datatype="html">
<source>Dashboard</source>
<target>Dashbord</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/bisq-master-page/bisq-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">31,33</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">32,34</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">32,34</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">master-page.dashboard</note>
</trans-unit>
<trans-unit id="299f97b8ee9c62d45f2cc01961aa1e5101d6d05a" datatype="html">
<source>Stats</source>
<target>Statistikk</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/bisq-master-page/bisq-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">40,42</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">master-page.stats</note>
</trans-unit>
<trans-unit id="a7ecfd7757d04b019beaa2d7208c728387bfc7e8" datatype="html">
<source>Docs</source>
<target>Dokumenter</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/bisq-master-page/bisq-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">43,45</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">49,51</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">master-page.docs</note>
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="ed8e33059967f554ff06b4f5b6049c465b92d9b3" datatype="html">
<source>Block Fee Rates</source>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.html</context>
<context context-type="linenumber">5,7</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.ts</context>
<context context-type="linenumber">65</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">14</context>
</context-group>
<note priority="1" from="description">mining.block-fee-rates</note>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="6c453b11fd7bd159ae30bc381f367bc736d86909" datatype="html">
<source>Block Fees</source>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/block-fees-graph/block-fees-graph.component.html</context>
<context context-type="linenumber">5,7</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-fees-graph/block-fees-graph.component.ts</context>
<context context-type="linenumber">58</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">16</context>
</context-group>
<note priority="1" from="description">mining.block-fees</note>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="c20172223f84462032664d717d739297e5a9e2fe" datatype="html">
<source>Fees</source>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/block-fees-graph/block-fees-graph.component.ts</context>
<context context-type="linenumber">160,158</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">16,17</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">217,219</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">265,267</context>
</context-group>
</trans-unit>
<trans-unit id="8ba8fe810458280a83df7fdf4c614dfc1a826445" datatype="html">
<source>Block Rewards</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-rewards-graph/block-rewards-graph.component.html</context>
<context context-type="linenumber">6,8</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-rewards-graph/block-rewards-graph.component.ts</context>
<context context-type="linenumber">56</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">18</context>
</context-group>
<note priority="1" from="description">mining.block-rewards</note>
</trans-unit>
<trans-unit id="12f86e6747a5ad39e62d3480ddc472b1aeab5b76" datatype="html">
<source>Reward</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-rewards-graph/block-rewards-graph.component.ts</context>
<context context-type="linenumber">160,158</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">15,17</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">216,218</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">264,266</context>
</context-group>
</trans-unit>
<trans-unit id="56fa1cd221491b6478998679cba2dc8d55ba330d" datatype="html">
<source>Block Sizes and Weights</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.html</context>
<context context-type="linenumber">4,6</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">65</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">20</context>
</context-group>
<note priority="1" from="description">mining.block-sizes-weights</note>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
<trans-unit id="7faaaa08f56427999f3be41df1093ce4089bbd75" datatype="html">
<source>Size</source>
<target>Størrelse</target>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">181,180</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">227,225</context>
</context-group>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">64,66</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">18,20</context>
</context-group>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/latest-blocks/latest-blocks.component.html</context>
<context context-type="linenumber">13,16</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">32,35</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/mempool-graph/mempool-graph.component.ts</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">260</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">219,222</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">267,271</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">212,214</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">116,119</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
<trans-unit id="919f2fd60a898850c24b1584362bbf18a4628bcb" datatype="html">
<source>Weight</source>
<target>Vekt</target>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">189,188</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">258,255</context>
</context-group>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">68,70</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">220,222</context>
</context-group>
</trans-unit>
<trans-unit id="bdf0e930eb22431140a2eaeacd809cc5f8ebd38c" datatype="html">
<source>Next Block</source>
<target>Neste blokk</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">7,8</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">19,20</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.ts</context>
<context context-type="linenumber">71</context>
</context-group>
<note priority="1" from="description">Next Block</note>
</trans-unit>
<trans-unit id="a0e07a711d171f4d40dd388d70ed32f9b8101e0a" datatype="html">
<source>Previous Block</source>
<target>Forrige blokk</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">26,27</context>
</context-group>
<note priority="1" from="description">Previous Block</note>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
<trans-unit id="0b47a777f024ab4e3cdf0062acb4d86e9ae1f635" datatype="html">
<source>Median fee</source>
<target>Medianavgift</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">78,79</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">16,17</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">block.median-fee</note>
</trans-unit>
<trans-unit id="d2eb45d1cd8cd146b7cb0223ab97a4b03b614060" datatype="html">
<source>sat/vB</source>
<target>sat/vB</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">79</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/blockchain-blocks/blockchain-blocks.component.html</context>
<context context-type="linenumber">11,14</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/blockchain-blocks/blockchain-blocks.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">14,17</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">6</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">12</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">18</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">17</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">21,24</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/mempool-blocks/mempool-blocks.component.html</context>
<context context-type="linenumber">10,13</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/mempool-blocks/mempool-blocks.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">13,16</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">169,170</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">182,183</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">391,394</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">402,404</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">259</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">159,163</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">235,239</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">sat/vB</note>
<note priority="1" from="meaning">shared.sat-vbyte</note>
</trans-unit>
<trans-unit id="855f852e5642a1279605465df0cbbe78c2622648" datatype="html">
<source>Based on average native segwit transaction of 140 vBytes</source>
<target>Basert på gjennomsnittlig native segwit-transaksjon på 140 vBytes</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">79,81</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">5,6</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">11,12</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">17,18</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">17,20</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction fee tooltip</note>
</trans-unit>
<trans-unit id="ae9770436d1823a1ddfa0837c5a98f412a0d42c4" datatype="html">
<source>Total fees</source>
<target>Totale avgifter</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">83,85</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">109,111</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">24,25</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Total fees in a block</note>
<note priority="1" from="meaning">block.total-fees</note>
</trans-unit>
<trans-unit id="b784270035273a5744e3c23c0fff31eebca32050" datatype="html">
<source>Subsidy + fees:</source>
<target>Subsidie + avgifter:</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">98,100</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">113,117</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Total subsidy and fees in a block</note>
<note priority="1" from="meaning">block.subsidy-and-fees</note>
</trans-unit>
<trans-unit id="21f88da2fbe81e4dc893ce1df92bd0fe25bcecee" datatype="html">
<source>Miner</source>
<target>Utvinner</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">118,120</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">block.miner</note>
</trans-unit>
<trans-unit id="fd04710d1a54d46cd1b81a13fc98e3d561b92141" datatype="html">
<source>Bits</source>
<target>Bits</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">151,153</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">block.bits</note>
</trans-unit>
<trans-unit id="d71be278785ad5940aacaf2b29a67bdbf6fc6be8" datatype="html">
<source>Merkle root</source>
<target>Merklerot</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">155,157</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">block.merkle-root</note>
</trans-unit>
<trans-unit id="25148835d92465353fc5fe8897c27d5369978e5a" datatype="html">
<source>Difficulty</source>
<target>Vanskelighetsgrad</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">165,168</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/difficulty-adjustments-table/difficulty-adjustments-table.component.html</context>
<context context-type="linenumber">7,10</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">14,16</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">73,75</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">237,236</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">305,302</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">block.difficulty</note>
</trans-unit>
<trans-unit id="a6bb63d98a8a67689070a79ccf13960c25b572ef" datatype="html">
<source>Nonce</source>
<target>Nonce</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">169,171</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">block.nonce</note>
</trans-unit>
<trans-unit id="cbfb79ff517493268a49acffa81ecc02336d8372" datatype="html">
<source>Block Header Hex</source>
<target>Blokkheader Hex</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">173,174</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">block.header</note>
</trans-unit>
<trans-unit id="5f32c623f92bf3ca31202cc6281d4abd5febaf6a" datatype="html">
<source>Details</source>
<target>Detaljer</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">184,188</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">197,201</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction Details</note>
<note priority="1" from="meaning">transaction.details</note>
</trans-unit>
<trans-unit id="56ad2f3895f350abdd3cee2d95498deb8819afac" datatype="html">
<source>Error loading block data.</source>
<target>Lasting av blokkdata feilet.</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">278,288</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">block.error.loading-block-data</note>
</trans-unit>
<trans-unit id="block.component.browser-title" datatype="html">
<source>Block <x id="BLOCK_HEIGHT" equiv-text="block.height"/>: <x id="BLOCK_ID" equiv-text="block.id"/></source>
<target>Blokk <x id="BLOCK_HEIGHT" equiv-text="block.height"/> : <x id="BLOCK_ID" equiv-text="block.id"/></target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/block/block.component.ts</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">146</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="e70fcca5a99575cffef3ff8cbd5e69f06ffd0f1c" datatype="html">
<source>Pool</source>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">12,13</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">86,87</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">114,115</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.pool-name</note>
</trans-unit>
<trans-unit id="65d447765db0bf3390e9b3ecce142bf34bb602a3" datatype="html">
<source>Mined</source>
<target>Utvunnet</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">14,15</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/latest-blocks/latest-blocks.component.html</context>
<context context-type="linenumber">11,12</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">214,215</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">262,263</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">113,114</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">latest-blocks.mined</note>
</trans-unit>
<trans-unit id="e6213c3f05146287cf121868d9f3d3c3ff5f9714" datatype="html">
<source>TXs</source>
<target>TXs</target>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">18,19</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">219,221</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">267,269</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">116,117</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">241,245</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">dashboard.txs</note>
</trans-unit>
<trans-unit id="clipboard.copied-message" datatype="html">
<source>Copied!</source>
<target>Kopiert!</target>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/clipboard/clipboard.component.ts</context>
<context context-type="linenumber">15</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
</trans-unit>
<trans-unit id="736a52d86df31df97dbb673d5dd4cc30ee322805" datatype="html">
<source>Adjusted</source>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty-adjustments-table/difficulty-adjustments-table.component.html</context>
<context context-type="linenumber">6,8</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.adjusted</note>
</trans-unit>
<trans-unit id="024cdb2814b0cb3f4ced148f1a0b9854447cb214" datatype="html">
<source>Change</source>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty-adjustments-table/difficulty-adjustments-table.component.html</context>
<context context-type="linenumber">8,11</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.change</note>
</trans-unit>
<trans-unit id="63da83692b85cf17e0606153029a83fd4038d6dd" datatype="html">
<source>Difficulty Adjustment</source>
<target>Vanskelighetsgradjustering</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">1,5</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">24</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">dashboard.difficulty-adjustment</note>
</trans-unit>
<trans-unit id="0912816d94f2f05a7eee8f7622670e0c6bbbce16" datatype="html">
<source>Remaining</source>
<target>Gjenstående</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">7,9</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">66,69</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">difficulty-box.remaining</note>
</trans-unit>
<trans-unit id="1bb6965f8e1bbe40c076528ffd841da86f57f119" datatype="html">
<source><x id="INTERPOLATION" equiv-text="&lt;span class=&quot;shared-block&quot;&gt;blocks&lt;/span&gt;&lt;/ng-template&gt; &lt;ng-template"/> <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;shared-block&quot;&gt;"/>blocks<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/></source>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">10,11</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">53,54</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">25,26</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-blocks/mempool-blocks.component.html</context>
<context context-type="linenumber">35,36</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">shared.blocks</note>
</trans-unit>
<trans-unit id="b7ef3894d9b6f157c400ddc937c70c9881ecd896" datatype="html">
<source><x id="INTERPOLATION" equiv-text="&lt;span class=&quot;shared-block&quot;&gt;block&lt;/span&gt;&lt;/ng-template&gt; &lt;/div&gt;"/> <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;shared-block&quot;&gt;"/>block<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/></source>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">11,12</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">54,55</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">26,27</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">shared.block</note>
</trans-unit>
<trans-unit id="5e65ce907fc0e1a1a09d4130eb8c59d00a9457ef" datatype="html">
<source>Estimate</source>
<target>Anslag</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">16,17</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">73,76</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">difficulty-box.estimate</note>
</trans-unit>
<trans-unit id="680d5c75b7fd8d37961083608b9fcdc4167b4c43" datatype="html">
<source>Previous</source>
<target>Forrige</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">31,33</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">difficulty-box.previous</note>
</trans-unit>
<trans-unit id="5db469cd0357e5f578b85a996f7e99c9e4148ff5" datatype="html">
<source>Current Period</source>
<target>Nåværende periode</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">43,44</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">80,83</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">difficulty-box.current-period</note>
</trans-unit>
<trans-unit id="df71fa93f0503396ea2bb3ba5161323330314d6c" datatype="html">
<source>Next Halving</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">50,52</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">difficulty-box.next-halving</note>
</trans-unit>
<trans-unit id="f2385584215e9b925b6347de866110d5e07d3a35" datatype="html">
<source>Low priority</source>
<target>Lav prioritet</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">4,5</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">27,30</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">fees-box.low-priority</note>
</trans-unit>
<trans-unit id="0ba9d74c1d31a9d98829892f40334a22624564b8" datatype="html">
<source>Medium priority</source>
<target>Medium prioritet</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">10,11</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">34,37</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">fees-box.medium-priority</note>
</trans-unit>
<trans-unit id="f80dd1511a91af4e592a538f95fa29d24907176f" datatype="html">
<source>High priority</source>
<target>Høy prioritet</target>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">16,17</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">41,44</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">fees-box.high-priority</note>
</trans-unit>
<trans-unit id="926c571b25cca7e2a294619f145960c0cd3848b6" datatype="html">
<source>Incoming transactions</source>
<target>Innkommende transaksjoner</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">5,6</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">268,269</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">dashboard.incoming-transactions</note>
</trans-unit>
<trans-unit id="a5950b2ce4c3ea32de91034de8269781eb333d73" datatype="html">
<source>Backend is synchronizing</source>
<target>Backend synkroniserer</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">8,10</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">271,274</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">dashboard.backend-is-synchronizing</note>
</trans-unit>
<trans-unit id="50904e472d4671388a20fbbb1ee9dfc0a4586fa1" datatype="html">
<source>vB/s</source>
<target>vB/s</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">13,17</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">276,281</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">vB/s</note>
<note priority="1" from="meaning">shared.vbytes-per-second</note>
</trans-unit>
<trans-unit id="60cd6fa18f925b42065d8cfb1a791efdc228b4c3" datatype="html">
<source>Unconfirmed</source>
<target>Ubekreftet</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">19,21</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">239,240</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">Unconfirmed count</note>
<note priority="1" from="meaning">dashboard.unconfirmed</note>
</trans-unit>
<trans-unit id="6f7832e2e8db3c4b16c41681ba334a2ab9726cc3" datatype="html">
<source>Mempool size</source>
<target>Mempool størrelse</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">23,24</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">Mempool size</note>
<note priority="1" from="meaning">dashboard.mempool-size</note>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="c95f8a34509967d6cbcf118a9637b23a83633449" datatype="html">
<source>Mining</source>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">5</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining</note>
</trans-unit>
<trans-unit id="4592bd8fffebd3841fc8d59472caf4b4655e6184" datatype="html">
<source>Pools Ranking</source>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">8</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">29,31</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.pools</note>
</trans-unit>
<trans-unit id="43f992a71c7b7def78d430e5af489b914cc61c11" datatype="html">
<source>Pools Dominance</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">10</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/hashrates-chart-pools/hashrate-chart-pools.component.html</context>
<context context-type="linenumber">6,8</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.pools-dominance</note>
</trans-unit>
<trans-unit id="3510fc6daa1d975f331e3a717bdf1a34efa06dff" datatype="html">
<source>Hashrate &amp; Difficulty</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">12</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">23,25</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">67</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.hashrate-difficulty</note>
</trans-unit>
<trans-unit id="79a9dc5b1caca3cbeb1733a19515edacc5fc7920" datatype="html">
<source>Hashrate</source>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">8,10</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">67,69</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">226,225</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">293,291</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">87,89</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.hashrate</note>
</trans-unit>
<trans-unit id="mining.pools-historical-dominance" datatype="html">
<source>Pools Historical Dominance</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/hashrates-chart-pools/hashrate-chart-pools.component.ts</context>
<context context-type="linenumber">63</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
</trans-unit>
<trans-unit id="23555386d8af1ff73f297e89dd4af3f4689fb9dd" datatype="html">
<source>Indexing blocks</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/indexing-progress/indexing-progress.component.html</context>
<context context-type="linenumber">1</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
</trans-unit>
<trans-unit id="5ee5eb7db86675abd5f0b0db835bf362ee9b23ff" datatype="html">
<source>Indexing network hashrate</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/indexing-progress/indexing-progress.component.html</context>
<context context-type="linenumber">2</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
</trans-unit>
<trans-unit id="439adfcf08f5035e2fd9e4c15e40eef92f6cc780" datatype="html">
<source>Indexing pools hashrate</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/indexing-progress/indexing-progress.component.html</context>
<context context-type="linenumber">3</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
</trans-unit>
<trans-unit id="5d4f792f048fcaa6df5948575d7cb325c9393383" datatype="html">
<source>Graphs</source>
<target>Grafer</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">38,41</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
<context context-type="linenumber">41,43</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/statistics/statistics.component.ts</context>
<context context-type="linenumber">62</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">master-page.graphs</note>
</trans-unit>
<trans-unit id="a681a4e2011bb28157689dbaa387de0dd0aa0c11" datatype="html">
<source>Mining Dashboard</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
<context context-type="linenumber">35,37</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.ts</context>
<context context-type="linenumber">16</context>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.mining-dashboard</note>
</trans-unit>
<trans-unit id="46ce8155c9ab953edeec97e8950b5a21e67d7c4e" datatype="html">
<source>TV view</source>
<target>TV-modus</target>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
<context context-type="linenumber">44,46</context>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/television/television.component.ts</context>
<context context-type="linenumber">37</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">master-page.tvview</note>
</trans-unit>
<trans-unit id="fcfd4675b4c90f08d18d3abede9a9a4dff4cfdc7" datatype="html">
<source>Documentation</source>
<target>Dokumentasjon</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
<context context-type="linenumber">47,49</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/docs/docs.component.html</context>
<context context-type="linenumber">4</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">documentation.title</note>
</trans-unit>
<trans-unit id="b2cb12c1680a46464cae5aa0d0d1d6914733a75d" datatype="html">
<source>Fee span</source>
<target>Avgiftsintervall</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">20,21</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mempool-block.fee-span</note>
</trans-unit>
<trans-unit id="mempool-block.stack.of.blocks" datatype="html">
<source>Stack of <x id="INTERPOLATION" equiv-text="blocksInBlock"/> mempool blocks</source>
<target>Stabel med <x id="INTERPOLATION" equiv-text="blocksInBlock"/> mempoolblokker</target>
Updating i18n from transifex.
2021-06-11 23:27:29 -05:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.ts</context>
<context context-type="linenumber">73</context>
Updating i18n from transifex.
2021-06-11 23:27:29 -05:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
</trans-unit>
<trans-unit id="mempool-block.block.no" datatype="html">
<source>Mempool block <x id="INTERPOLATION" equiv-text="this.mempoolBlockIndex + 1"/></source>
<target>Mempool blokk <x id="INTERPOLATION" equiv-text="this.mempoolBlockIndex + 1"/></target>
Updating i18n from transifex.
2021-06-11 23:27:29 -05:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.ts</context>
<context context-type="linenumber">75</context>
Update translations from Transifex
2020-12-05 00:36:00 +09:00
</context-group>
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="2348971518300945764" datatype="html">
<source>Range</source>
<target>Område</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-graph/mempool-graph.component.ts</context>
<context context-type="linenumber">259</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="1033261550402895380" datatype="html">
<source>Sum</source>
<target>Sum</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-graph/mempool-graph.component.ts</context>
<context context-type="linenumber">261</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="26e78cd052d05a0c1a7db43fac8df52ec6950672" datatype="html">
<source>Reward stats</source>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">10</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.reward-stats</note>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="8527213d7c7dbffe48a45c4d796ae221d419c71a" datatype="html">
<source>(144 blocks)</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">11</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.144-blocks</note>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="e1139ea570985b3f114e18876f09fd7223429983" datatype="html">
<source>Latest blocks</source>
<target>Nyeste blokker</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">52</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">109,112</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">dashboard.latest-blocks</note>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="21d0c2d4d5429197892c827178819da2770f2f25" datatype="html">
<source>Adjustments</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">63</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">dashboard.adjustments</note>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="8ef3568472375e791e861ca1ef76d4cb66eef8ef" datatype="html">
<source>Pools Luck (1w)</source>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">8,12</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">124,126</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.miners-luck</note>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="9ef8b357c32266f8423e24bf654006d3aa8fcd0b" datatype="html">
<source>Blocks (1w)</source>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">14,18</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">130,132</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">master-page.blocks</note>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="e1ea393882afe8ac40ff7637a33a5a46bdb3e0ce" datatype="html">
<source>Pools Count (1w)</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">20,24</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">136,138</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.miners-count</note>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="3c3a423d91e36ac6624e909fcd2669a25685f847" datatype="html">
<source>Rank</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">84,86</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.rank</note>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="3b85a3f96af9710b9a7684c5065bfbc2d3fb718a" datatype="html">
<source>Empty blocks</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">89,92</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.empty-blocks</note>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="d720761d772947b9a6a0ae3f1c68b2e7119259cf" datatype="html">
<source>All miners</source>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">107,108</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.all-miners</note>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="mining.mining-pools" datatype="html">
<source>Mining Pools</source>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
<context context-type="linenumber">55</context>
Update translated strings from Transifex
2021-01-21 12:39:33 +09:00
</context-group>
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="6095122426142344316" datatype="html">
<source><x id="PH" equiv-text="i"/> blocks</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
<context context-type="linenumber">160,158</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
<context context-type="linenumber">163,162</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</context-group>
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="cafc87479686947e2590b9f588a88040aeaf660b" datatype="html">
<source>Tags</source>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">22,23</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">30,31</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">321,323</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">329,331</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.tags</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="4eb84de23219c85432e38fb4fbdeb6c0f103ff8b" datatype="html">
<source>Show all</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">53,55</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">68,70</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">141,144</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">249,251</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">show-all</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="1eede69e18c5ac9c0b0295b72cabb7e64e029e74" datatype="html">
<source>Hide</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">55,58</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">hide</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="cc657077942054572b255be033d634cf601c50b6" datatype="html">
<source>Hashrate (24h)</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">91,93</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">114,116</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">368,370</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">395,397</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.hashrate-24h</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="91c20d9f5b4e74c46be050ed5bf0db732a86bcf7" datatype="html">
<source>Estimated</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">96,97</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">118,119</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">373,374</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">399,400</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.estimated</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="b34d145304d2f8d17e98586e27652a29f21691fe" datatype="html">
<source>Reported</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">97,98</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">119,120</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">374,375</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">400,401</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.reported</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="d7739a540416169fc6674db5b39deacbb00730f3" datatype="html">
<source>Luck</source>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">98,101</context>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">120,123</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">375,378</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">401,404</context>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.luck</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="88cb6e7b056be423b78e369ae1592c9e751095b8" datatype="html">
<source>Mined blocks</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">141,143</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">165,167</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">421,423</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">448,450</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.mined-blocks</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="149da150f9b3a141a73a58a25142a850107a8212" datatype="html">
<source>24h</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">147</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">170</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">24h</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="f7b50e4989540954a9035833470efba042a2819c" datatype="html">
<source>1w</source>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">148</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">171</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">1w</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="d7bb114523b22ee8330164224b11d75e62966539" datatype="html">
<source>Coinbase tag</source>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">215,217</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">263,265</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">latest-blocks.coinbasetag</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f13cbfe8cfc955918e9f64466d2cafddb4760d9a" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Broadcast Transaction</source>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<target>Send transaksjon</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/push-transaction/push-transaction.component.html</context>
<context context-type="linenumber">2</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/push-transaction/push-transaction.component.html</context>
<context context-type="linenumber">8</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">185,192</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Broadcast Transaction</note>
<note priority="1" from="meaning">shared.broadcast-transaction</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="7e93f7285e22e5a3c58cdde2205d4d2b5bfc079c" datatype="html">
<source>Transaction hex</source>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/push-transaction/push-transaction.component.html</context>
<context context-type="linenumber">6</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">238,239</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.hex</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="e48f3277d241b5e74b6e01a989a4ecb4495d3d25" datatype="html">
<source>Miners Reward</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">4,6</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">46,49</context>
</context-group>
<note priority="1" from="description">mining.rewards</note>
</trans-unit>
<trans-unit id="79b0842a2010172290ad09062bf51f09d8842f65" datatype="html">
<source>Amount being paid to miners in the past 144 blocks</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">6,8</context>
</context-group>
<note priority="1" from="description">mining.rewards-desc</note>
</trans-unit>
<trans-unit id="c4ae62409269c8255a390587baad3ff496889cba" datatype="html">
<source>Reward Per Tx</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">16,18</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">29,31</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">53,56</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">60,63</context>
</context-group>
<note priority="1" from="description">mining.rewards-per-tx</note>
</trans-unit>
<trans-unit id="b41ac8dd7567baf0e88ad834b5dd95df03a19c09" datatype="html">
<source>Average miners' reward per transaction in the past 144 blocks</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">18,20</context>
</context-group>
<note priority="1" from="description">mining.rewards-per-tx-desc</note>
</trans-unit>
<trans-unit id="31443c29cb161e8aa661eb5035f675746ef95b45" datatype="html">
<source>sats/tx</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">21,24</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">33,36</context>
</context-group>
<note priority="1" from="description">sat/vB</note>
<note priority="1" from="meaning">shared.sat-vbyte</note>
</trans-unit>
<trans-unit id="8be96dc461529381c812f64962c62f4228d01470" datatype="html">
<source>Fee paid on average for each transaction in the past 144 blocks</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">31,32</context>
</context-group>
<note priority="1" from="description">mining.average-fee</note>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="78fe1342aab9e91cb7cbd1becbaacf3b719546b3" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>TXID, block height, hash or address</source>
<target>TXID, blokkhøyde, hash eller adresse</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/search-form/search-form.component.html</context>
<context context-type="linenumber">4</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">search-form.searchbar-placeholder</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="7e892ba15f2c6c17e83510e273b3e10fc32ea016" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Search</source>
<target>Søk</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/search-form/search-form.component.html</context>
<context context-type="linenumber">7</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">search-form.search-title</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="dfd99c62b5b308fc5b1ad7adbbf9d526d2b31516" datatype="html">
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<source>Sponsor</source>
Update from transifex.
2021-07-06 20:05:59 +03:00
<target>Sponsor</target>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">7</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.ts</context>
<context context-type="linenumber">34</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">sponsor.title</note>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8a24d1f821c3fde832ff742b6aaba455accadc74" datatype="html">
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<source>Request invoice</source>
<target>Be om faktura</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">53</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.sponsor.request-invoice</note>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="64a98449e66031949cbf82767dd17c30d4e6da7f" datatype="html">
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<source>Waiting for transaction... </source>
<target>Venter på transaksjon...</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">142</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.sponsor.waiting-for-transaction</note>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="023f8e4927b3e3baa217a2577c78c5194b885a21" datatype="html">
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<source>Donation confirmed!</source>
<target>Donasjon bekreftet!</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">148</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.sponsor.donation-confirmed</note>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="768fa94396eb6bb2834ec52fc1b5fad92273027d" datatype="html">
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<source>Thank you!</source>
<target>Tusen takk!</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">149</context>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.sponsor.thank-you</note>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="75c20c8a9cd9723d45bee0230dd582d7c2e4ecbc" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Mempool by vBytes (sat/vByte)</source>
<target>Mempool i vBytes (sat/vByte)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">7</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">statistics.memory-by-vBytes</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="5ca707824ab93066c7d9b44e1b8bf216725c2c22" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Filter</source>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<target>Filter</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">49</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">statistics.component-filter.title</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="add9d52e5bf541c941df44e251a5c1cafcc92e9d" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Invert</source>
<target>Inverter</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">68</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">statistics.component-invert.title</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="dc15ec15e6206b40133f2c1b06095ce75aaee1ef" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Transaction vBytes per second (vB/s)</source>
<target>Transaksjoner per sekund (vB/s)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">88</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">statistics.transaction-vbytes-per-second</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.just-now" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Just now</source>
Updating from transifex.
2021-07-27 19:51:38 +03:00
<target>Akkurat nå</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context context-type="linenumber">57</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
<context context-type="linenumber">57</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="time-since" datatype="html">
<source><x id="DATE" equiv-text="dateStrings.i18nYear"/> ago</source>
<target> <x id="DATE" equiv-text="dateStrings.i18nYear"/> siden</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
<context context-type="linenumber">67</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
<context context-type="linenumber">68</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
<context context-type="linenumber">69</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context context-type="linenumber">70</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context context-type="linenumber">71</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">72</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">73</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">77</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">78</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">79</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">80</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">81</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">82</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">83</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="time-span" datatype="html">
<source>After <x id="DATE" equiv-text="dateStrings.i18nYear"/></source>
<target>Etter <x id="DATE" equiv-text="dateStrings.i18nYear"/></target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
<context context-type="linenumber">67</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
<context context-type="linenumber">68</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
<context context-type="linenumber">69</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
<context context-type="linenumber">70</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
<context context-type="linenumber">71</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">72</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">73</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">77</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">78</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">79</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">80</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">81</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">82</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-span/time-span.component.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">83</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="time-until" datatype="html">
<source>In ~<x id="DATE" equiv-text="dateStrings.i18nMinute"/></source>
<target>Om ~ <x id="DATE" equiv-text="dateStrings.i18nMinute"/></target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
<context context-type="linenumber">66</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">80</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">81</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">82</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">83</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">84</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">85</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
<context context-type="linenumber">86</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">90</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">91</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">92</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">93</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">94</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context context-type="linenumber">95</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-until/time-until.component.ts</context>
<context context-type="linenumber">96</context>
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="0094b97dd052620710f173e7aedf6807a1eba1f5" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>This transaction has been replaced by:</source>
<target>Denne transaksjonen har blitt byttet ut med:</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Updating from transifex.
2021-07-11 22:06:14 +03:00
<context context-type="linenumber">5,6</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">RBF replacement</note>
<note priority="1" from="meaning">transaction.rbf.replacement</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ef772ce5cf98a47b29175e3d46b8a9816c7990a2" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Unconfirmed</source>
<target>Ubekreftet</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">32,39</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">270,273</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction unconfirmed state</note>
<note priority="1" from="meaning">transaction.unconfirmed</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1bc4a5de56ea48a832e32294c124009867b478d0" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>First seen</source>
<target>Først sett</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">101,102</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction first seen</note>
<note priority="1" from="meaning">transaction.first-seen</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4e738ef3d2b4878f17f43002204f7b31aabb8e87" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>ETA</source>
<target>ETA</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">108,109</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction ETA</note>
<note priority="1" from="meaning">transaction.eta</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f9bad781ea9c5192160516ca55ddc5edc307ef07" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>In several hours (or more)</source>
<target>Om flere timer(eller mer)</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">114,117</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction ETA in several hours or more</note>
<note priority="1" from="meaning">transaction.eta.in-several-hours</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="54c58b39481f1749fce23fa8a77f616eee84d761" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Virtual size</source>
<target>Virtuell størrelse</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">153,155</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">216,219</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction Virtual Size</note>
<note priority="1" from="meaning">transaction.vsize</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="3e322ffba6477484e0dd2e65650fdd70322ea6d0" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Fee rate</source>
<target>Avgift</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">154,158</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">389,391</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction fee rate</note>
<note priority="1" from="meaning">transaction.fee-rate</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="dd230222e3ae689913445ce93b6ae3f7cce7458b" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Descendant</source>
<target>Etterkommer</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">161,163</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Descendant</note>
<note priority="1" from="meaning">transaction.descendant</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8c16167a5d7c96d14ff280b09de312d18d5e2511" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Ancestor</source>
<target>Forfader</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">175,177</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction Ancestor</note>
<note priority="1" from="meaning">transaction.ancestor</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="516a786e59a57efaf80e11370b4bade400f19445" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Locktime</source>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<target>Locktime</target>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">234,236</context>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.locktime</note>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="c9d9612bcd520103486b5fc84d84c9476a1b7f78" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Transaction not found.</source>
<target>Transaksjon ikke funnet</target>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">365,366</context>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.error.transaction-not-found</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="66b65556acb90d8764fe166a260af0309671698c" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Waiting for it to appear in the mempool...</source>
<target>Venter på at den kommer inn i mempool...</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">366,371</context>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.error.waiting-for-it-to-appear</note>
Updating from transifex.
2021-02-03 15:30:38 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="cb1b52c13b95fa29ea4044f2bbe0ac623b890c80" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Fee</source>
<target>Avgift</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">386</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction fee</note>
<note priority="1" from="meaning">transaction.fee</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="83b8b9dd1ed416447cf8438460a37b0ddeb2677c" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>sat</source>
<target>sat</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">386,387</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">259,260</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">sat</note>
<note priority="1" from="meaning">shared.sat</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="eb1737af67381ce6f0b347038bb4c65b3deb84be" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Effective fee rate</source>
<target>Effektiv avgift</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">399,402</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Effective transaction fee rate</note>
<note priority="1" from="meaning">transaction.effective-fee-rate</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="7e06b8dd9f29261827018351cd71efe1c87839de" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Coinbase</source>
<target>Coinbase</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">54</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.coinbase</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="7d745f2569c4ddc2992529f00ed991e36dada39a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>(Newly Generated Coins)</source>
<target>(Nygenererte Mynter)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">54</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.newly-generated-coins</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="5de25175982d51c72d25bd79933e7b412d51e343" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Peg-in</source>
<target>Peg-inn</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">56,58</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.peg-in</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="23f4a0693bc0ad8dbdccfc0b04238edfaf846bc5" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>ScriptSig (ASM)</source>
<target>ScriptSig(ASM)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">97,99</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">ScriptSig (ASM)</note>
<note priority="1" from="meaning">transactions-list.scriptsig.asm</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="3a5a04628e57fd93cfce206ccbc1432fed0925d3" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>ScriptSig (HEX)</source>
<target>ScriptSig(HEX)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">101,104</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">ScriptSig (HEX)</note>
<note priority="1" from="meaning">transactions-list.scriptsig.hex</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="c64b73564fd858ee5a4f73040893c9d625ca56ad" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Witness</source>
<target>Witness</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">106,108</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.witness</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="a8bc418b73c6bfcefc1b07c84d7f1126ab2a3237" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>P2SH redeem script</source>
<target>P2SH redeem script</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">110,111</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.p2sh-redeem-script</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="d4b97cae5fffc21333bed5d04a95e103650ebfb2" datatype="html">
<source>P2TR tapscript</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">114,116</context>
</context-group>
<note priority="1" from="description">transactions-list.p2tr-tapscript</note>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="e1d63108bdf06fa14ec13f038e23eebd4d391b16" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>P2WSH witness script</source>
<target>P2WSH witness script</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">116,118</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.p2wsh-witness-script</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="cb49c3831dcaed1b6ccaf5efe58730cf29a5d15d" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>nSequence</source>
<target>nSequence</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">121,123</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.nsequence</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="26cdad3f9e94369ff12c5c628d8eb5c724e3acb3" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Previous output script</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Forrige utgangs-script</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">126,127</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.previous-output-script</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="e7699861471f18a60e583512c45d84b388cfa120" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Previous output type</source>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<target>Tidligere utdatatype</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">130,131</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.previous-output-type</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="9fb28e77d5963f2275397f2f9cee54f32942aeeb" datatype="html">
<source>Peg-out to <x id="START_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;ng-container *ngTemplateOutlet=&quot;pegOutLink&quot;&gt;"/><x id="CLOSE_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;/ng-contain"/></source>
<target>Peg-out til <x id="START_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;ng-container *ngTemplateOutlet=&quot;pegOutLink&quot;&gt;"/> <x id="CLOSE_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;/ng-contain"/></target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">166,167</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.peg-out-to</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4bdf69370ca8b0cae3a17d7b84b59c49cd57288d" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>ScriptPubKey (ASM)</source>
<target>ScriptPubKey (ASM)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">227,229</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">ScriptPubKey (ASM)</note>
<note priority="1" from="meaning">transactions-list.scriptpubkey.asm</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="e191b4f47f3ea7532f83fd498f4860db664ab75c" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>ScriptPubKey (HEX)</source>
<target>ScriptPubKey (HEX)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">231,234</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">ScriptPubKey (HEX)</note>
<note priority="1" from="meaning">transactions-list.scriptpubkey.hex</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f85c05147b720576e50336cf26f63d3b05601699" datatype="html">
<source>This transaction saved <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedGains * 100 | number: '1.0-0' }}"/>% on fees by using native SegWit-Bech32</source>
<target>Denne transaksjonen sparte <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedGains * 100 | number: '1.0-0' }}"/> % på avgifter ved å bruke native SegWit-Bech32</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">1</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">ngbTooltip about segwit gains</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="0ca27703757bf9a636a0b9b61e6a0cf248781cb4" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>SegWit</source>
<target>SegWit</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">1</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">3</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">5</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">SegWit</note>
<note priority="1" from="meaning">tx-features.tag.segwit</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="975f46d122f2ca0a187308399a58b44d61ef08eb" datatype="html">
<source>This transaction saved <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedGains * 100 | number: '1.0-0' }}"/>% on fees by using SegWit and could save <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialBech32Gains * 100 | number : '1.0-0' }}"/>% more by fully upgrading to native SegWit-Bech32</source>
<target>Denne transaksjonen sparte <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedGains * 100 | number: '1.0-0' }}"/> % på avgifter ved å bruke SegWit og kunne spart <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialBech32Gains * 100 | number : '1.0-0' }}"/> % mer ved å oppgradere til native SegWit-Bech32</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">3</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">ngbTooltip about double segwit gains</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1be04d5407059059b596f72696a3d1704ce9c0ef" datatype="html">
<source>This transaction could save <x id="INTERPOLATION" equiv-text="{{ segwitGains.potentialBech32Gains * 100 | number : '1.0-0' }}"/>% on fees by upgrading to native SegWit-Bech32 or <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialP2shGains * 100 | number: '1.0-0' }}"/>% by upgrading to SegWit-P2SH</source>
<target>Denne transaksjonen kunne spart <x id="INTERPOLATION" equiv-text="{{ segwitGains.potentialBech32Gains * 100 | number : '1.0-0' }}"/> % på avgifter ved å oppgradere til native SegWit-Bech32 eller <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialP2shGains * 100 | number: '1.0-0' }}"/> % ved å oppgradere til SegWit-P2SH</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">5</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">ngbTooltip about missed out gains</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="e6da407140d70e08b6fba731455f8e0d72f900b5" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>This transaction uses Taproot</source>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<target>Denne transaksjonen bruker Taproot</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">8</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Taproot tooltip</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="71ed5c65589f49a732b8e93a780200191b2b6596" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Taproot</source>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<target>Taproot</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">8</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">tx-features.tag.taproot</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="5531c86f8e09b83930f66566fb85baf3057e2f51" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>This transaction support Replace-By-Fee (RBF) allowing fee bumping</source>
<target>Denne transaksjonen støtter Replace-By-Fee (RBF) som gjør at du kan endre avgift</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">9</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">RBF tooltip</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f0e7d6d900658ee5ce66d8fef3637caf13891c53" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>RBF</source>
<target>RBF</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">9</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">10</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">RBF</note>
<note priority="1" from="meaning">tx-features.tag.rbf</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="85ce9e4f45873116b746899169cbc3445321d60c" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>This transaction does NOT support Replace-By-Fee (RBF) and cannot be fee bumped using this method</source>
<target>Denne transaksjonen støtter IKKE Replace-By-Fee (RBF), avgiften kan derfor ikke endres.</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">10</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">RBF disabled tooltip</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="b2035d486e8d59980736a224891d9790c981691a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Optimal</source>
<target>Optimal</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-fee-rating/tx-fee-rating.component.html</context>
<context context-type="linenumber">1</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">TX Fee Rating is Optimal</note>
<note priority="1" from="meaning">tx-fee-rating.optimal</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="60601e02e7c1f6c4dbabd0ef0bb8946003db8dec" datatype="html">
<source>Only ~<x id="INTERPOLATION" equiv-text="{{ medianFeeNeeded | feeRounding }}"/> sat/vB was needed to get into this block</source>
<target>Bare ~ <x id="INTERPOLATION" equiv-text="{{ medianFeeNeeded | feeRounding }}"/> sat/vB var nødvendig for å komme inn i denne blokken</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-fee-rating/tx-fee-rating.component.html</context>
<context context-type="linenumber">2</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-fee-rating/tx-fee-rating.component.html</context>
<context context-type="linenumber">3</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">tx-fee-rating.warning-tooltip</note>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="0fa66b0c410bef320d3f370d7c98c51754b5f28f" datatype="html">
<source>Overpaid <x id="INTERPOLATION" equiv-text="{{ overpaidTimes }}"/>x</source>
<target>Overbetalt <x id="INTERPOLATION" equiv-text="{{ overpaidTimes }}"/> x</target>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-fee-rating/tx-fee-rating.component.html</context>
<context context-type="linenumber">2</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-fee-rating/tx-fee-rating.component.html</context>
<context context-type="linenumber">3</context>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">TX Fee Rating is Warning</note>
<note priority="1" from="meaning">tx-fee-rating.overpaid.warning</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="86d26b45470e43b409e589517922276109138e87" datatype="html">
Updating from transifex.
2021-07-27 19:51:38 +03:00
<source>Transaction Fees</source>
Updating from transifex.
2021-08-18 00:54:34 +03:00
<target>Transaksjonsavgift</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
<context context-type="linenumber">6,9</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">34,37</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">fees-box.transaction-fees</note>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="46ae0bacea22bcf409534f1c314735e4983e398a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Latest transactions</source>
<target>Nyeste transaksjoner</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">146,149</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">dashboard.latest-transactions</note>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1cb0c1f40f7ef8d62da2ccdccfdd2b7cdd18d2b9" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>USD</source>
<target>USD</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">152,153</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">dashboard.latest-transactions.USD</note>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="160f1ffbd26df073d0fbd02cf8ce0d8cea7603b0" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Fee</source>
<target>Avgift</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">153,155</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">dashboard.latest-transactions.fee</note>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1f332ec66f3bc8d943c248091be7f92772ba280f" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Expand</source>
<target>Utvid</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">173,174</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">dashboard.expand</note>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="e8bcb762b48cf52fbea66ce9c4f6b970b99a80fd" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Collapse</source>
<target>Slå sammen</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">174,180</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">dashboard.collapse</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1f9a922cb4010ee20eb9a241a22307b670f7628c" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Minimum fee</source>
<target>Minimumsavgift</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">232,233</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Minimum mempool fee</note>
<note priority="1" from="meaning">dashboard.minimum-fee</note>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4c3955cfe5955657297481efaf3ada8c55c75b2c" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Purging</source>
<target>Fjerner</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">233,234</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Purgin below fee</note>
<note priority="1" from="meaning">dashboard.purging</note>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="b9565832c4caef9a03f2b30fe37495ff38566fd5" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Memory usage</source>
<target>Minnebruk</target>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">245,246</context>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Memory usage</note>
<note priority="1" from="meaning">dashboard.memory-usage</note>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="eb7a000cd340b44291d790f7b56f7b926edc275b" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>L-BTC in circulation</source>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<target>L-BTC i omløp</target>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">259,261</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">dashboard.lbtc-pegs-in-circulation</note>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="6e70e73ac050983df55b277deb27955b5a33c606" datatype="html">
<source>API service</source>
<target>API-tjeneste</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
<context context-type="linenumber">37,39</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">api-docs.title</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="b151944861534c4a9e9623537dba0a95f60e4455" datatype="html">
<source>Endpoint</source>
<target>Endepunkt</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
<context context-type="linenumber">45,46</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
<context context-type="linenumber">97,100</context>
</context-group>
<note priority="1" from="description">Api docs endpoint</note>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="eec715de352a6b114713b30b640d319fa78207a0" datatype="html">
<source>Description</source>
<target>Beskrivelse</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
<context context-type="linenumber">62,63</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
<context context-type="linenumber">101,102</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="a706b1ded7506620b153dbcdea8108e6691bbbd9" datatype="html">
<source>Default push: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/><x id="INTERPOLATION" equiv-text="'track-ad"/> action: 'want', data: ['blocks', ...] <x id="INTERPOLATION_1" equiv-text="{{ '}' }}"/><x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> to express what you want pushed. Available: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>blocks<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>, <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>mempool-blocks<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>, <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>live-2h-chart<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>, and <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>stats<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>.<x id="LINE_BREAK" ctype="lb" equiv-text="Push transa"/><x id="LINE_BREAK" ctype="lb" equiv-text="Push transa"/>Push transactions related to address: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/><x id="INTERPOLATION" equiv-text="'track-ad"/> 'track-address': '3PbJ...bF9B' <x id="INTERPOLATION_1" equiv-text="{{ '}' }}"/><x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> to receive all new transactions containing that address as input or output. Returns an array of transactions. <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>address-transactions<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> for new mempool transactions, and <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>block-transactions<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> for new block confirmed transactions.</source>
<target>Standard push: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/> <x id="INTERPOLATION" equiv-text="'track-ad"/> handling: 'want', data: ['blocks', ...] <x id="INTERPOLATION_1" equiv-text="{{ '}' }}"/> <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> for å uttrykke hva du vil ha pushet. Tilgjengelig: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/> blocks <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> , <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/> mempool-blocks <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> , <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/> live-2h-chart <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>, og <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/> stats <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>. <x id="LINE_BREAK" ctype="lb" equiv-text="Push transa"/> <x id="LINE_BREAK" ctype="lb" equiv-text="Push transa"/> Push-transaksjoner relatert til adresse: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/><x id="INTERPOLATION" equiv-text="'track-ad"/> 'track-address': '3PbJ...bF9B' <x id="INTERPOLATION_1" equiv-text="{{ '}' }}"/> <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> for å motta alle nye transaksjoner som inneholder den adressen som inngang eller utgang. Returnerer en tabell av transaksjoner. <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>adress-transactions <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> for nye mempool-transaksjoner, og <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>block-transactions <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> for nye blokkbekreftede transaksjoner.</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
<context context-type="linenumber">102,103</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">api-docs.websocket.websocket</note>
</trans-unit>
<trans-unit id="e351b40b3869a5c7d19c3d4918cb1ac7aaab95c4" datatype="html">
<source>API</source>
<target>API</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.ts</context>
<context context-type="linenumber">48</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="0a668c1c2a17e557a18fc06619998e002f50df1e" datatype="html">
<source>Code Example</source>
<target>Kodeeksempel</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
<context context-type="linenumber">6,7</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
<context context-type="linenumber">13,14</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
<context context-type="linenumber">29,30</context>
</context-group>
<note priority="1" from="description">API Docs code example</note>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</trans-unit>
Pull from transifex
2022-05-19 20:12:21 +04:00
<trans-unit id="d6b673097fb7e79231afc43857e376f69ab9f3e3" datatype="html">
<source>Install Package</source>
<target>Installer pakke</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
<context context-type="linenumber">23,24</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">API Docs install lib</note>
</trans-unit>
<trans-unit id="4edb71f23e3ff228dbabd05e8ffc364fae8ae467" datatype="html">
<source>Response</source>
<target>Respons</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
Pull from transifex
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
<context context-type="linenumber">36,37</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
Pull from transifex
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">API Docs API response</note>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.year" datatype="html">
<source><x id="DATE" equiv-text="counter"/> year</source>
<target> <x id="DATE" equiv-text="counter"/> år</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">3</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.years" datatype="html">
<source><x id="DATE" equiv-text="counter"/> years</source>
<target> <x id="DATE" equiv-text="counter"/> år</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">4</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.month" datatype="html">
<source><x id="DATE" equiv-text="counter"/> month</source>
<target> <x id="DATE" equiv-text="counter"/> måned</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">5</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.months" datatype="html">
<source><x id="DATE" equiv-text="counter"/> months</source>
<target> <x id="DATE" equiv-text="counter"/> måneder</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">6</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.week" datatype="html">
<source><x id="DATE" equiv-text="counter"/> week</source>
<target> <x id="DATE" equiv-text="counter"/> uke</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">7</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.weeks" datatype="html">
<source><x id="DATE" equiv-text="counter"/> weeks</source>
<target> <x id="DATE" equiv-text="counter"/> uker</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">8</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.day" datatype="html">
<source><x id="DATE" equiv-text="counter"/> day</source>
<target> <x id="DATE" equiv-text="counter"/> dag</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">9</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.days" datatype="html">
<source><x id="DATE" equiv-text="counter"/> days</source>
<target> <x id="DATE" equiv-text="counter"/> dager</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">10</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.hour" datatype="html">
<source><x id="DATE" equiv-text="counter"/> hour</source>
<target> <x id="DATE" equiv-text="counter"/> time</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">11</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.hours" datatype="html">
<source><x id="DATE" equiv-text="counter"/> hours</source>
<target> <x id="DATE" equiv-text="counter"/> timer</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">12</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.minute" datatype="html">
<source><x id="DATE" equiv-text="counter"/> minute</source>
<target> <x id="DATE" equiv-text="counter"/> minutt</target>
Updating from transfex.
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">13</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.minutes" datatype="html">
<source><x id="DATE" equiv-text="counter"/> minutes</source>
<target> <x id="DATE" equiv-text="counter"/> minutter</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
<context context-type="linenumber">14</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.second" datatype="html">
<source><x id="DATE" equiv-text="counter"/> second</source>
<target> <x id="DATE" equiv-text="counter"/> sekund</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">15</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.seconds" datatype="html">
<source><x id="DATE" equiv-text="counter"/> seconds</source>
<target> <x id="DATE" equiv-text="counter"/> sekunder</target>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">16</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="2799825781368047816" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Transaction fee</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<target>Transaksjonsavgift</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/shared/pipes/scriptpubkey-type-pipe/scriptpubkey-type.pipe.ts</context>
<context context-type="linenumber">11</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new nginx.conf and nginx-mempool.conf files, and tweak for their specific site configuration. Fixes #81
2020-12-02 04:19:33 +09:00
</body>
</file>
</xliff>
Reference in New Issue Copy Permalink