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

4321 lines
256 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="sl">
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Zapri</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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/alert/alert.ts</context>
<context context-type="linenumber">58,61</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.carousel.slide-number" datatype="html">
<source> Slide <x id="INTERPOLATION" equiv-text="OnHover$ = new"/> of <x id="INTERPOLATION_1" equiv-text="; private _pa"/> </source>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/carousel/carousel.ts</context>
<context context-type="linenumber">114,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">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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Prejšnji</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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/carousel/carousel.ts</context>
<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>
</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Naslednji</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/carousel/carousel.ts</context>
<context context-type="linenumber">147,152</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>Izberi mesec</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/datepicker/datepicker-navigation-select.ts</context>
<context context-type="linenumber">44,49</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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/datepicker/datepicker-navigation-select.ts</context>
<context context-type="linenumber">49,50</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>Izberi leto</target>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/datepicker/datepicker-navigation-select.ts</context>
<context context-type="linenumber">59,63</context>
Update translations from Transifex
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/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>
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>Prejšnji mesec</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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/datepicker/datepicker-navigation.ts</context>
<context context-type="linenumber">24,27</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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/datepicker/datepicker-navigation.ts</context>
<context context-type="linenumber">35,36</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>Naslednji mesec</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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/datepicker/datepicker-navigation.ts</context>
<context context-type="linenumber">47,50</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/datepicker/datepicker-navigation.ts</context>
<context context-type="linenumber">60,64</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>««</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/pagination/pagination.ts</context>
<context context-type="linenumber">182,183</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>«</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/pagination/pagination.ts</context>
<context context-type="linenumber">186,190</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 i18n from transifex.
2021-06-09 13:35:07 -05: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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/pagination/pagination.ts</context>
<context context-type="linenumber">194,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>
</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 i18n from transifex.
2021-06-09 13:35:07 -05: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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/pagination/pagination.ts</context>
<context context-type="linenumber">201,204</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Prva</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/pagination/pagination.ts</context>
<context context-type="linenumber">208,209</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Prejšnja</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/pagination/pagination.ts</context>
<context context-type="linenumber">215,216</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Naslednja</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/pagination/pagination.ts</context>
<context context-type="linenumber">226,228</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Zadnja</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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/pagination/pagination.ts</context>
<context context-type="linenumber">232,233</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">
<source><x id="INTERPOLATION" equiv-text="; } /** *"/></source>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/progressbar/progressbar.ts</context>
<context context-type="linenumber">32,38</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>HH</target>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">40,41</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Ure</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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">46,47</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 i18n from transifex
2021-06-10 09:52:13 -05: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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">51,54</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Minute</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">58,59</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Prištej ure</target>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">63,64</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Odštej ure</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">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">69,70</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Prištej minute</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">76,78</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Odštej minute</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">82,84</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>SS</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">87,88</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Sekunde</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">92,93</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Prištej sekunde</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">100,101</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Odštej sekunde</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">106,110</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.AM" datatype="html">
<source><x id="INTERPOLATION" equiv-text="NgbTime; pr"/></source>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">115,121</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.PM" datatype="html">
<source><x id="INTERPOLATION" equiv-text="t() meridian: b"/></source>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/timepicker/timepicker.ts</context>
<context context-type="linenumber">123,131</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Zapri</target>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="sourcefile">node_modules/@ng-bootstrap/src/toast/toast.ts</context>
<context context-type="linenumber">78,85</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="791a4c4131a0ae0aaf82ddb66dacdc7f1c007c3b" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Registered assets</source>
<target>Registrirana sredstva</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/assets/assets.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">3,8</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">Registered assets page header</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="aef0d676b15fdae8cb70fc3b089cce7399fde9da" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Search asset</source>
<target>Iskanje sredstev</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/assets/assets.component.html</context>
<context context-type="linenumber">9,11</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">Search Assets Placeholder Text</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="99ee4faa69cd2ea8e3678c1f557c0ff1f05aae46" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Clear</source>
<target>Počisti</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/assets/assets.component.html</context>
<context context-type="linenumber">11,16</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">Search Clear Button</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="cff1428d10d59d14e45edec3c735a27b5482db59" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Name</source>
<target>Naziv</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/assets/assets.component.html</context>
<context context-type="linenumber">19,21</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/assets/assets.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">44,46</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">Asset name header</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="4ad173c0e4010b1f25bf58e96a383edc1b59cd80" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Ticker</source>
<target>Oznaka</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/assets/assets.component.html</context>
<context context-type="linenumber">20,21</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/assets/assets.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">45,47</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">Asset ticker header</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="465c39daa2b644679d73a451043622f1610a2084" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Issuer domain</source>
<target>Domena izdajatelja</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/assets/assets.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">21,25</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/assets/assets.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">46,50</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">Asset Issuer Domain header</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="d5e7c95d7c8920ae0a384e3fffb14776b1e203f4" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Asset ID</source>
<target>ID sredstva</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/assets/assets.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">22,25</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
<context-group purpose="location">
<context context-type="sourcefile">src/app/assets/assets.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">47,50</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">Asset ID 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="52686df280be57a57e1e9ecf5786499b147e0e90" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Error loading assets data.</source>
<target>Napaka pri nalaganju podatkov o sredstvih.</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/assets/assets.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">63,71</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">Asset data load error</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="ee8f8008bae6ce3a49840c4e1d39b4af23d4c263" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Assets</source>
<target>Sredstva</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/assets/assets.component.ts</context>
<context context-type="linenumber">40</context>
Updating from transifex.
2021-02-03 15:30:38 +07: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/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">44,46</context>
</context-group>
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/master-page/master-page.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">58,61</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>Naslov</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>Skupaj prejeto</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>Skupaj poslano</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>Stanje</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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">168,169</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/blockchain-blocks/blockchain-blocks.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">19,20</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-blocks/mempool-blocks.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<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>
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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">169,170</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">20,21</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">19,20</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>
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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>Zgoščena vrednost</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="804faeaeb734a942eeb814dd53eceed25427d864" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Timestamp</source>
<target>Datum in čas</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>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">34,37</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">49,52</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 Timestamp</note>
<note priority="1" from="meaning">transaction.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>Prejšnji blok</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>
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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>BSQ Bloki</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>Višina</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">12,14</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/bisq/bisq-transactions/bisq-transactions.component.html</context>
<context context-type="linenumber">22,24</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/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>
<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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq block height 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="a1daf43d26259bffdd5eb2d405c61583540b113b" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Confirmed</source>
<target>Potrjeno</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>
<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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">21,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>
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>Transakcije</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>
<context context-type="linenumber">33,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/master-page/master-page.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">37,40</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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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="8a7b4bd44c0ac71b2e72de0398b303257f7d2f54" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Blocks</source>
<target>Bloki</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.ts</context>
<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>
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>
<context context-type="linenumber">36,39</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">2,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>
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>
<context context-type="linenumber">33,36</context>
</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">40,43</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +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/master-page/master-page.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">48,51</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +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="6b2fdbdddef74630e1076d58786ca339a8c030f0" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Bisq Trading Volume</source>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Bisq obseg trgovanja</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-dashboard/bisq-dashboard.component.html</context>
<context context-type="linenumber">3,7</context>
Update translated strings from Transifex
2020-12-04 23:03:17 +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>
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="d3ad0babadabfa3e3b7f51637651822f3e56a7b1" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Markets</source>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Trgi</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-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>
Update translated strings from Transifex
2020-12-04 23:03:17 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Bisq All Markets</note>
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="ece163b62f5e9b0b68a8d6a2d93e216318f557ba" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Bitcoin Markets</source>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Bitcoin trgi</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>
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>
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">Bisq Bitcoin Markets</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="32072c7fb0469aaf82d256a59b3e0d6ecce973b9" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Currency</source>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Valuta</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">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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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="4d6ee53858628de558a18623894a03c8673bce9e" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Price</source>
<target>Tečaj</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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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 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>
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">78</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-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 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="b666c0101ab9ef128a75fdf05a43184a57de0cff" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Volume (7d)</source>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Obseg (7d)</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">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>
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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Posli (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">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-02-03 15:30:38 +07: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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Najnovejši posli</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>
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>
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/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>
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">Latest Trades 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="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 indeks cen</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 tržna cena</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="1915fb658404dd3fa2a05f7d5fdd774ad72ef422" datatype="html">
Updated i18n from transifex.
2021-05-11 15:31:42 +04:00
<source>View all »</source>
<target>Prikaži vse »</target>
<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>
<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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">110,115</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">dashboard.view-all</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>Pogoji storitve</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">111,118</context>
</context-group>
<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">239,243</context>
Update i18n from transifex.
2021-06-09 13:35:07 -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/docs/docs.component.html</context>
<context context-type="linenumber">33</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/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">152,154</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>
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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Nakup</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>
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="abf29235edbf341b6f626c315ff509f38fbf728a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Sell Offers</source>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Prodaja</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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
<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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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">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 Statistika</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">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/bisq/bisq-stats/bisq-stats.component.ts</context>
<context context-type="linenumber">28</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">BSQ statistics 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="1cde02174ca8cc2cc0b18172cd2ec598aa82dcc7" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Existing amount</source>
<target>Obstoječi znesek</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">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>
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="3218e6768d0d5fbc69d4931819e21451c89ba8ed" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Minted amount</source>
<target>Skupni znesek</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">16</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">58</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 minted 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="32377aae07f946d943f9361c8e518f714988c619" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Burnt amount</source>
<target>Uničeno (burned)</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">20</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">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>
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-transfers/bisq-transfers.component.html</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context context-type="linenumber">68</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">BSQ burnt 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="7882f2edb1d4139800b276b6b0bbf5ae0b2234ef" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Addresses</source>
<target>Naslovi</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>
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>Neporabljeni TXO</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>Porabljeni TXO</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>Tržna kapitalizacija</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Datum</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>Znesek</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>
<context context-type="linenumber">20,22</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">121,122</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>
<target>Vhodi</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>
<target>Izhodi</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>Izdani znesek</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>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">54</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>Tip</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">211,213</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>Verzija</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>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">125,126</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">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>Transakcija</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>
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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">238,239</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>
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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">239,240</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>Vključeno v blok</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>Lastnosti</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>Omrežnina na vBajt</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>Podrobnosti</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>
<target>Vhodi &amp; Izhodi</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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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">194,197</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">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>
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>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">133,132</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>BSQ Transakcije</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">120,121</context>
Update from transifex.
2021-02-15 00:15:04 +07:00
</context-group>
</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Provizija za registracijo sredstva</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Tajno glasovanje</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Zahteva za izplačilo</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 i18n from transifex
2021-06-10 09:52:13 -05: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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Nepravilno</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Zaklepanje</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Plačilo provizije za trgovanje</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Dokaz o uničenosti</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Predlog</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Zahteva za povračilo</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Prenos 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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Odklepanje</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Razkritje rezultatov glasovanja</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>Izberi vse</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>Počisti izbiro</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Posli</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 i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Obseg</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>
<target>Odprtokodni projekt 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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f447b21299afc5bc9dadade96dbc90114bea837a" datatype="html">
Updated from transifex.
2021-06-17 11:09:52 -05:00
<source>Building a mempool and blockchain explorer for the Bitcoin community, focusing on the transaction fee market and multi-layer ecosystem, without any advertising, altcoins, or third-party trackers.</source>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<target>Raziskovalec blokov in mempool-a razvit za Bitcoin skupnost, osredotočen na trg omrežnin za transakcije in večplastni ekosistem. Brez oglaševanja, alternativnih kriptovalut in sledilcev tretjih ponudnikov.</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>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">13,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>
</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Sponzorji - podjetja 🚀</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">35,38</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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Sponzorji - posamezniki ❤️</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">65,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">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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8d0b91c3b649c0237734a2c27585ed0409451523" datatype="html">
Updating translations from transifex.
2021-03-07 20:13:39 +07:00
<source>Become a sponsor ❤️</source>
<target>Postanite sponzor ❤️</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">77,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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">about.become-a-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="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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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">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>
<context-group purpose="location">
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context context-type="linenumber">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">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="1405c5f1a9834338ff13442c550927ab7144fdc8" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Community Integrations</source>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Integracije</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">82,85</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.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>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Zavezništva skupnosti</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">153,155</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>
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>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Sodelujoč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/components/about/about.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">169,171</context>
</context-group>
<note priority="1" from="description">about.contributors</note>
</trans-unit>
<trans-unit id="3d395b07b1f87656ed773adcbb3daf8e00c08779" datatype="html">
<source>Project Members</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">181,183</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>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Vzdrževalci</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">194,196</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>O projektu</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>
Pulled from transifex
2021-12-26 11:15:19 +04: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>
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>
<context context-type="linenumber">45,48</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">50,53</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/master-page/master-page.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">64,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>
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="9f10a0577222a7d6c35a889453fa3a794750d9c4" datatype="html">
<source>multisig <x id="INTERPOLATION" equiv-text="{{ multisigM }}"/> of <x id="INTERPOLATION_1" equiv-text="{{ multisigN }}"/></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/address-labels/address-labels.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">address-labels.multisig</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="31c09dcc0ab351767631539b208d5f7de4005473" datatype="html">
<source>Lightning <x id="INTERPOLATION" equiv-text="{{ lightning }}"/></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/address-labels/address-labels.component.html</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 context-type="linenumber">11</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">address-labels.upper-layer-peg-out</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="696ade981a05c12e10df38ba6218c76e318813b3" datatype="html">
<source>Liquid <x id="INTERPOLATION" equiv-text="{{ liquid }}"/></source>
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-labels/address-labels.component.html</context>
<context context-type="linenumber">17</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">address-labels.upper-layer-peg-out</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="04ffd930e7a2dc086c952a3a51b42c836bf21cc1" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Unconfidential</source>
<target>Javno</target>
<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>
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>
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>Napaka pri nalaganju podatkov naslova.</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="cedcc9d48ffb2714e7b2f012ab67bd21f8e96a18" datatype="html">
<source><x id="START_ITALIC_TEXT" ctype="x-i" equiv-text="The number of transactions on this address exceeds the Electrum server limit&lt;/i&gt; &lt;br&gt;&lt;br&gt;"/>The number of transactions on this address exceeds the Electrum server limit<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>Zaupno</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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">152</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">247,249</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">128,129</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.confidential</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="address.component.browser-title" datatype="html">
<source>Address: <x id="INTERPOLATION" equiv-text="this.addressString"/></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/address/address.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<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>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="f8c91b77ad53ccd0f6adb4a6ea3a0f5c3329688b" datatype="html">
<source>Asset</source>
<target>Sredstvo</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">
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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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">Liquid Asset page title</note>
<note priority="1" from="meaning">asset</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="2346453954cf21bf1326e790bfb3cb3369574ed9" datatype="html">
<source>Name</source>
<target>Naziv</target>
Update translations from Transifex
2020-12-05 00:36:00 +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">23</context>
Update translations from Transifex
2020-12-05 00:36:00 +09:00
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Liquid Asset name</note>
<note priority="1" from="meaning">asset.name</note>
Update translations from Transifex
2020-12-05 00:36:00 +09:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="8f301d45550dcb7dec91cc1fdc1f65f13c6a2892" datatype="html">
<source>Precision</source>
<target>Decimalna mesta</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>Izdajatelj</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>Izdajna transakcija</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 in</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">46</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 out</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">50</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>Uničeno (burned)</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">58</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>Znesek v obtoku</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">62</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>
<context context-type="linenumber">66</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>
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 In/Out in Burn Transakcij</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>Izdajnih in Burn Transakcij</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>Napaka pri nalaganju podatkov o sredstvu.</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">141</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>
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>
<context context-type="linenumber">73</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="2b34680062c4aed90c4d846eab42d6e99501b783" datatype="html">
<source>Offline</source>
<target>Brez povezave</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>
<context context-type="linenumber">7,8</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>Ponovno povezovanje...</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>
<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/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>Omrežja 2. plasti</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>
<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/master-page/master-page.component.html</context>
<context context-type="linenumber">22,23</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.layer2-networks-header</note>
</trans-unit>
<trans-unit id="f65253954b66e929a8b4d5ecaf61f9129f8cec64" datatype="html">
<source>Dashboard</source>
<target>Pregledna plošča</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">30,32</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>
<context context-type="linenumber">30,33</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/master-page/master-page.component.html</context>
<context context-type="linenumber">33,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">master-page.dashboard</note>
</trans-unit>
<trans-unit id="299f97b8ee9c62d45f2cc01961aa1e5101d6d05a" datatype="html">
<source>Stats</source>
<target>Statistika</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">39,42</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">43,47</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>
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">42,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>
<context context-type="linenumber">47,50</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>
<trans-unit id="bdf0e930eb22431140a2eaeacd809cc5f8ebd38c" datatype="html">
<source>Next Block</source>
<target>Naslednji blok</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">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/block/block.component.html</context>
<context context-type="linenumber">19,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">Next Block</note>
</trans-unit>
<trans-unit id="a0e07a711d171f4d40dd388d70ed32f9b8101e0a" datatype="html">
<source>Previous Block</source>
<target>Prejšnji blok</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">26,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">Previous Block</note>
</trans-unit>
<trans-unit id="07193288a0312875e18f38c3a2486b927a15520a" datatype="html">
<source>Timestamp</source>
<target>Datum in čas</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">55,57</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/latest-blocks/latest-blocks.component.html</context>
<context context-type="linenumber">10,12</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.timestamp</note>
</trans-unit>
<trans-unit id="7faaaa08f56427999f3be41df1093ce4089bbd75" datatype="html">
<source>Size</source>
<target>Velikost</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">64,66</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/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>
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-graph/mempool-graph.component.ts</context>
<context context-type="linenumber">257</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>
<context context-type="linenumber">94,97</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.size</note>
</trans-unit>
<trans-unit id="919f2fd60a898850c24b1584362bbf18a4628bcb" datatype="html">
<source>Weight</source>
<target>Utež</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">68,70</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.weight</note>
</trans-unit>
<trans-unit id="0b47a777f024ab4e3cdf0062acb4d86e9ae1f635" datatype="html">
<source>Median fee</source>
<target>Mediana omrežnin</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>
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">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>
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/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>
<context context-type="linenumber">14,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/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>
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">13,15</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>
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/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>
<context context-type="linenumber">231</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>
<context context-type="linenumber">130,134</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>
<context context-type="linenumber">185,189</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>Na podlagi povprečne native segwit transakcije (140 vBajtov).</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>Skupaj omrežnin</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">83,84</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>
<context context-type="linenumber">98,100</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>Nagrada + omrežnine:</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">90,92</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>
<context context-type="linenumber">102,106</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>Rudar</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">107,108</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>
<context context-type="linenumber">129,131</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>Merkle koren</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">133,135</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>Težavnost</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">143,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
<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>
<context context-type="linenumber">147,149</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>Glava bloka (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>
<context context-type="linenumber">151,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">block.header</note>
</trans-unit>
<trans-unit id="5f32c623f92bf3ca31202cc6281d4abd5febaf6a" datatype="html">
<source>Details</source>
<target>Podrobnosti</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">162,167</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>Napaka pri nalaganju podatkov bloka.</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">256,266</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>
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>
<context context-type="linenumber">141</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="clipboard.copied-message" datatype="html">
<source>Copied!</source>
<target>Kopirano!</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/clipboard/clipboard.component.ts</context>
<context context-type="linenumber">15</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="6e70e73ac050983df55b277deb27955b5a33c606" datatype="html">
<source>API service</source>
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/docs/api-docs.component.html</context>
<context context-type="linenumber">12,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">api-docs.title</note>
</trans-unit>
<trans-unit id="b151944861534c4a9e9623537dba0a95f60e4455" datatype="html">
<source>Endpoint</source>
<target>Končna točka</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/docs/api-docs.component.html</context>
<context context-type="linenumber">32,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/docs/api-docs.component.html</context>
<context context-type="linenumber">49,50</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/docs/api-docs.component.html</context>
<context context-type="linenumber">62,63</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/docs/api-docs.component.html</context>
<context context-type="linenumber">75,76</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/docs/api-docs.component.html</context>
<context context-type="linenumber">88,89</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/docs/api-docs.component.html</context>
<context context-type="linenumber">101,102</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/docs/api-docs.component.html</context>
<context context-type="linenumber">114,115</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/docs/api-docs.component.html</context>
<context context-type="linenumber">127,128</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/docs/api-docs.component.html</context>
<context context-type="linenumber">140,141</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/docs/api-docs.component.html</context>
<context context-type="linenumber">157,158</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/docs/api-docs.component.html</context>
<context context-type="linenumber">174,175</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/docs/api-docs.component.html</context>
<context context-type="linenumber">187,188</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/docs/api-docs.component.html</context>
<context context-type="linenumber">200,201</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/docs/api-docs.component.html</context>
<context context-type="linenumber">213,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/components/docs/api-docs.component.html</context>
<context context-type="linenumber">226,227</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/docs/api-docs.component.html</context>
<context context-type="linenumber">243,244</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/docs/api-docs.component.html</context>
<context context-type="linenumber">268,269</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/docs/api-docs.component.html</context>
<context context-type="linenumber">285,286</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/docs/api-docs.component.html</context>
<context context-type="linenumber">298,299</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/docs/api-docs.component.html</context>
<context context-type="linenumber">311,312</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/docs/api-docs.component.html</context>
<context context-type="linenumber">324,325</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/docs/api-docs.component.html</context>
<context context-type="linenumber">337,338</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
</context-group>
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/docs/api-docs.component.html</context>
<context context-type="linenumber">350,351</context>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</context-group>
Update translations from Transifex
2020-12-05 00:36:00 +09:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">363,364</context>
Update translations from Transifex
2020-12-05 00:36:00 +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/docs/api-docs.component.html</context>
<context context-type="linenumber">376,377</context>
Update translations from Transifex
2020-12-05 00:36:00 +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/docs/api-docs.component.html</context>
<context context-type="linenumber">389,390</context>
Update translations from Transifex
2020-12-05 00:36:00 +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/docs/api-docs.component.html</context>
<context context-type="linenumber">402,403</context>
Update translations from Transifex
2020-12-05 00:36:00 +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/docs/api-docs.component.html</context>
<context context-type="linenumber">415,416</context>
Update translations from Transifex
2020-12-05 00:36:00 +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/docs/api-docs.component.html</context>
<context context-type="linenumber">428,429</context>
Update translations from Transifex
2020-12-05 00:36:00 +09:00
</context-group>
Update translation strings from Transifex
2020-12-05 02:39:50 +09:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">445,446</context>
Update translation strings from Transifex
2020-12-05 02:39:50 +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/docs/api-docs.component.html</context>
<context context-type="linenumber">458,459</context>
Update translation strings from Transifex
2020-12-05 02:39:50 +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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">475,476</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">488,489</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">501,502</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">518,519</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/docs/api-docs.component.html</context>
<context context-type="linenumber">531,532</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">544,545</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">557,558</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">570,571</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">583,584</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">596,597</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">609,610</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">622,623</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">635,636</context>
Update strings from transifex.
2020-12-08 11:58:43 +07: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/docs/api-docs.component.html</context>
<context context-type="linenumber">648,651</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/docs/api-docs.component.html</context>
<context context-type="linenumber">666,669</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">Api docs endpoint</note>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="eec715de352a6b114713b30b640d319fa78207a0" datatype="html">
<source>Description</source>
<target>Opis</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/docs/api-docs.component.html</context>
<context context-type="linenumber">36,37</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/docs/api-docs.component.html</context>
<context context-type="linenumber">53,54</context>
Update strings from transifex.
2020-12-08 11:58:43 +07:00
</context-group>
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/docs/api-docs.component.html</context>
<context context-type="linenumber">66,67</context>
Updating from transfex.
2021-07-25 01:49:35 +03: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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">79,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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">92,94</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">105,106</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.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>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">131,132</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 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/docs/api-docs.component.html</context>
<context context-type="linenumber">144,145</context>
Updating from transfex.
2021-07-25 01:49:35 +03: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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">161,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>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">178,179</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">204,205</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">217,218</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">230,231</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">247,248</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">259,260</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/docs/api-docs.component.html</context>
<context context-type="linenumber">272,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>
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">289,290</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">302,303</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">315,316</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 i18n from transifex.
2021-08-03 18:38:34 +03:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">328,329</context>
Updating i18n from transifex.
2021-08-03 18:38:34 +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/docs/api-docs.component.html</context>
<context context-type="linenumber">341,342</context>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
</context-group>
Update translated strings from Transifex
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">354,355</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">367,369</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/docs/api-docs.component.html</context>
<context context-type="linenumber">380,381</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">393,394</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 i18n from transifex.
2021-06-11 23:27:29 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">406,407</context>
Updating i18n from transifex.
2021-06-11 23:27:29 -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/docs/api-docs.component.html</context>
<context context-type="linenumber">419,420</context>
Updating i18n from transifex.
2021-06-11 23:27:29 -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/docs/api-docs.component.html</context>
<context context-type="linenumber">432,433</context>
Updating i18n from transifex.
2021-06-11 23:27:29 -05:00
</context-group>
Updated from transifex.
2021-06-17 11:09:52 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">449,450</context>
Updated from transifex.
2021-06-17 11:09:52 -05:00
</context-group>
Updating i18n from transifex.
2021-06-11 23:27:29 -05:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">462,463</context>
Updating i18n from transifex.
2021-06-11 23:27:29 -05: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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">479,480</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">492,493</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">505,506</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">522,523</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">535,536</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">548,549</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">561,562</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">574,575</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">587,588</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">600,601</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">613,614</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">626,627</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">639,640</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">652,653</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">670,671</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="2761d0de651f1c4395e6e7fbc7fded09918f8dcb" datatype="html">
<source>Returns details about difficulty adjustment.</source>
<target>Vrne podrobnosti o prilagoditvi težavnosti.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">37,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>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="842f6eb4d8f230db4bdf483a08d4d2a77e2d5869" datatype="html">
<source>Provides list of available currencies for a given base currency. </source>
<target>Vrne seznam razpoložljivih valut (valutnih parov) za podano osnovno valuto.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">54,56</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="9c7dafb6f51e229d02a80844f6f99a01487e7cb2" datatype="html">
<source>Provides list of open offer prices for a single market.</source>
<target>Vrne seznam cen odprtih naročil za podan trg.</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/docs/api-docs.component.html</context>
<context context-type="linenumber">67,69</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="9e95c144fcb1afd7724dc5a3aad31125a59d9d71" datatype="html">
<source>Provides hi/low/open/close data for a given market. This can be used to generate a candlestick chart.</source>
<target>Vrne najvišji/najnižji/odpiralni/zadnji tečaj za podan trg. Te podatke lahko uporabimo za ustvarjanje svečnega grafikona.</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/docs/api-docs.component.html</context>
<context context-type="linenumber">80,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
</trans-unit>
<trans-unit id="9c6e8e72b7a5f4e8a0e8ede12ab5ede4e0af2484" datatype="html">
<source>Provides list of available markets.</source>
<target>Vrne seznam razpoložljivih trgov.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">93,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>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="a02929fcc15f8b54d2f6d602722d2c7d1d790a2a" datatype="html">
<source>Provides list of open offer details for a single market.</source>
<target>Vrne seznam odprtih naročil za podan trg.</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/docs/api-docs.component.html</context>
<context context-type="linenumber">106,108</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
</trans-unit>
<trans-unit id="342f8a4ceda8cda17584e920ad7459b41e86b069" datatype="html">
<source>Provides 24 hour price ticker for single market or all markets</source>
<target>Vrne podatke o ceni (ticker, 24h) na podanem trgu ali vseh trgih.</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/docs/api-docs.component.html</context>
<context context-type="linenumber">119,121</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="dd194a2109134d62cb518ba0ccfc296701de5522" datatype="html">
<source>Provides list of completed trades for a single market.</source>
<target>Vrne seznam zaključenih poslov za izbran trg.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">132,134</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
</trans-unit>
<trans-unit id="b925fd1f3213560c0737f6016be18eaba7c28c9c" datatype="html">
<source>Provides periodic volume data in terms of base currency for one or all markets.</source>
<target>Vrne periodične podatke o obsegu trgovanja v osnovni valuti za izbran trg ali vse trge.</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/docs/api-docs.component.html</context>
<context context-type="linenumber">145,147</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="088d201b8d0589637d7aa64457a6cdd97a5d0f11" datatype="html">
<source>Returns statistics about all Bisq transactions.</source>
<target>Vrne statistične podatke o vseh Bisq transakcijah.</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/docs/api-docs.component.html</context>
<context context-type="linenumber">162,164</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="e12cd52eaa77b446ba97436c145b59741151adf3" datatype="html">
<source>Returns details about an address. Available fields: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>address<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;"/>chain_stats<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;"/>mempool_stats<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>. <x id="INTERPOLATION" equiv-text="{{ '{' }}"/>chain,mempool<x id="INTERPOLATION_1" equiv-text="{{ '}' }}"/>_stats each contain an object with <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>tx_count<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;"/>funded_txo_count<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;"/>funded_txo_sum<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;"/>spent_txo_count<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;"/>spent_txo_sum<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">179,180</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
</trans-unit>
<trans-unit id="c9f5914dbba46a8dc4ab4e81b40b1582eea7c5e2" datatype="html">
<source>Get transaction history for the specified address/scripthash, sorted with newest first. Returns up to 50 mempool transactions plus the first 25 confirmed transactions. You can request more confirmed transactions using <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>:last_seen_txid<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (see below).</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">192,193</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="5676910aa3ffb568079a7499b366744fe3fd87ea" datatype="html">
<source>Get confirmed transaction history for the specified address/scripthash, sorted with newest first. Returns 25 transactions per page. More can be requested by specifying the last txid seen by the previous query.</source>
<target>Pridobi zgodovino potrjenih transakcij za podan naslov/scripthash, urejeno po času, najnovejša na začetku. Vrne 25 transakcij na stran. Več jih je mogoče pridobiti z navedbo zadnjega vrnjenega txid-ja.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">205,207</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
</trans-unit>
<trans-unit id="f10009779c64e19e20414fae506f27118420aa33" datatype="html">
<source>Get unconfirmed transaction history for the specified address/scripthash. Returns up to 50 transactions (no paging).</source>
<target>Pridobi zgodovino nepotrjenih transakcij za podan naslov/scripthash. Vrne do 50 transakcij (brez ostranjevanja, angl. paging).</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">218,220</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
</trans-unit>
<trans-unit id="4eb50557085c85bfca995b6ee0de56ec3f5e97eb" datatype="html">
<source>Get the list of unspent transaction outputs associated with the address/scripthash. Available fields: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>txid<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;"/>vout<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;"/>value<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;"/>status<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (with the status of the funding tx).<x id="START_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;ng-container *ngIf=&quot;network.val === 'liquid'&quot;&gt;"/>There is also a <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>valuecommitment<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> field that may appear in place of <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>value<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>, plus the following additional fields: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>asset<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;"/>assetcommitment<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;"/>nonce<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;"/>noncecommitment<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;"/>surjection_proof<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;"/>range_proof<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>.<x id="CLOSE_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;/ng-container&gt;"/></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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">231,233</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
</trans-unit>
<trans-unit id="b885a96aa1a96bff3f603dab79746f90eef5cbdf" datatype="html">
<source>Returns information about a Liquid asset.</source>
<target>Vrne podatke o Liquid sredstvu.</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/docs/api-docs.component.html</context>
<context context-type="linenumber">248,250</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
</trans-unit>
<trans-unit id="4a0bf20cf26a4f4a387bed5c3d47c23294cb606e" datatype="html">
<source>Returns transactions associated with the specified Liquid asset. For the network's native asset, returns a list of peg in, peg out, and burn transactions. For user-issued assets, returns a list of issuance, reissuance, and burn transactions. Does not include regular transactions transferring this asset.</source>
<target>Vrne transakcije povezane s podanim Liquid sredstvom. Za izvorno sredstvo omrežja, vrne seznam peg in, peg out, in burn transakcij. Za uporabniško izdana sredstva, vrne seznam izdajnih, transakcij ponovne izdaje in burn transakcij. Ne vključuje rednih transakcij prenosa tega sredstva.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">260,262</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="44a238eb28145f904f3a5bbfd4050987668f78d0" datatype="html">
<source>Get the current total supply of the specified asset. For the native asset (L-BTC), this is calculated as [chain,mempool]_stats.peg_in_amount - [chain,mempool]_stats.peg_out_amount - [chain,mempool]_stats.burned_amount. For issued assets, this is calculated as [chain,mempool]_stats.issued_amount - [chain,mempool]_stats.burned_amount. Not available for assets with blinded issuances. If /decimal is specified, returns the supply as a decimal according to the asset's divisibility. Otherwise, returned in base units.</source>
<target>Pridobi trenutni znesek v obtoku za podano sredstvo. Za izvorno sredstvo (L-BTC), je izračunan kot [chain,mempool]_stats.peg_in_amount - [chain,mempool]_stats.peg_out_amount - [chain,mempool]_stats.burned_amount. Za izdana sredstva pa [chain,mempool]_stats.issued_amount - [chain,mempool]_stats.burned_amount. Ni na voljo za sredstva z zaupnim zneskom izdaje. Če je podan /decimal, vrne znesek na število decimalnih mest sredstva natančno. Sicer vrnjeno v osnovnih enotah.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">273,275</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="194d480219559b855b01ea58459066e3c63acdb2" datatype="html">
<source>Returns details about a block. Available fields: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>id<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;"/>height<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;"/>version<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;"/>timestamp<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;"/>bits<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;"/>nonce<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;"/>merkle_root<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;"/>tx_count<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;"/>size<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;"/>weight<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>,<x id="START_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;ng-container *ngIf=&quot;network.val === 'liquid'&quot;&gt;"/><x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>proof<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>,<x id="CLOSE_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="&lt;/ng-container&gt;"/> and <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>previousblockhash<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">290,291</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
</trans-unit>
<trans-unit id="2ca235ae8c14854eb6ea6d42fd2521204d3db01f" datatype="html">
<source>Returns the hex-encoded block header.</source>
<target>Vrne šestnajstiško vrednost glave bloka.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">303,305</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="36df9865e9099d98537ea69c9cfdc035d1b64116" datatype="html">
<source>Returns the hash of the block currently at <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>:height<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">316,317</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
</trans-unit>
<trans-unit id="6d5aacdd7e6c375570a88c25bfd0be82beba4c7b" datatype="html">
<source>Returns the raw block representation in binary.</source>
<target>Vrne neobdelane podatke o bloku v binarni obliki.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">329,331</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
</trans-unit>
<trans-unit id="a2c00fbdcce9d6291c3b04c67979f9694be23f28" datatype="html">
<source>Returns the confirmation status of a block. Available fields: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>in_best_chain<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (boolean, false for orphaned blocks), <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>next_best<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (the hash of the next block, only available for blocks in the best chain).</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">342,343</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
</trans-unit>
<trans-unit id="4767bdd2059533d5eed7f3fe7cf0be5c260cdb00" datatype="html">
<source>Returns the height of the last block.</source>
<target>Vrne višino zadnjega bloka.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">355,357</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
</trans-unit>
<trans-unit id="940153d58769f1a8f50dba2458693142675a5dcb" datatype="html">
<source>Returns the hash of the last block.</source>
<target>Vrne zgoščeno vrednost (hash) zadnjega bloka.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
</trans-unit>
<trans-unit id="3e08815110b2e5ce8aa7256ed05a2faf6dbb7077" datatype="html">
<source>Returns the transaction at index <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>:index<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> within the specified block.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">381,382</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
</trans-unit>
<trans-unit id="3846f2527c3c9a50bb84b2c941a876f66797449b" datatype="html">
<source>Returns a list of all txids in the block.</source>
<target>Vrne seznam vseh txid-jev v bloku.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">394,396</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
</trans-unit>
<trans-unit id="1126cb2e03d0371d03b57047052d4ff1b6556753" datatype="html">
<source>Returns a list of transactions in the block (up to 25 transactions beginning at <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>start_index<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>). Transactions returned here do not have the <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>status<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> field, since all the transactions share the same block and confirmation status.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">407,408</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
</trans-unit>
<trans-unit id="f8380186899495340cbfe7fb836ba664fb4b52af" datatype="html">
<source>Returns the 10 newest blocks starting at the tip or at <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>:start_height<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> if specified.</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">420,421</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">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">433,434</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
</trans-unit>
<trans-unit id="b95b496df2b0f016831d0984f3798a2e22b74103" datatype="html">
<source>Returns current mempool as projected blocks.</source>
<target>Vrne trenutni mempool, kot projekcijo blokov.</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">450,452</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">API Docs for /api/v1/fees/mempool-blocks</note>
<note priority="1" from="meaning">api-docs.fees.mempool-blocks</note>
</trans-unit>
<trans-unit id="39f61f2d1434d921a1f80a2a2f0903f06e9fd4df" datatype="html">
<source>Returns our currently suggested fees for new transactions.</source>
<target>Vrne trenutno predlagano omrežnino za nove transakcije.</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">463,465</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">API Docs for /api/v1/fees/recommended</note>
<note priority="1" from="meaning">api-docs.fees.recommended</note>
</trans-unit>
<trans-unit id="7d43b13f97ee52aae72d728a52af2e31f6edbf38" datatype="html">
<source>Returns current mempool backlog statistics.</source>
<target>Vrne trenutno statistiko mempoola.</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">480,482</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">API Docs for /api/mempool</note>
<note priority="1" from="meaning">api-docs.mempool.mempool</note>
</trans-unit>
<trans-unit id="23c346e87b137b1807bac13c27d19dc18f745f8f" datatype="html">
<source>Get the full list of txids in the mempool as an array. The order of the txids is arbitrary and does not match bitcoind.</source>
<target>Vrne celoten seznam txid-jev v mempoolu v obliki polja. Vrstni red txid-jev je arbitraren in se ne ujema z bitcoind.</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">493,495</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">API Docs for /api/mempool/txids</note>
<note priority="1" from="meaning">api-docs.mempool.txids</note>
</trans-unit>
<trans-unit id="af1a465e50097fabbe55bf5dbcf5d0702bdbc98b" datatype="html">
<source>Get a list of the last 10 transactions to enter the mempool. Each transaction object contains simplified overview data, with the following fields: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>txid<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;"/>fee<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;"/>vsize<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;"/>value<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>.</source>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">506,507</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">API Docs for /api/mempool/recent</note>
<note priority="1" from="meaning">api-docs.mempool.recent</note>
</trans-unit>
<trans-unit id="4ebf8d4a2433cca5a8a933ef8ccef1b01e45acef" datatype="html">
<source>Returns the ancestors and the best descendant fees for a transaction.</source>
<target>Vrne prednike in najboljšo omrežnino za potomce transakcije.</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">523,525</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">API Docs for /api/v1/fees/cpfp</note>
<note priority="1" from="meaning">api-docs.fees.cpfp</note>
</trans-unit>
<trans-unit id="a8ea1ec66e7bb9f92e87ae5482e50748baafffd2" datatype="html">
<source>Returns details about a transaction. Available fields: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>txid<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;"/>version<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;"/>locktime<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;"/>size<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;"/>weight<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;"/>fee<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;"/>vin<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;"/>vout<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;"/>status<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/>.</source>
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/docs/api-docs.component.html</context>
<context context-type="linenumber">536,537</context>
Updating from transifex.
2021-04-26 04:05:55 +04: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="34c21c242665d87bf22645c90f571bd5078eac93" datatype="html">
<source>Returns a transaction serialized as hex.</source>
<target>Vrne transakcijo v šestnajstiški obliki.</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">549,551</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
</trans-unit>
<trans-unit id="d51106cc898981e9862d35a4db40796f0cf464f8" datatype="html">
<source>Returns a merkle inclusion proof for the transaction using <x id="START_LINK" ctype="x-a" equiv-text="&lt;a href=&quot;https://bitcoin.org/en/glossary/merkle-block&quot;&gt;"/>bitcoind's merkleblock<x id="CLOSE_LINK" ctype="x-a" equiv-text="&lt;/a&gt;"/> format.</source>
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/docs/api-docs.component.html</context>
<context context-type="linenumber">562,563</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
</trans-unit>
<trans-unit id="a57953199686e9980df838cb25edb51691941ac5" datatype="html">
<source>Returns a merkle inclusion proof for the transaction using <x id="START_LINK" ctype="x-a" equiv-text="&lt;a href=&quot;https://electrumx.readthedocs.io/en/latest/protocol-methods.html#blockchain-transaction-get-merkle&quot;&gt;"/>Electrum's blockchain.transaction.get_merkle format.<x id="CLOSE_LINK" ctype="x-a" equiv-text="&lt;/a&gt;"/></source>
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/docs/api-docs.component.html</context>
<context context-type="linenumber">575,576</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
</trans-unit>
<trans-unit id="fe9a40b2ff9674b4ab7d82624ffed340c9ee5b89" datatype="html">
<source>Returns the spending status of a transaction output. Available fields: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>spent<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (boolean), <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>txid<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (optional), <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>vin<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (optional), and <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>status<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (optional, the status of the spending tx).</source>
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/docs/api-docs.component.html</context>
<context context-type="linenumber">588,589</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
</trans-unit>
<trans-unit id="0358265aa88614843e1f5e887b94c673808c84f1" datatype="html">
<source>Returns the spending status of all transaction outputs.</source>
<target>Vrne stanje porabe vseh izhodov transakcije.</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/docs/api-docs.component.html</context>
<context context-type="linenumber">601,603</context>
Updating from transifex.
2021-04-26 04:05:55 +04: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="fd42ee72bb64b93578d7d2142ae50796d0056d7a" datatype="html">
<source>Returns a transaction as binary data.</source>
<target>Vrne transakcijo v binarni obliki.</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">614,616</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
</trans-unit>
<trans-unit id="7e784cfa5833e7b54d4dfc723fabde94f66ebde3" datatype="html">
<source>Returns the confirmation status of a transaction. Available fields: <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>confirmed<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (boolean), <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>block_height<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (optional), and <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>block_hash<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> (optional).</source>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">627,628</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="e9a58657c410cf65dba4c3cdfb1af7099dedb241" datatype="html">
<source>Returns :length of latest Bisq transactions, starting from :index.</source>
<target>Vrne :length zadnjih Bisq transakcij, z začetkom od :index.</target>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">640,642</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
</trans-unit>
<trans-unit id="01723473ecc53cab60ef1b37dc39d8941994d56f" datatype="html">
<source>Broadcast a raw transaction to the network. The transaction should be provided as hex in the request body. The <x id="START_TAG_CODE" ctype="x-code" equiv-text="&lt;code&gt;"/>txid<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="&lt;/code&gt;"/> will be returned on success.</source>
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/docs/api-docs.component.html</context>
<context context-type="linenumber">653,654</context>
Updating from transifex.
2021-04-26 04:05:55 +04: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="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>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.html</context>
<context context-type="linenumber">671,672</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">api-docs.websocket.websocket</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="e351b40b3869a5c7d19c3d4918cb1ac7aaab95c4" datatype="html">
<source>API</source>
<target>API</target>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/api-docs.component.ts</context>
<context context-type="linenumber">42</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="0a668c1c2a17e557a18fc06619998e002f50df1e" datatype="html">
<source>Code Example</source>
<target>Primer</target>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/code-template.component.html</context>
<context context-type="linenumber">6,7</context>
Update translations from transifex.
2021-05-08 01:12:57 +04: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/docs/code-template.component.html</context>
<context context-type="linenumber">13,14</context>
Update translations from transifex.
2021-05-08 01:12:57 +04: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/docs/code-template.component.html</context>
<context context-type="linenumber">29,30</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">API Docs code example</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="d6b673097fb7e79231afc43857e376f69ab9f3e3" datatype="html">
<source>Install Package</source>
<target>Namestitev paketa</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/docs/code-template.component.html</context>
<context context-type="linenumber">23,24</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">API Docs install lib</note>
Updating from transfex.
2021-07-25 01:49:35 +03:00
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="4edb71f23e3ff228dbabd05e8ffc364fae8ae467" datatype="html">
<source>Response</source>
<target>Odziv</target>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/code-template.component.html</context>
<context context-type="linenumber">36,37</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">API Docs API response</note>
</trans-unit>
<trans-unit id="fcfd4675b4c90f08d18d3abede9a9a4dff4cfdc7" datatype="html">
<source>Documentation</source>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="sourcefile">src/app/components/docs/docs.component.html</context>
<context context-type="linenumber">4</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
</context-group>
Updating from transifex.
2021-02-03 15:30:38 +07:00
<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">61,64</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">documentation.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="8f3ac0544491bf048120928d39e02a6baeb0b278" datatype="html">
<source>Privacy Policy</source>
<target>Politika zasebnosti</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/docs/docs.component.html</context>
<context context-type="linenumber">35</context>
Updating from transifex.
2021-04-26 04:05:55 +04: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>
<context context-type="linenumber">154,156</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">Privacy Policy</note>
<note priority="1" from="meaning">shared.privacy-policy</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="f2385584215e9b925b6347de866110d5e07d3a35" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Low priority</source>
<target>Počasi</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
Updating from transifex.
2021-07-11 22:06:14 +03:00
<context context-type="linenumber">4,5</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/fees-box/fees-box.component.html</context>
<context context-type="linenumber">27,30</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">fees-box.low-priority</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="0ba9d74c1d31a9d98829892f40334a22624564b8" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Medium priority</source>
<target>Srednje</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
Updating from transifex.
2021-07-11 22:06:14 +03:00
<context context-type="linenumber">10,11</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/fees-box/fees-box.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">34,37</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">fees-box.medium-priority</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="f80dd1511a91af4e592a538f95fa29d24907176f" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>High priority</source>
<target>Hitro</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
Updating from transifex.
2021-07-11 22:06:14 +03:00
<context context-type="linenumber">16,17</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/fees-box/fees-box.component.html</context>
Update translations from transifex.
2021-05-08 01:12:57 +04:00
<context context-type="linenumber">41,44</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">fees-box.high-priority</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="0ae5beecbbfc96bcdf4f9a637aa72687e81ef5e1" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Tx vBytes per second:</source>
<target>Tx vBajtov na sekundo:</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">5,7</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">footer.tx-vbytes-per-second</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="a5950b2ce4c3ea32de91034de8269781eb333d73" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Backend is synchronizing</source>
<target>Sinhronizacija zaledja (backend)</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">7,11</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">221,224</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">dashboard.backend-is-synchronizing</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="50904e472d4671388a20fbbb1ee9dfc0a4586fa1" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>vB/s</source>
<target>vB/s</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">11,16</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">226,232</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">vB/s</note>
<note priority="1" from="meaning">shared.vbytes-per-second</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="60cd6fa18f925b42065d8cfb1a791efdc228b4c3" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Unconfirmed</source>
<target>Nepotrjeno</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">16,18</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">189,190</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">Unconfirmed count</note>
<note priority="1" from="meaning">dashboard.unconfirmed</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="6f7832e2e8db3c4b16c41681ba334a2ab9726cc3" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Mempool size</source>
<target>Mempool velikost</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">20,21</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Mempool size</note>
<note priority="1" from="meaning">dashboard.mempool-size</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="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 #blo"/> <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>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">22,23</context>
</context-group>
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-blocks/mempool-blocks.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">32,33</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">242,243</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">shared.blocks</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="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; &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 transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">23,24</context>
</context-group>
<context-group purpose="location">
Updating from transifex.
2021-07-17 15:37:34 +03:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">243,244</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.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="65d447765db0bf3390e9b3ecce142bf34bb602a3" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Mined</source>
<target>Narudarjeno</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/latest-blocks/latest-blocks.component.html</context>
<context context-type="linenumber">11,12</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">92,93</context>
</context-group>
<note priority="1" from="description">latest-blocks.mined</note>
</trans-unit>
<trans-unit id="f4cba7faeb126346f09cc6af30124f9a343f7a28" datatype="html">
<source>Blocks</source>
<target>Bloki</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/latest-blocks/latest-blocks.component.ts</context>
<context context-type="linenumber">39</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="5d4f792f048fcaa6df5948575d7cb325c9393383" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Graphs</source>
<target>Grafi</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/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">36,39</context>
</context-group>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">51,53</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/statistics/statistics.component.ts</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">58</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">master-page.graphs</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="46ce8155c9ab953edeec97e8950b5a21e67d7c4e" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>TV view</source>
<target>TV pogled</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">54,57</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/television/television.component.ts</context>
Updating i18n from transifex.
2021-08-03 18:38:34 +03:00
<context context-type="linenumber">27</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">master-page.tvview</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="b2cb12c1680a46464cae5aa0d0d1d6914733a75d" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Fee span</source>
<target>Razpon omrežnin</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">20,21</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">mempool-block.fee-span</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="926dd4c7e830240b502eb44b6c485815f563e595" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Total fees</source>
<target>Skupaj omrežnin</target>
<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>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">mempool-block.total-fees</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="mempool-block.next.block" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Next block</source>
<target>Naslednji blok</target>
<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>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="mempool-block.stack.of.blocks" datatype="html">
<source>Stack of <x id="INTERPOLATION" equiv-text="blocksInBlock"/> mempool blocks</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.ts</context>
<context context-type="linenumber">73</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="mempool-block.block.no" datatype="html">
<source>Mempool block <x id="INTERPOLATION" equiv-text="this.mempoolBlockIndex + 1"/></source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.ts</context>
<context context-type="linenumber">75</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="2348971518300945764" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Range</source>
<target>Razpon</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-graph/mempool-graph.component.ts</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">256</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="1033261550402895380" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Sum</source>
<target>Skupno</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-graph/mempool-graph.component.ts</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">258</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="e5d8bb389c702588877f039d72178f219453a72d" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Unknown</source>
<target>Neznano</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/miner/miner.component.html</context>
<context context-type="linenumber">10</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">miner.tag.unknown-miner</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="miner-identified-by-payout" datatype="html">
<source>Identified by payout address: '<x id="PAYOUT_ADDRESS" equiv-text="vout.scriptpubkey_address"/>'</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/miner/miner.component.ts</context>
<context context-type="linenumber">42</context>
</context-group>
</trans-unit>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="miner-identified-by-coinbase" datatype="html">
<source>Identified by coinbase tag: '<x id="TAG" equiv-text="tag"/>'</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/miner/miner.component.ts</context>
<context context-type="linenumber">52</context>
</context-group>
</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>
<target>Objava transakcije</target>
<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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">156,162</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="a2fbb7745c7048af923991e08ccd6975364be90d" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Transaction Hex</source>
<target>Šestnajstiška vrednost</target>
<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>
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, višina bloka, hash ali naslov</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-form.component.html</context>
<context context-type="linenumber">4</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">search-form.searchbar-placeholder</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="7e892ba15f2c6c17e83510e273b3e10fc32ea016" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Search</source>
<target>Iskanje</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-form.component.html</context>
<context context-type="linenumber">7</context>
</context-group>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">search-form.search-title</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="dfd99c62b5b308fc5b1ad7adbbf9d526d2b31516" datatype="html">
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<source>Sponsor</source>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Sponzorstvo</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>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context context-type="linenumber">3</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>Ustvari račun</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context context-type="linenumber">49</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>Čakanje na transakcijo... </target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context context-type="linenumber">138</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>Prispevek potrjen!</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context context-type="linenumber">144</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>Hvala vam!</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/sponsor/sponsor.component.html</context>
Updated i18n from transifex
2021-06-11 10:58:54 -05:00
<context context-type="linenumber">145</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 v vBajtih (sat/vBajt)</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">6</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">statistics.memory-by-vBytes</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="5ca707824ab93066c7d9b44e1b8bf216725c2c22" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Filter</source>
<target>Filter</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
<context context-type="linenumber">40</context>
</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>Obrni</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">62</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">statistics.component-invert.title</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="dc15ec15e6206b40133f2c1b06095ce75aaee1ef" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Transaction vBytes per second (vB/s)</source>
<target>Pretočnost, vBajtov na sekundo (vB/s)</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">87</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">statistics.transaction-vbytes-per-second</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="date-base.just-now" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Just now</source>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<target>Pravkar</target>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<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>
Updating from transifex.
2021-04-26 04:05:55 +04: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>
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="time-since" datatype="html">
<source><x id="DATE" equiv-text="dateStrings.i18nYear"/> ago</source>
Updating from transifex.
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
<context context-type="linenumber">67</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
<context context-type="linenumber">68</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time-since/time-since.component.ts</context>
<context context-type="linenumber">69</context>
</context-group>
<context-group purpose="location">
<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>
Updating from transifex.
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
<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>
Updating from transifex.
2021-04-26 04:05:55 +04: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">72</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/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>
Updating from transifex.
2021-04-26 04:05:55 +04: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">77</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/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>
Updating from transifex.
2021-04-26 04:05:55 +04: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">80</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/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>
Updating from transifex.
2021-04-26 04:05:55 +04: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">82</context>
Updating from transifex.
2021-04-26 04:05:55 +04: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>
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>
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>
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="0094b97dd052620710f173e7aedf6807a1eba1f5" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>This transaction has been replaced by:</source>
<target>Ta transakcija je bila nadomeščena z:</target>
<context-group purpose="location">
<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>
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">RBF replacement</note>
<note priority="1" from="meaning">transaction.rbf.replacement</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="ef772ce5cf98a47b29175e3d46b8a9816c7990a2" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Unconfirmed</source>
<target>Nepotrjeno</target>
<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">32,39</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/transactions-list/transactions-list.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">242,246</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 unconfirmed state</note>
<note priority="1" from="meaning">transaction.unconfirmed</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="bfa87f9724434e4245b30f2bdd11d97477048cd1" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Confirmed</source>
<target>Potrjeno</target>
<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">65,66</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 Confirmed state</note>
<note priority="1" from="meaning">transaction.confirmed</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="1bc4a5de56ea48a832e32294c124009867b478d0" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>First seen</source>
<target>Prejeto</target>
<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">101,102</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 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>
<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">108,109</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 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>V nekaj urah (ali več)</target>
<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">114,117</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 ETA in several hours or more</note>
<note priority="1" from="meaning">transaction.eta.in-several-hours</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="54c58b39481f1749fce23fa8a77f616eee84d761" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Virtual size</source>
<target>Navidezna velikost</target>
<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">153,155</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">216,219</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 Virtual Size</note>
<note priority="1" from="meaning">transaction.vsize</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="3e322ffba6477484e0dd2e65650fdd70322ea6d0" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Fee rate</source>
Update i18n from transifex.
2021-06-09 13:35:07 -05:00
<target>Stopnja omrežnine</target>
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">154,158</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">389,391</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 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>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Potomec</target>
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">161,163</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">Descendant</note>
<note priority="1" from="meaning">transaction.descendant</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="8c16167a5d7c96d14ff280b09de312d18d5e2511" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Ancestor</source>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Prednik</target>
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">175,177</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 Ancestor</note>
<note priority="1" from="meaning">transaction.ancestor</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="35214e7a6aec1b0317e0fa1eb32e8caf6757b147" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Size</source>
<target>Velikost</target>
<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">212,215</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 Size</note>
<note priority="1" from="meaning">transaction.size</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="13f5a75f3e01e5924e45052d2f336eda8bac37e8" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Weight</source>
<target>Utež</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">220,223</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 Weight</note>
<note priority="1" from="meaning">transaction.weight</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="516a786e59a57efaf80e11370b4bade400f19445" datatype="html">
Update i18n strings from Transifex
2021-12-03 08:54:13 +09:00
<source>Locktime</source>
<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>Transakcije ni mogoče najti.</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>Čakanje, da se prikaže v mempool-u...</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>Omrežnina</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="071dc2ed21e40ad2199ea5dda884f48c0414a42a" 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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">386,389</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 sat</note>
<note priority="1" from="meaning">transaction.fee.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>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Efektivna stopnja omrežnine</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>
Pulled from transifex
2021-12-26 11:15:19 +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>
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>(Novo ustvarjeni kovanci)</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>
Pulled from transifex
2021-12-26 11:15:19 +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>
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-in</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<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>
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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">86,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">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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">90,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>
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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">95,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>
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 skripta</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">99,100</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>
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 skripta</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">103,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">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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">107,109</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>
<target>Skripta prejšnjega izhoda</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>
Pulled from transifex
2021-12-26 11:15:19 +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">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>
<target>Tip prejšnjega izhoda</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">116,117</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="288d096739aa2d9aae2911f072f91b3a29245509" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Load all</source>
<target>Prikaži vse</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">127,130</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">221,224</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.load-all</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="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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">146,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>
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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">199,201</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">203,206</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="3ac775768c0ab6f813c8bab0fe0e68960fc87c4d" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>data</source>
<target>podatki</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>
Pulled from transifex
2021-12-26 11:15:19 +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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.vout.scriptpubkey-type.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>
Pulled from transifex
2021-12-26 11:15:19 +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>
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/transactions-list/transactions-list.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">231,232</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">sat</note>
<note priority="1" from="meaning">shared.sat</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="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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
<target>Ta transakcija uporablja Taproot.</target>
<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>
<target>Taproot</target>
<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>Ta transakcija omogoča povečanje omrežnine, Replace-By-Fee (RBF).</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>
Update i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Ta transakcija NE omogoča povečanja omrežnine, z uporabo Replace-By-Fee (RBF).</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>Optimalno</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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
Implement i18n support in frontend using Angular + Transifex + NGINX This PR adds basic i18n support into the mempool frontend, together with a smooth workflow for developers and translators to collaborate: * Using the existing @angular/localize module, developers add i18n metadata to any frontend strings their new features or changes modify * Using the new npm script `i18n-extract-from-source`, developers extract the i18n data from source code into `src/locale/messages.xlf` * After pushing the updated `src/locale/messages.xlf` to GitHub, the Transifex service will update its database from the new source data * Using the Transifex website UI, translators can work together to translate all the mempool frontend strings into their native languages * Using the new npm script `i18n-pull-from-transifex`, developers can pull in completed translations from Transifex, and commit them into git. This flow requires an API key from Transifex, which can be obtained at https://www.transifex.com/user/settings/api/ to be used with the python script installed by `pip install transifex-client` - after preparing these, run the npm script which will ask you for the API key the first time. When downloading is complete, you can test building the frontend, and if successful, commit the new strings files into git. This PR implements a new locale selector in the footer of the homepage dashboard, and includes WIP translations for the following languages: * Czech (cs) * German (de) * Japanese (ja) * Norwegian (nn) * Spanish (es) * Swedish (sv) * Ukrainian (uk) * Persian (fa) * Portugese (pt) * Turkish (tr) * Dutch (nl) * French (fr) * Chinese (zh) * Slovenian (sl) * Korean (ko) * Polish (pl) The user-agent's `Accept-Language` header is used to automatically detect their preferred language, which can be manually overriden by the pull-down selector, which saves their preference to a cookie, which is used by nginx to serve the correct HTML bundle to the user. Remaining tasks include adding i18n metadata for strings in the Bisq and Liquid frontend code, mouseover hover tooltip strings, hard-coded og metadata inside HTML templates, and many other places. This will be done in a separate PR. When upgrading to add i18n support, mempool instance operators must take care to install the new 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>
Pull from transifex
2021-08-27 14:28:51 +09:00
<target>Omrežnina</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>
<context context-type="linenumber">33,36</context>
</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="e1139ea570985b3f114e18876f09fd7223429983" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Latest blocks</source>
<target>Najnovejši bloki</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">88,91</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.latest-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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="e6213c3f05146287cf121868d9f3d3c3ff5f9714" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>TXs</source>
<target>TXs</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/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">94,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>
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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">191,195</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.latest-blocks.transaction-count</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="46ae0bacea22bcf409534f1c314735e4983e398a" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Latest transactions</source>
<target>Najnovejše transakcije</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">117,120</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">123,124</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>Omrežnina</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">124,126</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>Razširi</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">144,145</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>Strni</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">145,151</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>Najnižja omrežnina</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">182,183</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>Prag</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">183,184</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>Velikost</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">195,196</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>
<target>L-BTC v obtoku</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">209,211</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<trans-unit id="926c571b25cca7e2a294619f145960c0cd3848b6" datatype="html">
Updating from transifex.
2021-04-26 04:05:55 +04:00
<source>Incoming transactions</source>
<target>Pretočnost</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">218,219</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.incoming-transactions</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="63da83692b85cf17e0606153029a83fd4038d6dd" datatype="html">
Updating from transifex.
2021-07-17 15:37:34 +03:00
<source>Difficulty Adjustment</source>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<target>Prilagoditev težavnosti</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">233,237</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.difficulty-adjustment</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="0912816d94f2f05a7eee8f7622670e0c6bbbce16" datatype="html">
Updating from transifex.
2021-07-17 15:37:34 +03:00
<source>Remaining</source>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<target>Preostalo</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">239,241</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">290,293</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">difficulty-box.remaining</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="5e65ce907fc0e1a1a09d4130eb8c59d00a9457ef" datatype="html">
Updating from transifex.
2021-07-17 15:37:34 +03:00
<source>Estimate</source>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<target>Ocena</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">248,249</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">297,300</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">difficulty-box.estimate</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="680d5c75b7fd8d37961083608b9fcdc4167b4c43" datatype="html">
Updating from transifex.
2021-07-27 19:51:38 +03:00
<source>Previous</source>
Pull from transifex
2021-08-27 14:28:51 +09:00
<target>Prejšnja</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">263,265</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">difficulty-box.previous</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="5db469cd0357e5f578b85a996f7e99c9e4148ff5" datatype="html">
Updating from transifex.
2021-07-17 15:37:34 +03:00
<source>Current Period</source>
Updating i18n from transifex. Moving hindi location.
2021-07-20 15:43:01 +03:00
<target>Trenutno obdobje</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>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">275,276</context>
Updating from transifex.
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
Pulled from transifex
2021-12-26 11:15:19 +04:00
<context context-type="linenumber">304,307</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">difficulty-box.current-period</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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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 i18n from transifex
2021-06-10 09:52:13 -05:00
<target>Omrežnina transakcije</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