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">
2021-12-26 11:15:19 +04:00
<file source-language="en-US" datatype="plaintext" original="ng2.template" target-language="nb">
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<body>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.alert.close" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Close</source>
2021-05-08 01:12:57 +04:00
<target>Lukk</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-12-03 08:54:13 +09:00
</context-group>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.timepicker.HH" datatype="html">
<source>HH</source>
<target>TT</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">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>
2021-02-03 15:30:38 +07:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.toast.close-aria" datatype="html">
<source>Close</source>
<target>Lukk</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">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>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ngb.datepicker.select-month" datatype="html">
<source>Select month</source>
<target>Velg måned</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">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>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="ngb.pagination.first" datatype="html">
<source>««</source>
<target>««</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-05 00:11:40 +09:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.datepicker.previous-month" datatype="html">
2021-12-03 08:54:13 +09:00
<source>Previous month</source>
<target>Forrige måned</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">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>
2020-12-09 01:17:22 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
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>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.progressbar.value" datatype="html">
<source><x id="INTERPOLATION"/></source>
2024-01-13 16:57:03 +00:00
<target><x id="INTERPOLATION"/></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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-08 11:58:43 +07:00
</context-group>
2023-11-26 17:00:34 +09:00
</trans-unit>
<trans-unit id="ngb.carousel.slide-number" datatype="html">
<source> Slide <x id="INTERPOLATION"/> of <x id="INTERPOLATION_1"/> </source>
2024-01-13 16:57:03 +00:00
<target> Lysbilde <x id="INTERPOLATION"/> av <x id="INTERPOLATION_1"/></target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-08 11:58:43 +07:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">Currently selected slide number read by screen reader</note>
2021-01-21 12:39:33 +09:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.timepicker.hours" datatype="html">
<source>Hours</source>
<target>Timer</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.pagination.previous" datatype="html">
2021-04-26 04:05:55 +04:00
<source>«</source>
2021-05-08 01:12:57 +04:00
<target>«</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
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>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.carousel.previous" datatype="html">
<source>Previous</source>
<target>Forrige</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">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>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.timepicker.MM" datatype="html">
<source>MM</source>
<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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-08 11:58:43 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.pagination.next" datatype="html">
<source>»</source>
<target>»</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-08 11:58:43 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.datepicker.select-year" datatype="html">
<source>Select year</source>
<target>Velg år</target>
<context-group purpose="location">
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
</context-group>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-08 11:58:43 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.datepicker.next-month" datatype="html">
<source>Next month</source>
<target>Neste måned</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">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>
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">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>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.carousel.next" datatype="html">
<source>Next</source>
<target>Neste</target>
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-04-26 05:37:03 +09:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.timepicker.minutes" datatype="html">
<source>Minutes</source>
<target>Minutter</target>
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-04 23:03:17 +09:00
</context-group>
2021-02-03 15:30:38 +07:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.pagination.last" datatype="html">
<source>»»</source>
<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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">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>
2021-02-03 15:30:38 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ngb.pagination.first-aria" datatype="html">
<source>First</source>
<target>Første</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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-08 11:58:43 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ngb.timepicker.increment-hours" datatype="html">
<source>Increment hours</source>
<target>Øk timer</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2020-12-08 11:58:43 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ngb.pagination.previous-aria" datatype="html">
<source>Previous</source>
<target>Forrige</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">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>
2021-04-26 04:05:55 +04:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.decrement-hours" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Decrement hours</source>
2021-05-08 01:12:57 +04:00
<target>Reduser timer</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
</context-group>
</trans-unit>
<trans-unit id="ngb.pagination.next-aria" datatype="html">
<source>Next</source>
<target>Neste</target>
<context-group purpose="location">
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-02-03 15:30:38 +07:00
</context-group>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.increment-minutes" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Increment minutes</source>
2021-05-08 01:12:57 +04:00
<target>Øk minutter</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
</context-group>
</trans-unit>
<trans-unit id="ngb.pagination.last-aria" datatype="html">
<source>Last</source>
<target>Siste</target>
<context-group purpose="location">
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.decrement-minutes" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Decrement minutes</source>
2021-05-08 01:12:57 +04:00
<target>Reduser minutter</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-02-03 15:30:38 +07:00
</context-group>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.SS" datatype="html">
2021-04-26 04:05:55 +04:00
<source>SS</source>
2021-05-08 01:12:57 +04:00
<target>SS</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-04-26 05:37:03 +09:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.seconds" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Seconds</source>
2021-05-08 01:12:57 +04:00
<target>Sekunder</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-02-03 15:30:38 +07:00
</context-group>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.increment-seconds" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Increment seconds</source>
2021-05-08 01:12:57 +04:00
<target>Øk sekunder</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="ngb.timepicker.decrement-seconds" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Decrement seconds</source>
2021-05-08 01:12:57 +04:00
<target>Reduser sekunder</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="ngb.timepicker.PM" datatype="html">
<source><x id="INTERPOLATION"/></source>
2022-06-08 00:44:04 +04:00
<target><x id="INTERPOLATION"/></target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">node_modules/src/ngb-config.ts</context>
<context context-type="linenumber">13</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-04-26 05:37:03 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="9bada74bc2b36480a6db8734d56a2b89135de590" datatype="html">
<source>Become a Community Sponsor</source>
<target>Bli en samfunnssponsor</target>
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about-sponsors.component.html</context>
<context context-type="linenumber">4</context>
2021-02-03 15:30:38 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.community-sponsor-button</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="bef4c03ebfa29b890665fbcf6bf097b9ae29a91e" datatype="html">
<source>Become an Enterprise Sponsor</source>
<target>Bli en bedriftssponsor</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about-sponsors.component.html</context>
<context context-type="linenumber">11</context>
2021-02-03 15:30:38 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.enterprise-sponsor-button</note>
</trans-unit>
<trans-unit id="4b137ec8bf73a47063740b75c0c40d5fd3c48015" datatype="html">
<source>The Mempool Open Source Project</source>
<target>Åpen kildekode-prosjektet The Mempool</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">13</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.about-the-project</note>
</trans-unit>
<trans-unit id="8a4411dcb4da0aa489ec367bf2a3ec289e07a86e" datatype="html">
<source>Our mempool and blockchain explorer for the Bitcoin community, focusing on the transaction fee market and multi-layer ecosystem, completely self-hosted without any trusted third-parties.</source>
<target>Vår mempool- og blokkkjede-utforsker for Bitcoin-samfunnet, med fokus på transaksjonsgebyrmarkedet og flerlagsøkosystemet, fullstendig self-hosted uten tredjeparter.</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">14</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="a24b1c6a9c4334ba204e4cec2dd9f32ea33d043f" datatype="html">
<source>Enterprise Sponsors 🚀</source>
<target>Bedriftssponsorer 🚀</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">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>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.sponsors.enterprise.withRocket</note>
</trans-unit>
<trans-unit id="299789f4d4817ccf915f6a5b0e48c093b646b079" datatype="html">
<source>Whale Sponsors</source>
<target>Hvalsponsorer</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">187</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.sponsors.withHeart</note>
</trans-unit>
<trans-unit id="2dca632c813555d7153785d4b6d25cc0f04d6bcd" datatype="html">
<source>Chad Sponsors</source>
<target>Chadsponsorer</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">200</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.sponsors.withHeart</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="0a441237b27eaeacbeba376cabd33921fa4bb2d6" datatype="html">
<source>OG Sponsors ❤️</source>
<target>OG Sponsorer ❤️</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">213</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.sponsors.withHeart</note>
</trans-unit>
<trans-unit id="1405c5f1a9834338ff13442c550927ab7144fdc8" datatype="html">
<source>Community Integrations</source>
<target>Sammfunnsintegrasjoner</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">224</context>
2020-12-08 11:58:43 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.community-integrations</note>
</trans-unit>
<trans-unit id="020cce975a5d7e0cc0f4578903358459d693e4bb" datatype="html">
<source>Community Alliances</source>
<target>Samfunnsallianser</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">338</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.alliances</note>
</trans-unit>
<trans-unit id="d5a535ddb26ae8cb056325715af27bb1b4008c14" datatype="html">
<source>Project Translators</source>
<target>Oversettere</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">354</context>
2020-12-08 11:58:43 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.translators</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="2dd9b8a8997a6b57413ca3cd32dd38cef9fa39c2" datatype="html">
<source>Project Contributors</source>
<target>Bidragsytere til prosjektet</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">368</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.contributors</note>
</trans-unit>
<trans-unit id="3d395b07b1f87656ed773adcbb3daf8e00c08779" datatype="html">
<source>Project Members</source>
<target>Prosjektmedlemmer</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">380</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.project_members</note>
</trans-unit>
<trans-unit id="d177262e3a43b2a7221183812daf0ada97659436" datatype="html">
<source>Project Maintainers</source>
<target>Prosjektvedlikeholdere</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.html</context>
<context context-type="linenumber">393</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">about.maintainers</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="004b222ff9ef9dd4771b777950ca1d0e4cd4348a" datatype="html">
<source>About</source>
<target>Om</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.ts</context>
<context context-type="linenumber">49</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">84</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">96</context>
2021-01-21 12:39:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="meta.description.about" datatype="html">
<source>Learn more about The Mempool Open Source Project®: enterprise sponsors, individual sponsors, integrations, who contributes, FOSS licensing, and more.</source>
<target>Lær mer om The Mempool Open Source Project®: bedriftssponsorer, individuelle sponsorer, integrasjoner, hvem som bidrar, FOSS-lisensiering og mer.</target>
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/about/about.component.ts</context>
<context context-type="linenumber">50</context>
2021-01-21 12:39:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="83b8b9dd1ed416447cf8438460a37b0ddeb2677c" datatype="html">
<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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-fee-graph.component.html</context>
<context context-type="linenumber">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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">35</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">43</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">43</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<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>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction-preview.component.html</context>
<context context-type="linenumber">24</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">588</context>
2020-12-08 11:58:43 +07:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">304</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">sat</note>
<note priority="1" from="meaning">shared.sat</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-05 16:46:23 +09:00
<trans-unit id="7159011509695804248" datatype="html">
<source>maximum</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-fee-graph.component.ts</context>
<context context-type="linenumber">55</context>
</context-group>
</trans-unit>
<trans-unit id="bdf0e930eb22431140a2eaeacd809cc5f8ebd38c" datatype="html">
<source>Next Block</source>
<target>Neste blokk</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-fee-graph.component.ts</context>
<context context-type="linenumber">66</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">12</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">28</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.ts</context>
<context context-type="linenumber">87</context>
</context-group>
</trans-unit>
<trans-unit id="f24773075af97666c0feca0e883c2585712fe597" datatype="html">
<source>Your transaction</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">35</context>
</context-group>
<note priority="1" from="description">accelerator.your-transaction</note>
</trans-unit>
<trans-unit id="bee6b649ee82d9a7cde233070b665eec7c531b1d" datatype="html">
<source>Plus <x id="INTERPOLATION" equiv-text="{{ estimate.txSummary.ancestorCount - 1 }}"/> unconfirmed ancestor(s)</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">39</context>
</context-group>
<note priority="1" from="description">accelerator.plus-unconfirmed-ancestors</note>
</trans-unit>
<trans-unit id="54c58b39481f1749fce23fa8a77f616eee84d761" datatype="html">
<source>Virtual size</source>
<target>Virtuell størrelse</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">44</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">59</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<context context-type="linenumber">25</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">103</context>
2024-04-05 16:46:23 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">231</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">Transaction Virtual Size</note>
<note priority="1" from="meaning">transaction.vsize</note>
</trans-unit>
2024-04-09 16:58:02 +09:00
<trans-unit id="df89e157bacb4ab32e6ec725bf1eb176dc15201e" datatype="html">
<source>Size in vbytes of this transaction (including unconfirmed ancestors)</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">49</context>
</context-group>
<note priority="1" from="description">accelerator.transaction-vbytes-size-description</note>
</trans-unit>
2024-04-05 16:46:23 +09:00
<trans-unit id="adbeb446bf941afda4d4a923b5e4ce0cf4a1c1b8" datatype="html">
<source>In-band fees</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">53</context>
</context-group>
<note priority="1" from="description">accelerator.in-band-fees</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="e4b2d9e6a2ab9e6ca34027ec03beaac42b7badd4" datatype="html">
<source>sats</source>
<target>sats</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">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>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">78</context>
2020-12-08 11:58:43 +07:00
</context-group>
2020-12-09 01:17:22 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">112</context>
2020-12-09 01:17:22 +07:00
</context-group>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">134</context>
2020-12-05 00:11:40 +09:00
</context-group>
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">153</context>
2021-04-26 05:37:03 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">165</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">184</context>
2022-05-19 20:12:21 +04:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">204</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">227</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">249</context>
2022-10-17 16:21:29 +04:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/calculator/calculator.component.html</context>
<context context-type="linenumber">29</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/calculator/calculator.component.html</context>
<context context-type="linenumber">44</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
<context context-type="linenumber">63</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
<context context-type="linenumber">87</context>
2021-04-26 05:37:03 +09:00
</context-group>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
<context context-type="linenumber">17</context>
2024-01-22 21:30:03 +07:00
</context-group>
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
<context context-type="linenumber">63</context>
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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/group/group-preview.component.html</context>
<context context-type="linenumber">34</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/group/group.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>
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/group/group.component.html</context>
<context context-type="linenumber">83</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/justice-list/justice-list.component.html</context>
<context context-type="linenumber">28</context>
2021-01-21 12:39:33 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.html</context>
<context context-type="linenumber">50</context>
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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
<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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.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>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
<context context-type="linenumber">23</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
<context context-type="linenumber">79</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.sats</note>
</trans-unit>
2024-04-09 16:58:02 +09:00
<trans-unit id="fad137784196a8fdc10588e27ed5d8ae95fe4e79" datatype="html">
<source>Fees already paid by this transaction (including unconfirmed ancestors)</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">60</context>
</context-group>
<note priority="1" from="description">accelerator.fees-already-paid-description</note>
</trans-unit>
2024-04-05 16:46:23 +09:00
<trans-unit id="8611a038eb243bbed95bf5ff49af4129f22dc55a" datatype="html">
<source>How much more are you willing to pay?</source>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">69</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.pay-how-much</note>
</trans-unit>
<trans-unit id="4487eb902b70d33b4bb7a0828b66afec3a96fc18" datatype="html">
<source>Choose the maximum extra transaction fee you're willing to pay to get into the next block.</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">72</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-05 16:46:23 +09:00
<note priority="1" from="description">accelerator.transaction-fee-description</note>
</trans-unit>
2024-04-09 16:58:02 +09:00
<trans-unit id="012fac6ebe9d7a2cf3edc1ec394f91eb43bd26a3" datatype="html">
<source>Boost rate</source>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">98</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-09 16:58:02 +09:00
<note priority="1" from="description">accelerator.boost-rate</note>
2024-04-05 16:46:23 +09:00
</trans-unit>
<trans-unit id="d2eb45d1cd8cd146b7cb0223ab97a4b03b614060" datatype="html">
<source>sat/vB</source>
<target>sat/vB</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">102</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">124</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/shared/components/fee-rate/fee-rate.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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/shared/components/fee-rate/fee-rate.component.html</context>
<context context-type="linenumber">7</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">sat/vB</note>
<note priority="1" from="meaning">shared.sat-vbyte</note>
</trans-unit>
2024-04-09 16:58:02 +09:00
<trans-unit id="ece1a4cb6cadf75d497b433703265a230679f5a0" datatype="html">
<source>Boost fee</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">106</context>
</context-group>
<note priority="1" from="description">accelerator.estimated-extra-fee-required</note>
</trans-unit>
<trans-unit id="0b537472d5f7518ed2c2c2b747997b0447ec5ee8" datatype="html">
<source>Next block market rate</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">120</context>
</context-group>
<note priority="1" from="description">accelerator.next-block-rate</note>
</trans-unit>
2024-04-05 16:46:23 +09:00
<trans-unit id="c2836a2964adf9e369ee0a1ce67f991cf2aa435d" datatype="html">
<source>Estimated extra fee required</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">128</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.estimated-extra-fee-required</note>
</trans-unit>
<trans-unit id="26e50fa97db4eecde26ff892d725e61ca9201c48" datatype="html">
<source>Mempool Accelerator™ fees</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">143</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.mempool-accelerator-fees</note>
</trans-unit>
<trans-unit id="1ec82428244c76064090ea5a55827e3fada82306" datatype="html">
<source>Accelerator Service Fee</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">147</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.service-fee</note>
</trans-unit>
<trans-unit id="7d07b80b17dfab3582807759420b8d723c9e4414" datatype="html">
<source>Transaction Size Surcharge</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">159</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.tx-size-surcharge</note>
</trans-unit>
2024-04-09 16:58:02 +09:00
<trans-unit id="36b3f41abf6308a0eb7decf26e710d871865f1eb" datatype="html">
<source>Total cost</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
<context context-type="linenumber">176</context>
</context-group>
<note priority="1" from="description">accelerator.total-cost</note>
</trans-unit>
2024-04-05 16:46:23 +09:00
<trans-unit id="004732b44df582a2d24e2abbd3f46bc42ae8c546" datatype="html">
<source>Estimated acceleration cost</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">196</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.estimated-cost</note>
</trans-unit>
<trans-unit id="c9ec95585f57bd87212693db7cb00d9ed70d49b1" datatype="html">
<source>Maximum acceleration cost</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">219</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.maximum-cost</note>
</trans-unit>
<trans-unit id="f3ff11006f77909b9fca2e0fda0a72b097cd76de" datatype="html">
<source>Available balance</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">244</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.available-balance</note>
</trans-unit>
<trans-unit id="ba4f24bf9bf3dc4db3d6bc1b8b63339295f0b806" datatype="html">
<source>Sign In</source>
<target>Logg inn</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">263</context>
2024-04-05 16:46:23 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/menu/menu.component.html</context>
<context context-type="linenumber">21</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">29</context>
2024-04-05 16:46:23 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">37</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">shared.sign-in</note>
</trans-unit>
<trans-unit id="2504ca478a61c5e53f9ed55e9aeb3e8f2d01b3eb" datatype="html">
<source>Accelerate on mempool.space</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">272</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.accelerate-on-mempoolspace</note>
</trans-unit>
<trans-unit id="913e89d2d1ae354079cccf48b3d3f4ebf2e74080" datatype="html">
<source>Accelerate</source>
<target>Akselerer</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">284</context>
2024-04-05 16:46:23 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">81</context>
2024-04-05 16:46:23 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">541</context>
2024-04-05 16:46:23 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">550</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">Accelerate button label</note>
<note priority="1" from="meaning">transaction.accelerate</note>
</trans-unit>
<trans-unit id="2bec172478fbbbe6536a662f5d4d3d711c208b09" datatype="html">
<source>If your tx is accelerated to ~<x id="INTERPOLATION" equiv-text="{{ i | number : '1.0-0' }}"/> sat/vB</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/accelerate-preview/accelerate-preview.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">310</context>
2024-04-05 16:46:23 +09:00
</context-group>
<note priority="1" from="description">accelerator.accelerated-to-description</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="bcf34abc2d9ed8f45a2f65dd464c46694e9a181e" datatype="html">
<source>Acceleration Fees</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-fees-graph/acceleration-fees-graph.component.html</context>
<context context-type="linenumber">6</context>
2021-12-03 08:54:13 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-fees-graph/acceleration-fees-graph.component.ts</context>
<context context-type="linenumber">75</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.acceleration-fees</note>
</trans-unit>
<trans-unit id="7920806087360513675" datatype="html">
<source>No accelerated transaction for this timeframe</source>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-fees-graph/acceleration-fees-graph.component.ts</context>
<context context-type="linenumber">121</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="4793828002882320882" datatype="html">
<source>At block: <x id="PH" equiv-text="ticks[0].data[2]"/></source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-fees-graph/acceleration-fees-graph.component.ts</context>
<context context-type="linenumber">165</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.ts</context>
<context context-type="linenumber">255</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-health-graph/block-health-graph.component.ts</context>
<context context-type="linenumber">143</context>
2022-10-17 16:21:29 +04: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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">168</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="8918254921747459635" datatype="html">
<source>Around block: <x id="PH" equiv-text="ticks[0].data[2]"/></source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-fees-graph/acceleration-fees-graph.component.ts</context>
<context context-type="linenumber">167</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.ts</context>
<context context-type="linenumber">257</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-health-graph/block-health-graph.component.ts</context>
<context context-type="linenumber">145</context>
2020-12-04 23:03:17 +09:00
</context-group>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">170</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="5238405b3e8e1b72d2732f0ecbd83be35b98cd5d" datatype="html">
<source>Requests</source>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-stats/acceleration-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">4</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-stats/acceleration-stats.component.html</context>
<context context-type="linenumber">32</context>
2021-12-03 08:54:13 +09:00
</context-group>
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/pending-stats/pending-stats.component.html</context>
<context context-type="linenumber">4</context>
2020-12-04 23:03:17 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/pending-stats/pending-stats.component.html</context>
<context context-type="linenumber">32</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.requests</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="25fbf6e80a945703c906a5a7d8c92e8729c7ab21" datatype="html">
<source>accelerated</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-stats/acceleration-stats.component.html</context>
<context context-type="linenumber">7</context>
2020-12-04 23:03:17 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.total-accelerated</note>
2020-12-04 23:03:17 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="bdb8bbb38e4ca3c73e19dc4167fbe4aec316f818" datatype="html">
<source>Total Bid Boost</source>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-stats/acceleration-stats.component.html</context>
<context context-type="linenumber">11</context>
2020-12-05 00:11:40 +09:00
</context-group>
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-stats/acceleration-stats.component.html</context>
<context context-type="linenumber">39</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/acceleration/accelerator-dashboard/accelerator-dashboard.component.html</context>
<context context-type="linenumber">56</context>
2021-05-11 15:31:42 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.total-boost</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="53475bdf4a94f0103f33211d02102859e9a8fe3e" datatype="html">
<source>BTC</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-stats/acceleration-stats.component.html</context>
<context context-type="linenumber">13</context>
2021-05-11 15:31:42 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/pending-stats/pending-stats.component.html</context>
<context context-type="linenumber">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>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-stats/recent-pegs-stats.component.html</context>
<context context-type="linenumber">12</context>
2021-05-11 15:31:42 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-stats/recent-pegs-stats.component.html</context>
<context context-type="linenumber">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>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">BTC</note>
<note priority="1" from="meaning">shared.btc</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="599dec71fe5c264d05012c7f64080d6347c1dc49" datatype="html">
<source>Success Rate</source>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-stats/acceleration-stats.component.html</context>
<context context-type="linenumber">20</context>
2021-05-11 15:31:42 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-stats/acceleration-stats.component.html</context>
<context context-type="linenumber">46</context>
2020-12-08 11:58:43 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.success-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>
2024-04-03 18:47:16 +09:00
<trans-unit id="1c9007410ce2f5175124a37eea71022a752833d3" datatype="html">
<source>mined</source>
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/acceleration-stats/acceleration-stats.component.html</context>
<context context-type="linenumber">23</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.mined-next-block</note>
</trans-unit>
<trans-unit id="02573b6980a2d611b4361a2595a4447e390058cd" datatype="html">
<source>Accelerations</source>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">2</context>
2020-12-08 11:58:43 +07:00
</context-group>
2024-04-05 16:46:23 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/acceleration/accelerator-dashboard/accelerator-dashboard.component.html</context>
<context context-type="linenumber">41</context>
</context-group>
<note priority="1" from="description">accelerator.accelerations</note>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="94c248797dd2b6af49068cb49c3b4bc26bec6a16" datatype="html">
<source>TXID</source>
<target>TXID</target>
2021-06-10 09:52:13 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">10</context>
2021-06-10 09:52:13 -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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">102</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">71</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">134</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.latest-transactions.txid</note>
2021-02-03 15:30:38 +07:00
</trans-unit>
2024-04-09 16:58:02 +09:00
<trans-unit id="3e322ffba6477484e0dd2e65650fdd70322ea6d0" datatype="html">
<source>Fee rate</source>
<target>Avgift</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">12</context>
2021-01-21 12:39:33 +09:00
</context-group>
2024-04-09 16:58:02 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">46</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">105</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">598</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
<context context-type="linenumber">18</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
<context context-type="linenumber">31</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
<context context-type="linenumber">41</context>
</context-group>
<note priority="1" from="description">Transaction fee rate</note>
<note priority="1" from="meaning">transaction.fee-rate</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-09 16:58:02 +09:00
<trans-unit id="9310d4be621ac60b19a4d73258b25f2b411971e7" datatype="html">
<source>Bid</source>
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">13</context>
2021-05-11 15:31:42 +04:00
</context-group>
2024-04-09 16:58:02 +09:00
<note priority="1" from="description">accelerator.bid</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="dac1da772be9797ce39c7364d0e01373e4955ed1" datatype="html">
<source>Requested</source>
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">14</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.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>
2024-04-09 16:58:02 +09:00
<note priority="1" from="description">accelerator.requested</note>
2021-02-03 15:30:38 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="57cde27765d527a0d9195212fa5a7ce06408c827" datatype="html">
<source>Bid Boost</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">17</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Bid Boost</note>
<note priority="1" from="meaning">transaction.bid-boost</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="7f5d0c10614e8a34f0e2dad33a0568277c50cf69" datatype="html">
<source>Block</source>
<target>Blokk</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">18</context>
2023-11-26 17:00:34 +09:00
</context-group>
2021-05-11 15:31:42 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.html</context>
<context context-type="linenumber">3</context>
2021-05-11 15:31:42 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">9</context>
2021-05-11 15:31:42 +04:00
</context-group>
2024-04-09 16:58:02 +09:00
<note priority="1" from="description">shared.block-title</note>
2021-05-11 15:31:42 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="aa28c3afcb8b1a556fc1e1842e48a57f24fd643f" datatype="html">
<source>Status</source>
<target>Status</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">19</context>
2024-01-22 21:30:03 +07:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<context context-type="linenumber">33</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">74</context>
2022-05-19 20:12:21 +04:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2022-10-17 16:21:29 +04:00
<context context-type="linenumber">40</context>
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction Status</note>
<note priority="1" from="meaning">transaction.status</note>
2021-06-09 13:35:07 -05:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="e6a27066251ca1e04c5be86ad758380856df2506" datatype="html">
<source>Pending</source>
2021-06-09 13:35:07 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">53</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.pending</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>
2024-04-03 18:47:16 +09:00
<trans-unit id="9362dc86738f282259d3ef3789b7824dbfd19202" datatype="html">
<source>Completed <x id="START_TAG_SPAN" ctype="x-span" equiv-text="<span *ngIf="acceleration.status === 'completed_provisional'">"/>🔄<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="</span>"/></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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">54,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>
2021-02-03 15:30:38 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="7131ba3d0dee65d36dc5de582917a4fc826e73d0" datatype="html">
<source>Failed <x id="START_TAG_SPAN" ctype="x-span" equiv-text="<span *ngIf="acceleration.status === 'failed_provisional'">"/>🔄<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="</span>"/></source>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">55,56</context>
2021-01-21 12:39:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.canceled</note>
2021-02-03 15:30:38 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="805f27b06c3c2b919234b3bcf3d0f5abe445d922" datatype="html">
<source>There are no active accelerations</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">96</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerations.no-accelerations</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="0c2d0d4986aed63c43d3d39a37d5039a55ddf9d0" datatype="html">
<source>There are no recent accelerations</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerations-list/accelerations-list.component.html</context>
<context context-type="linenumber">97</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerations.no-accelerations</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="e51c45c636401f8bb3bd8cfd1ed5a3c9810c5fa8" datatype="html">
<source>Active Accelerations</source>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerator-dashboard/accelerator-dashboard.component.html</context>
<context context-type="linenumber">10</context>
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerator-dashboard/accelerator-dashboard.component.html</context>
<context context-type="linenumber">74</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.pending-accelerations</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="41a9456b7e195dfc4df3d67b09940bda160882af" datatype="html">
<source>Acceleration stats</source>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerator-dashboard/accelerator-dashboard.component.html</context>
<context context-type="linenumber">24</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.acceleration-stats</note>
</trans-unit>
<trans-unit id="12ad90f635ec3df50b367b133c213b27912325cc" datatype="html">
<source>(3 months)</source>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerator-dashboard/accelerator-dashboard.component.html</context>
<context context-type="linenumber">25</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.3-months</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="97ff5554c708164d58b14e45072acbcbf9f4d137" datatype="html">
<source>View more »</source>
<target>Se mer »</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerator-dashboard/accelerator-dashboard.component.html</context>
<context context-type="linenumber">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>
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">34</context>
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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">46</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/lightning-dashboard/lightning-dashboard.component.html</context>
<context context-type="linenumber">42</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/lightning-dashboard/lightning-dashboard.component.html</context>
<context context-type="linenumber">56</context>
2020-12-08 11:58:43 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.view-more</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="f0ae1220633178276128371f3965fb53d63581d4" datatype="html">
<source>Recent Accelerations</source>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerator-dashboard/accelerator-dashboard.component.html</context>
<context context-type="linenumber">86</context>
2020-12-08 11:58:43 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.recent-accelerations</note>
</trans-unit>
<trans-unit id="6b867dc61c6a92f3229f1950f9f2d414790cce95" datatype="html">
<source>Accelerator Dashboard</source>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/accelerator-dashboard/accelerator-dashboard.component.ts</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">54</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">75</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="3590f5c3ef2810f637316edb8aaa86b8e907f152" datatype="html">
<source>pending</source>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/pending-stats/pending-stats.component.html</context>
<context context-type="linenumber">7</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.total-pending</note>
</trans-unit>
<trans-unit id="841f2a74ae5095e6e37f5749f3cc1851cf36a420" datatype="html">
<source>Avg Max Bid</source>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/pending-stats/pending-stats.component.html</context>
<context context-type="linenumber">11</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/pending-stats/pending-stats.component.html</context>
<context context-type="linenumber">39</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.average-max-bid</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>
2024-04-03 18:47:16 +09:00
<trans-unit id="16fedee43f919b6a0992f32aeec5d6938e8d6b76" datatype="html">
<source>Total Vsize</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/pending-stats/pending-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>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/pending-stats/pending-stats.component.html</context>
<context context-type="linenumber">46</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.total-vsize</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="b5439bbae31f512a4ef3c3e2aa41f013f1dc120a" datatype="html">
<source> of next 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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/acceleration/pending-stats/pending-stats.component.html</context>
<context context-type="linenumber">23</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">accelerator.percent-of-next-block</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="7b2e0a6bafe35c5cd10e55846d89397df0bff128" datatype="html">
<source>Balance History</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address-graph/address-graph.component.html</context>
<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>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">address.balance-history</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>
2024-04-09 16:58:02 +09:00
<trans-unit id="7e69426bd97a606d8ae6026762858e6e7c86a1fd" datatype="html">
<source>Balance</source>
<target>Balanse</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address-graph/address-graph.component.ts</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">164</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/address/address-preview.component.html</context>
<context context-type="linenumber">31</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">39</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-addresses-list/federation-addresses-list.component.html</context>
<context context-type="linenumber">9</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="b45214d1bf328d07f0aea939dfc197f5c59f421b" datatype="html">
<source>Balances</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address-group/address-group.component.html</context>
2023-11-26 17:00:34 +09:00
<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>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">addresses.balance</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>
2024-04-03 18:47:16 +09:00
<trans-unit id="d04d5b5d13ac9acf9750f1807f0227eeee98b247" datatype="html">
<source>Total</source>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address-group/address-group.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">9</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">addresses.total</note>
</trans-unit>
<trans-unit id="address-label.multisig" datatype="html">
<source>Multisig <x id="multisigM" equiv-text="ms.m"/> of <x id="multisigN" equiv-text="ms.n"/></source>
<target>Multisignatur <x id="multisigM" equiv-text="ms.m"/> av <x id="multisigN" equiv-text="ms.n"/></target>
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address-labels/address-labels.component.ts</context>
<context context-type="linenumber">107</context>
2020-12-04 23:03:17 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="729754dd19eb9ce0670b0aeb5a6ae60574c2c563" datatype="html">
<source>Address</source>
<target>Adresse</target>
2022-07-08 15:07:38 +00:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address-preview.component.html</context>
<context context-type="linenumber">3</context>
2022-07-08 15:07:38 +00:00
</context-group>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">3</context>
2020-12-08 11:58:43 +07:00
</context-group>
2021-02-15 00:15:04 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-addresses-list/federation-addresses-list.component.html</context>
<context context-type="linenumber">8</context>
2021-02-15 00:15:04 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">9</context>
2021-02-15 00:15:04 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.address</note>
2021-02-15 00:15:04 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="04ffd930e7a2dc086c952a3a51b42c836bf21cc1" datatype="html">
<source>Unconfidential</source>
<target>Ukonfidensielt</target>
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address-preview.component.html</context>
2021-04-26 04:05:55 +04:00
<context context-type="linenumber">15</context>
2020-12-04 23:03:17 +09:00
</context-group>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">21</context>
2021-01-21 12:39:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">address.unconfidential</note>
2021-01-21 12:39:33 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="a9b87c3aa4731edee661c8287ef3aab71799c0b8" datatype="html">
<source>Total received</source>
<target>Totalt mottatt</target>
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address-preview.component.html</context>
<context context-type="linenumber">22</context>
2020-12-08 11:58:43 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">30</context>
2020-12-08 11:58:43 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">address.total-received</note>
</trans-unit>
<trans-unit id="f149942f271231be52f55589398967093382d96d" datatype="html">
<source>Total sent</source>
<target>Totalt sendt</target>
2020-12-04 23:03:17 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address-preview.component.html</context>
<context context-type="linenumber">26</context>
2020-12-04 23:03:17 +09:00
</context-group>
2020-12-05 02:39:50 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">34</context>
2020-12-04 23:03:17 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">address.total-sent</note>
2021-02-03 15:30:38 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="add4cd82e3e38a3110fe67b3c7df56e9602644ee" datatype="html">
<source>Transactions</source>
<target>Transaksjoner</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address-preview.component.html</context>
<context context-type="linenumber">35</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">419</context>
2021-12-03 08:54:13 +09:00
</context-group>
2022-06-05 22:39:36 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">451</context>
2022-06-05 22:39:36 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">475</context>
2023-11-26 17:00:34 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">24</context>
2022-10-17 16:21:29 +04:00
</context-group>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/clock/clock.component.html</context>
<context context-type="linenumber">59</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">32</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">address.transactions</note>
2021-12-03 08:54:13 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="fb5b5aec9a6add4912de64b7bbc55884cc7f8e3a" datatype="html">
<source>Unspent TXOs</source>
<target>Ubrukte TXOer</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address-preview.component.html</context>
<context context-type="linenumber">39</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">address.unspent_txos</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="30751732ff4b8f6ddb2a906e0173072ac29d412a" datatype="html">
<source>Confidential</source>
<target>Konfidensielt</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address-preview.component.html</context>
<context context-type="linenumber">55</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">167</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/amount/amount.component.html</context>
<context context-type="linenumber">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>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset-circulation/asset-circulation.component.html</context>
<context context-type="linenumber">2</context>
2021-04-26 04:05:55 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">158</context>
2023-11-26 17:00:34 +09:00
</context-group>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction-preview.component.html</context>
<context context-type="linenumber">18</context>
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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">313</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">98</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">146</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.confidential</note>
2021-01-21 12:39:33 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="address.component.browser-title" datatype="html">
<source>Address: <x id="INTERPOLATION" equiv-text="this.addressString"/></source>
<target>Adresse: <x id="INTERPOLATION" equiv-text="this.addressString"/></target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address-preview.component.ts</context>
<context context-type="linenumber">71</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.ts</context>
<context context-type="linenumber">78</context>
2020-12-05 00:11:40 +09:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.bitcoin.address" datatype="html">
<source>See mempool transactions, confirmed transactions, balance, and more for <x id="PH" equiv-text="this.stateService.network==='liquid'||this.stateService.network==='liquidtestnet'?'Liquid':'Bitcoin'"/><x id="PH_1" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> address <x id="INTERPOLATION" equiv-text="this.addressString"/>.</source>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address-preview.component.ts</context>
<context context-type="linenumber">72</context>
2021-02-03 15:30:38 +07:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.ts</context>
<context context-type="linenumber">79</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="714e34125b3343df73f19ec800b43be95217d5d4" datatype="html">
<source><x id="INTERPOLATION" equiv-text="of {{ txCount | number }} transaction</ng-templ"/> of <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/> transaction</source>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">69</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">X of X Address Transaction</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="0f6ada0cfb60aefd8f77f8a22349850ce186d666" datatype="html">
<source><x id="INTERPOLATION" equiv-text="of {{ txCount | number }} transactions</ng-template>"/> of <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/> transactions</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">70</context>
2021-02-03 15:30:38 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">X of X Address Transactions (Plural)</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="f094f67fbe759cdbeb2ea14455634bbe5cc6375d" datatype="html">
<source>Error loading address data.</source>
<target>Lasting av adressedata feilet.</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">140</context>
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
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">157</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">address.error.loading-address-data</note>
</trans-unit>
<trans-unit id="49cef95661d86f4341788ce40068d58801adc6e6" datatype="html">
<source><x id="START_ITALIC_TEXT" ctype="x-i" equiv-text="There many transactions on this address, more than your backend can handle. See more on <a href="/d"/>There many transactions on this address, more than your backend can handle. See more on <x id="START_LINK" ctype="x-a" equiv-text="<a href="/docs/faq#address-lookup-issues">"/>setting up a stronger backend<x id="CLOSE_LINK" ctype="x-a" equiv-text="</a>"/>.<x id="CLOSE_ITALIC_TEXT" ctype="x-i" equiv-text="</i>"/><x id="LINE_BREAK" ctype="lb"/><x id="LINE_BREAK" ctype="lb"/> Consider viewing this address on the official Mempool website instead: </source>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/address/address.component.html</context>
<context context-type="linenumber">143,146</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Electrum server limit exceeded error</note>
</trans-unit>
<trans-unit id="f8c91b77ad53ccd0f6adb4a6ea3a0f5c3329688b" datatype="html">
<source>Asset</source>
<target>Ressurs</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">3</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Liquid Asset page title</note>
<note priority="1" from="meaning">asset</note>
</trans-unit>
<trans-unit id="cff1428d10d59d14e45edec3c735a27b5482db59" datatype="html">
<source>Name</source>
<target>Navn</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">21</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">4</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">31</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
<context context-type="linenumber">138</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.html</context>
<context context-type="linenumber">28</context>
2021-02-15 00:15:04 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Asset name header</note>
2021-02-15 00:15:04 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="8f301d45550dcb7dec91cc1fdc1f65f13c6a2892" datatype="html">
<source>Precision</source>
<target>Presisjon</target>
2021-02-15 00:15:04 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">25</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Liquid Asset precision</note>
<note priority="1" from="meaning">asset.precision</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>
2024-04-03 18:47:16 +09:00
<trans-unit id="80475fc1bf22ded644db203c43a075f623c527d4" datatype="html">
<source>Issuer</source>
<target>Utsteder</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">29</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Liquid Asset issuer</note>
<note priority="1" from="meaning">asset.issuer</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="e357dfd9e8685f17a862680cd98fe4aa2e068d28" datatype="html">
<source>Issuance TX</source>
<target>Utstedelse TX</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
2021-12-03 08:54:13 +09:00
<context context-type="linenumber">33</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Liquid Asset issuance TX</note>
<note priority="1" from="meaning">asset.issuance-tx</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="c5b2c0d65b8fd12ebf8c0d79f562703776fc954e" datatype="html">
<source>Pegged in</source>
<target>Pegged inn</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">37</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Liquid Asset pegged-in amount</note>
<note priority="1" from="meaning">asset.pegged-in</note>
</trans-unit>
<trans-unit id="8f5d6ce525a24b049fee47f9b2d8447cca97ccc8" datatype="html">
<source>Pegged out</source>
<target>Pegged ut</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">41</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09: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="21530115a661c0faac6906740c586118628c2d54" datatype="html">
<source>Issued amount</source>
<target>Beløp som er utstedt</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">45</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Liquid Asset issued amount</note>
<note priority="1" from="meaning">asset.issued-amount</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="e21556753a442f3d474ccfed50cd3f60bec18fe3" datatype="html">
<source>Burned amount</source>
<target>Beløp som er brent</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">49</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Liquid Asset burned amount</note>
<note priority="1" from="meaning">asset.burned-amount</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="1990b8bef8f205a7d1b821aa4f979cc9f4fe179d" datatype="html">
<source>Circulating amount</source>
<target>Sirkulerende beløp</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">53</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">57</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Liquid Asset circulating amount</note>
<note priority="1" from="meaning">asset.circulating-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>
2024-04-03 18:47:16 +09:00
<trans-unit id="c3360a933cb312b395d276a2b865214cf832df58" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ (transactions?.length | number) || '?' }}"/> of <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/>
<target> <x id="INTERPOLATION" equiv-text="{{ (transactions?.length | number) || '?' }}"/> av <x id="INTERPOLATION_1" equiv-text="{{ txCount | number }}"/></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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">78</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">asset.M_of_N</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>
2024-04-03 18:47:16 +09:00
<trans-unit id="d2a84740e76b7220516a9f10644e4b3bdabdb833" datatype="html">
<source>Peg In/Out and Burn Transactions</source>
<target>Peg inn / ut og brenn transaksjoner</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">79</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Liquid native asset transactions title</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="fcbd3315aa10b59ba6ef383c6f16ace6c9d53b71" datatype="html">
<source>Issuance and Burn Transactions</source>
<target>Utstedelse og forbrennings transaksjoner</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">80</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Default asset transactions title</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ef5ac12104751b93b03c16f64d4c3a4341dce89c" datatype="html">
<source>Error loading asset data.</source>
<target>Lasting av ressursdata feilet.</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.html</context>
<context context-type="linenumber">150</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">asset.error.loading-asset-data</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="asset.component.asset-browser-title" datatype="html">
<source>Asset: <x id="INTERPOLATION" equiv-text="this.assetString"/></source>
<target>Eiendel: <x id="INTERPOLATION" equiv-text="this.assetString"/></target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.ts</context>
<context context-type="linenumber">75</context>
2020-12-05 00:11:40 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.liquid.asset" datatype="html">
<source>Browse an overview of the Liquid asset <x id="INTERPOLATION" equiv-text="this.assetContract[1]"/> (<x id="INTERPOLATION" equiv-text="this.assetContract[1]"/>): see issued amount, burned amount, circulating amount, related transactions, and more.</source>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/asset/asset.component.ts</context>
<context context-type="linenumber">108</context>
2020-12-05 00:11:40 +09:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="e3f9fda25b281496fe296fb7e8228f59b50983ad" datatype="html">
<source>Group of <x id="INTERPOLATION" equiv-text="{{ group.assets.length | number }}"/> assets</source>
<target>Gruppe av <x id="INTERPOLATION" equiv-text="{{ group.assets.length | number }}"/> ressurser</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/asset-group/asset-group.component.html</context>
<context context-type="linenumber">8</context>
2020-12-05 00:11:40 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets-featured/assets-featured.component.html</context>
<context context-type="linenumber">11</context>
2021-04-26 04:05:55 +04:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="f315148e376b86b7c61be25ac372fcbd5cc49175" datatype="html">
<source>No featured assets</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets-featured/assets-featured.component.html</context>
<context context-type="linenumber">3</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.no-featured.assets</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ee8f8008bae6ce3a49840c4e1d39b4af23d4c263" datatype="html">
<source>Assets</source>
<target>Ressurser</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
<context context-type="linenumber">3</context>
2023-11-26 17:00:34 +09:00
</context-group>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.ts</context>
<context context-type="linenumber">42</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets.component.ts</context>
<context context-type="linenumber">44</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">78</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Assets page header</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="d06e27f7453fcf29134f9e61533ea4eb4b890f5f" datatype="html">
<source>Featured</source>
<target>Utvalgte</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
<context context-type="linenumber">9</context>
2024-01-22 21:30:03 +07:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="dfc3c34e182ea73c5d784ff7c8135f087992dac1" datatype="html">
<source>All</source>
<target>Alle</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">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>
2024-04-05 16:46:23 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-filters/block-filters.component.html</context>
<context context-type="linenumber">22</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">72</context>
2023-11-26 17:00:34 +09:00
</context-group>
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">122</context>
2021-04-26 05:37:03 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">145</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">408</context>
2023-11-26 17:00:34 +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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">433</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/rbf-list/rbf-list.component.html</context>
<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>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
<context context-type="linenumber">60</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-05 16:46:23 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.ts</context>
<context context-type="linenumber">78</context>
</context-group>
2020-12-05 00:11:40 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="aef0d676b15fdae8cb70fc3b089cce7399fde9da" datatype="html">
<source>Search asset</source>
<target>Søk ressurs</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
<context context-type="linenumber">19</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Search Assets Placeholder Text</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="99ee4faa69cd2ea8e3678c1f557c0ff1f05aae46" datatype="html">
<source>Clear</source>
<target>Fjern</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.html</context>
<context context-type="linenumber">21</context>
2021-12-26 11:15:19 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Search Clear Button</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.liquid.assets" datatype="html">
<source>Explore all the assets issued on the Liquid network like L-BTC, L-CAD, USDT, and more.</source>
<target>Utforsk alle eiendelene utstedt på Liquid-nettverket som L-BTC, L-CAD, USDT og mer.</target>
2021-12-26 11:15:19 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets-nav/assets-nav.component.ts</context>
<context context-type="linenumber">43</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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>
2024-04-03 18:47:16 +09:00
<trans-unit id="4ad173c0e4010b1f25bf58e96a383edc1b59cd80" datatype="html">
<source>Ticker</source>
<target>Ticker</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets.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>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets.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>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Asset ticker header</note>
</trans-unit>
<trans-unit id="465c39daa2b644679d73a451043622f1610a2084" datatype="html">
<source>Issuer domain</source>
<target>Utsteder-domene</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">6</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">33</context>
</context-group>
<note priority="1" from="description">Asset Issuer Domain header</note>
</trans-unit>
<trans-unit id="d5e7c95d7c8920ae0a384e3fffb14776b1e203f4" datatype="html">
<source>Asset ID</source>
<target>Ressurs-ID</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">7</context>
2021-12-03 08:54:13 +09:00
</context-group>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">34</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Asset ID 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>
2024-04-03 18:47:16 +09:00
<trans-unit id="52686df280be57a57e1e9ecf5786499b147e0e90" datatype="html">
<source>Error loading assets data.</source>
<target>Feil ved innlasting av ressursdata.</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/assets/assets.component.html</context>
<context context-type="linenumber">50</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Asset data load error</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ed8e33059967f554ff06b4f5b6049c465b92d9b3" datatype="html">
<source>Block Fee Rates</source>
<target>Blokkavgiftsrater</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.html</context>
<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>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.ts</context>
<context context-type="linenumber">72</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">17</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.block-fee-rates</note>
</trans-unit>
<trans-unit id="f2600d9f6db47cc43f16142cf401048a1d360bda" datatype="html">
<source>Avg Block Fee (24h)</source>
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.html</context>
<context context-type="linenumber">51</context>
2021-05-08 01:12:57 +04:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.html</context>
<context context-type="linenumber">76</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.avg-block-fee-24h</note>
</trans-unit>
<trans-unit id="de9a93ca8a13ccbd6de65782abb6b1432759b654" datatype="html">
<source>Avg Block Fee (1m)</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.html</context>
<context context-type="linenumber">57</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.html</context>
<context context-type="linenumber">84</context>
2020-12-05 00:11:40 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.avg-block-fee-1m</note>
</trans-unit>
<trans-unit id="meta.description.bitcoin.graphs.block-fee-rates" datatype="html">
<source>See Bitcoin feerates visualized over time, including minimum and maximum feerates per block along with feerates at various percentiles.</source>
<target>Se Bitcoin-gebyrer visualisert over tid, inkludert minimums- og maksimumsgebyrer per blokk sammen med gebyrer på forskjellige persentiler.</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fee-rates-graph/block-fee-rates-graph.component.ts</context>
<context context-type="linenumber">73</context>
2022-05-19 20:12:21 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="6c453b11fd7bd159ae30bc381f367bc736d86909" datatype="html">
<source>Block Fees</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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fees-graph/block-fees-graph.component.html</context>
<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>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fees-graph/block-fees-graph.component.ts</context>
<context context-type="linenumber">69</context>
2022-10-17 16:21:29 +04: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">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">19</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.block-fees</note>
</trans-unit>
<trans-unit id="meta.description.bitcoin.graphs.block-fees" datatype="html">
<source>See the average mining fees earned per Bitcoin block visualized in BTC and USD over time.</source>
<target>Se gjennomsnittlig utvinningsavgift tjent per Bitcoin-blokk visualisert i BTC og USD over tid.</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fees-graph/block-fees-graph.component.ts</context>
<context context-type="linenumber">70</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="23555386d8af1ff73f297e89dd4af3f4689fb9dd" datatype="html">
<source>Indexing blocks</source>
<target>Indekserer blokker</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-fees-graph/block-fees-graph.component.ts</context>
<context context-type="linenumber">119</context>
2021-04-26 04:05:55 +04:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-rewards-graph/block-rewards-graph.component.ts</context>
<context context-type="linenumber">116</context>
2022-10-17 16:21:29 +04:00
</context-group>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">119</context>
2021-04-26 04:05:55 +04:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">202</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrates-chart-pools/hashrate-chart-pools.component.ts</context>
<context context-type="linenumber">202</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/indexing-progress/indexing-progress.component.html</context>
<context context-type="linenumber">1</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool-preview.component.ts</context>
<context context-type="linenumber">120</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="98ec8c22c6a0e036b9af829b20e84afc56a79af8" datatype="html">
<source>select filter categories to highlight matching transactions</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-filters/block-filters.component.html</context>
<context context-type="linenumber">2</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-05 16:46:23 +09:00
<note priority="1" from="description">Mempool Goggles™ tooltip</note>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="7cbedd89f60daafaf0e56363900d666a4e02ffb1" datatype="html">
<source>beta</source>
<target>beta</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-filters/block-filters.component.html</context>
<context context-type="linenumber">3</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">76</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">beta</note>
</trans-unit>
2024-04-05 16:46:23 +09:00
<trans-unit id="180092a6b8a6151a05f4a7552a2fb75fd159dfa8" datatype="html">
<source>Match</source>
<target>Identisk</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-filters/block-filters.component.html</context>
<context context-type="linenumber">19</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">70</context>
</context-group>
<note priority="1" from="description">mempool-goggles.match</note>
</trans-unit>
<trans-unit id="16d449549ab7bc61caf3d636372a4a56b5870383" datatype="html">
<source>Any</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-filters/block-filters.component.html</context>
<context context-type="linenumber">25</context>
</context-group>
<note priority="1" from="description">mempool-goggles.any</note>
</trans-unit>
<trans-unit id="360b9f5c32209001518dbd1dc512f25291473b79" datatype="html">
<source>Tint</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-filters/block-filters.component.html</context>
<context context-type="linenumber">30</context>
</context-group>
<note priority="1" from="description">mempool-goggles.tint</note>
</trans-unit>
<trans-unit id="4cfabb48965febabe67eb491a3b7e58555d3d52a" datatype="html">
<source>Classic</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-filters/block-filters.component.html</context>
<context context-type="linenumber">33</context>
</context-group>
2024-04-09 16:58:02 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/theme-selector/theme-selector.component.html</context>
<context context-type="linenumber">3</context>
</context-group>
2024-04-05 16:46:23 +09:00
<note priority="1" from="description">mempool-goggles.classic</note>
</trans-unit>
<trans-unit id="2e6be334a2152f179a557167f98ce4459ff9a2f9" datatype="html">
<source>Age</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-filters/block-filters.component.html</context>
<context context-type="linenumber">36</context>
</context-group>
<note priority="1" from="description">mempool-goggles.age</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="b1fa5b210c9670d49a6506f046d4a0c2797fd402" datatype="html">
<source>Block Health</source>
<target>Blokkhelse</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-health-graph/block-health-graph.component.html</context>
<context context-type="linenumber">6</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">25</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.blocks-health</note>
</trans-unit>
<trans-unit id="d7d5fcf50179ad70c938491c517efb82de2c8146" datatype="html">
<source>Block Health</source>
<target>Blokkhelse</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-health-graph/block-health-graph.component.ts</context>
<context context-type="linenumber">63</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="meta.description.bitcoin.graphs.block-health" datatype="html">
<source>See Bitcoin block health visualized over time. Block health is a measure of how many expected transactions were included in an actual mined block. Expected transactions are determined using Mempool's re-implementation of Bitcoin Core's transaction selection algorithm.</source>
<target>Se Bitcoin-blokkhelse visualisert over tid. Blokkhelse er et mål på hvor mange forventede transaksjoner som ble inkludert i en faktisk utvunnet blokk. Forventede transaksjoner bestemmes ved hjelp av Mempools re-implementering av Bitcoin Cores transaksjonsvalgalgoritme.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-health-graph/block-health-graph.component.ts</context>
<context context-type="linenumber">64</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="80065834848189518" datatype="html">
<source>No data to display yet. Try again later.</source>
<target>Ingen data å vise ennå. Prøv igjen senere.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-health-graph/block-health-graph.component.ts</context>
<context context-type="linenumber">109</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/node-fee-chart/node-fee-chart.component.ts</context>
<context context-type="linenumber">120</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/node-statistics-chart/node-statistics-chart.component.ts</context>
<context context-type="linenumber">86</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-channels-map/nodes-channels-map.component.ts</context>
<context context-type="linenumber">233</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-map/nodes-map.component.ts</context>
<context context-type="linenumber">146</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="d2bcd3296d2850de762fb943060b7e086a893181" datatype="html">
<source>Health</source>
<target>Helse</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-health-graph/block-health-graph.component.ts</context>
<context context-type="linenumber">190</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">62</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">17</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">17</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">185</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="86c50fc2171298179283e3c9b6d79b57b821599b" datatype="html">
<source>not available</source>
<target>ikke tilgjengelig</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/block-overview-graph/block-overview-graph.component.html</context>
<context context-type="linenumber">7</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.not-available</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="f13653cd063e5c83ac884349e4657d68d804126e" datatype="html">
<source>Your browser does not support this feature.</source>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-graph/block-overview-graph.component.html</context>
<context context-type="linenumber">21</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">webgl-disabled</note>
</trans-unit>
<trans-unit id="b59ea65c89a5ae15b787d8318fdad9edd6fec243" datatype="html">
<source>Transaction</source>
<target>Transaksjon</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">12</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-list/recent-pegs-list.component.html</context>
<context context-type="linenumber">12</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<context context-type="linenumber">11</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction-preview.component.html</context>
<context context-type="linenumber">3</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">20</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">72</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.transaction</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="1bc4a5de56ea48a832e32294c124009867b478d0" datatype="html">
<source>First seen</source>
<target>Først sett</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">20</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">24</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">28</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<context context-type="linenumber">17</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">465</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">470</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
<context context-type="linenumber">74</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
<context context-type="linenumber">61</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
<context context-type="linenumber">58</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-ranking/oldest-nodes/oldest-nodes.component.html</context>
<context context-type="linenumber">11</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-capacity/top-nodes-per-capacity.component.html</context>
<context context-type="linenumber">15</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-channels/top-nodes-per-channels.component.html</context>
<context context-type="linenumber">15</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction first seen</note>
<note priority="1" from="meaning">transaction.first-seen</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="bfa87f9724434e4245b30f2bdd11d97477048cd1" datatype="html">
<source>Confirmed</source>
<target>Bekreftet</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">32</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">451</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/shared/components/confirmations/confirmations.component.html</context>
<context context-type="linenumber">9</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction confirmed state</note>
<note priority="1" from="meaning">transaction.confirmed</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="dfc2fb58e2a04ed944a4bd80f0a2087775134068" datatype="html">
<source>Amount</source>
<target>Beløp</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">38</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">10</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-list/recent-pegs-list.component.html</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">14</context>
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">135</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.latest-transactions.amount</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="cb1b52c13b95fa29ea4044f2bbe0ac623b890c80" datatype="html">
<source>Fee</source>
<target>Avgift</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">42</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<context context-type="linenumber">21</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction-preview.component.html</context>
<context context-type="linenumber">24</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">587</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">44</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">137</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction fee</note>
<note priority="1" from="meaning">transaction.fee</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="eb1737af67381ce6f0b347038bb4c65b3deb84be" datatype="html">
<source>Effective fee rate</source>
<target>Effektiv avgift</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">52</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">619</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Effective transaction fee rate</note>
<note priority="1" from="meaning">transaction.effective-fee-rate</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="a85400ca5aa86c938188f02b5fca2757d20b46ad" datatype="html">
<source>Accelerated fee rate</source>
<target>Akselerert gebyrsats</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">53</context>
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Effective transaction fee rate</note>
<note priority="1" from="meaning">transaction.effective-fee-rate</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="13f5a75f3e01e5924e45052d2f336eda8bac37e8" datatype="html">
<source>Weight</source>
<target>Vekt</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">63</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<context context-type="linenumber">29</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">104</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction Weight</note>
<note priority="1" from="meaning">transaction.weight</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="1a8035ac608b083c29407327290b7cc9d6cbb95d" datatype="html">
<source>Audit status</source>
<target>Revisjonsstatus</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">67</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">transaction.audit-status</note>
</trans-unit>
<trans-unit id="58fbcd58e305ab289b99fad67d223f3e83ddb755" datatype="html">
<source>Removed</source>
<target>Fjernet</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">71</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/shared/components/confirmations/confirmations.component.html</context>
<context context-type="linenumber">15</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction removed state</note>
<note priority="1" from="meaning">transaction.audit.removed</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="f0136f1a1d77aa656e0ebd0f3c023118dd2a2776" datatype="html">
<source>Marginal fee rate</source>
<target>Marginal avgiftsats</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">72</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">78</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">transaction.audit.marginal</note>
</trans-unit>
<trans-unit id="42795e8b4dc68e08fbf27cf2f7e724bbc2930610" datatype="html">
<source>High sigop count</source>
<target>Høyt antall sigops</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">73</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">transaction.audit.sigop</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="d702ad6f00c620c9658ac1ad8184d5fe5bc099fb" datatype="html">
<source>Recently broadcasted</source>
<target>Nylig sendt</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">74</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">transaction.audit.recently-broadcasted</note>
</trans-unit>
<trans-unit id="c9b422e0850708663a9748e778a9d6feb4d6394e" datatype="html">
<source>Recently CPFP'd</source>
<target>Nylig CPFPet</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">75</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">transaction.audit.recently-cpfped</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="73d42175ea0544a652c4f989afbec127367e8681" datatype="html">
<source>Added</source>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">76</context>
2024-01-22 21:30:03 +07:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">511</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Added</note>
<note priority="1" from="meaning">tx-features.tag.added</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="f046047ce9c57627e2b74101ef739a89cf0f568a" datatype="html">
<source>Prioritized</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">77</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">514</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Prioritized</note>
<note priority="1" from="meaning">tx-features.tag.prioritized</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="52d9050d910141e93c3005296a01ec5c7e62934b" datatype="html">
<source>Conflict</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">79</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">517</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Conflict</note>
<note priority="1" from="meaning">tx-features.tag.conflict</note>
</trans-unit>
<trans-unit id="b484583f0ce10f3341ab36750d05271d9d22c9a1" datatype="html">
<source>Accelerated</source>
<target>Akselerert</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">80</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-overview-tooltip/block-overview-tooltip.component.html</context>
<context context-type="linenumber">88</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">571</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-05 16:46:23 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/filters.utils.ts</context>
<context context-type="linenumber">99</context>
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">transaction.audit.accelerated</note>
</trans-unit>
<trans-unit id="8ba8fe810458280a83df7fdf4c614dfc1a826445" datatype="html">
<source>Block Rewards</source>
<target>Blokkbelønning</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-rewards-graph/block-rewards-graph.component.html</context>
<context context-type="linenumber">7</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-rewards-graph/block-rewards-graph.component.ts</context>
<context context-type="linenumber">67</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">21</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.block-rewards</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.bitcoin.graphs.block-rewards" datatype="html">
<source>See Bitcoin block rewards in BTC and USD visualized over time. Block rewards are the total funds miners earn from the block subsidy and fees.</source>
<target>Se Bitcoin-blokkbelønninger i BTC og USD visualisert over tid. Blokkbelønninger er de totale midlene utvinnerene tjener fra blokksubsidier og gebyr.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-rewards-graph/block-rewards-graph.component.ts</context>
<context context-type="linenumber">68</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="56fa1cd221491b6478998679cba2dc8d55ba330d" datatype="html">
<source>Block Sizes and Weights</source>
<target>Blokkstørrelse og vekt</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.html</context>
<context context-type="linenumber">5</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">64</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">23</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.block-sizes-weights</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.bitcoin.graphs.block-sizes" datatype="html">
<source>See Bitcoin block sizes (MB) and block weights (weight units) visualized over time.</source>
<target>Se Bitcoin-blokkstørrelser (MB) og blokkvekter (vektenheter) visualisert over tid.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">65</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="7faaaa08f56427999f3be41df1093ce4089bbd75" datatype="html">
<source>Size</source>
<target>Størrelse</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">187</context>
2023-11-26 17:00:34 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">242</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">54</context>
2022-10-17 16:21:29 +04:00
</context-group>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">25</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/clock/clock.component.html</context>
<context context-type="linenumber">54</context>
2021-04-26 04:05:55 +04:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">36</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mempool-graph/mempool-graph.component.ts</context>
<context context-type="linenumber">327</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">189</context>
2022-05-19 20:12:21 +04:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">250</context>
2022-10-17 16:21:29 +04:00
</context-group>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">227</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">108</context>
2021-06-11 10:58:54 -05:00
</context-group>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="919f2fd60a898850c24b1584362bbf18a4628bcb" datatype="html">
<source>Weight</source>
<target>Vekt</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">195</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">273</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.html</context>
<context context-type="linenumber">32</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">58</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">415</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">442</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">471</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">243</context>
2021-06-11 10:58:54 -05:00
</context-group>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="4786852746659896870" datatype="html">
<source>Size per weight</source>
<target>Størrelse per vekt</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">203</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-sizes-weights-graph/block-sizes-weights-graph.component.ts</context>
<context context-type="linenumber">285</context>
2021-06-11 10:58:54 -05:00
</context-group>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="block.component.browser-title" datatype="html">
<source>Block <x id="BLOCK_HEIGHT" equiv-text="block.height"/>: <x id="BLOCK_ID" equiv-text="block.id"/></source>
<target>Blokk <x id="BLOCK_HEIGHT" equiv-text="block.height"/>: <x id="BLOCK_ID" equiv-text="block.id"/></target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-view/block-view.component.ts</context>
<context context-type="linenumber">110</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.ts</context>
<context context-type="linenumber">102</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.ts</context>
<context context-type="linenumber">279</context>
2022-05-19 20:12:21 +04:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.liquid.block" datatype="html">
<source>See size, weight, fee range, included transactions, and more for Liquid<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> block <x id="BLOCK_HEIGHT" equiv-text="block.height"/> (<x id="BLOCK_ID" equiv-text="block.id"/>).</source>
<target>Se størrelse, vekt, gebyrområde, inkluderte transaksjoner og mer for Liquid<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> blokk <x id="BLOCK_HEIGHT" equiv-text="block.height"/> (<x id="BLOCK_ID" equiv-text="block.id"/>).</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-view/block-view.component.ts</context>
<context context-type="linenumber">112</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.ts</context>
<context context-type="linenumber">104</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.ts</context>
<context context-type="linenumber">281</context>
2022-05-19 20:12:21 +04:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.bitcoin.block" datatype="html">
<source>See size, weight, fee range, included transactions, audit (expected v actual), and more for Bitcoin<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> block <x id="BLOCK_HEIGHT" equiv-text="block.height"/> (<x id="BLOCK_ID" equiv-text="block.id"/>).</source>
<target>Se størrelse, vekt, gebyrområde, inkluderte transaksjoner, revisjon (forventet v faktisk) og mer for Bitcoin<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> blokk <x id="BLOCK_HEIGHT" equiv-text="block.height"/> ( <x id="BLOCK_ID" equiv-text="block.id"/>).</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block-view/block-view.component.ts</context>
<context context-type="linenumber">114</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.ts</context>
<context context-type="linenumber">106</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.ts</context>
<context context-type="linenumber">283</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="2303359202781425764" datatype="html">
<source>Genesis</source>
<target>Genesis</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.html</context>
<context context-type="linenumber">10</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">10</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="07193288a0312875e18f38c3a2486b927a15520a" datatype="html">
<source>Timestamp</source>
<target>Tidspunkt</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.html</context>
<context context-type="linenumber">26</context>
2023-11-26 17:00:34 +09:00
</context-group>
2023-11-28 14:42:25 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">48</context>
2023-11-28 14:42:25 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">15</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">182</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">244</context>
2022-05-19 20:12:21 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
<context context-type="linenumber">15</context>
2023-11-26 17:00:34 +09:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">434</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.timestamp</note>
</trans-unit>
<trans-unit id="0b47a777f024ab4e3cdf0062acb4d86e9ae1f635" datatype="html">
<source>Median fee</source>
<target>Medianavgift</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.html</context>
<context context-type="linenumber">36</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">136</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">16</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.median-fee</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ae9770436d1823a1ddfa0837c5a98f412a0d42c4" datatype="html">
<source>Total fees</source>
<target>Totale avgifter</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.html</context>
<context context-type="linenumber">41</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">147</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">173</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">409</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">430</context>
2021-07-25 01:49:35 +03:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">467</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">28</context>
2021-07-25 01:49:35 +03:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Total fees in a block</note>
<note priority="1" from="meaning">block.total-fees</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="21f88da2fbe81e4dc893ce1df92bd0fe25bcecee" datatype="html">
<source>Miner</source>
<target>Utvinner</target>
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block-preview.component.html</context>
<context context-type="linenumber">53</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">182</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">648</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.miner</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="e170a90ee0d3a604adf439a60c890caff9152466" datatype="html">
<source>This block does not belong to the main chain, it has been replaced by:</source>
<target>Denne blokken tilhører ikke hovedkjeden, den er erstattet av:</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">5</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Block reorg</note>
<note priority="1" from="meaning">block.reorged</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="a0e07a711d171f4d40dd388d70ed32f9b8101e0a" datatype="html">
<source>Previous Block</source>
<target>Forrige blokk</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">19</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Previous Block</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="0dc973e4853621b49d9e31be902a0680334f632d" datatype="html">
<source>Stale</source>
<target>Foreldet</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">30</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Stale block state</note>
<note priority="1" from="meaning">block.stale</note>
</trans-unit>
<trans-unit id="960cd598cbd85edb0a254ff3e59574d2c5cb888c" datatype="html">
<source>Hash</source>
<target>Hash</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">44</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.hash</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="e5d8bb389c702588877f039d72178f219453a72d" datatype="html">
<source>Unknown</source>
<target>Ukjent</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">73</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">62</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">122</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">106</context>
2023-11-26 17:00:34 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">218</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channel/closing-type/closing-type.component.ts</context>
<context context-type="linenumber">32</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.html</context>
<context context-type="linenumber">52</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
<context context-type="linenumber">56</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
<context context-type="linenumber">103</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
<context context-type="linenumber">154</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
<context context-type="linenumber">323</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-05 16:46:23 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/services/api.service.ts</context>
<context context-type="linenumber">254</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/services/api.service.ts</context>
<context context-type="linenumber">267</context>
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">unknown</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="b2cb12c1680a46464cae5aa0d0d1d6914733a75d" datatype="html">
<source>Fee span</source>
<target>Avgiftsintervall</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">132</context>
2023-11-26 17:00:34 +09:00
</context-group>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">20</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mempool-block.fee-span</note>
</trans-unit>
<trans-unit id="855f852e5642a1279605465df0cbbe78c2622648" datatype="html">
<source>Based on average native segwit transaction of 140 vBytes</source>
<target>Basert på gjennomsnittlig native segwit-transaksjon på 140 vBytes</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">140</context>
2021-06-11 10:58:54 -05:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">16</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">22</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">27</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">32</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.html</context>
<context context-type="linenumber">17</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction fee tooltip</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="a1c8a44428c774facdd0b1e3ae42468c25666367" datatype="html">
<source>Subsidy + fees</source>
<target>Subsidie + avgifter</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">162</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">177</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Total subsidy and fees in a block</note>
<note priority="1" from="meaning">block.subsidy-and-fees</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="23fa95fce7b4badf5ad584d4a1712d558266266f" datatype="html">
<source>Expected</source>
<target>Forventet</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">225</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.expected</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="1da6d9283e3222148d76c10c8e37abeeb66c93cb" datatype="html">
<source>Actual</source>
<target>Faktisk</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">227</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.actual</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="97577daae15cc7f30ab4d0f4f4dfb8045477aefd" datatype="html">
<source>Expected Block</source>
<target>Forventet blokk</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">231</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.expected-block</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="6efa73f0d6f0844a1e0c341c9b88323f51852d91" datatype="html">
<source>Actual Block</source>
<target>Faktisk blokk</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">246</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.actual-block</note>
</trans-unit>
<trans-unit id="8fe73a4787b8068b2ba61f54ab7e0f9af2ea1fc9" datatype="html">
<source>Version</source>
<target>Versjon</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">273</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">253</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">transaction.version</note>
</trans-unit>
<trans-unit id="65d5167c4947e3ad81758d238a7ac7e893c261f0" datatype="html">
<source>Taproot</source>
<target>Taproot</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">274</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">12</context>
2022-07-07 16:40:18 +02:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">14</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">16</context>
2023-11-26 17:00:34 +09:00
</context-group>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">18</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">21</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Taproot</note>
<note priority="1" from="meaning">tx-features.tag.taproot</note>
</trans-unit>
<trans-unit id="fd04710d1a54d46cd1b81a13fc98e3d561b92141" datatype="html">
<source>Bits</source>
<target>Bits</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">277</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.bits</note>
</trans-unit>
<trans-unit id="d71be278785ad5940aacaf2b29a67bdbf6fc6be8" datatype="html">
<source>Merkle root</source>
<target>Merklerot</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">281</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.merkle-root</note>
</trans-unit>
<trans-unit id="25148835d92465353fc5fe8897c27d5369978e5a" datatype="html">
<source>Difficulty</source>
<target>Vanskelighetsgrad</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">292</context>
2022-07-07 16:40:18 +02:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-adjustments-table/difficulty-adjustments-table.component.html</context>
<context context-type="linenumber">7</context>
2023-11-26 17:00:34 +09:00
</context-group>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">14</context>
2022-07-07 16:40:18 +02:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">75</context>
2022-07-07 16:40:18 +02:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">310</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">407</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.difficulty</note>
</trans-unit>
<trans-unit id="a6bb63d98a8a67689070a79ccf13960c25b572ef" datatype="html">
<source>Nonce</source>
<target>Nonce</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">296</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.nonce</note>
</trans-unit>
<trans-unit id="cbfb79ff517493268a49acffa81ecc02336d8372" datatype="html">
<source>Block Header Hex</source>
<target>Blokkheader Hex</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">300</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.header</note>
2022-07-07 16:40:18 +02:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ccf00caac258749fa1c5fd488fb15368fa6fce37" datatype="html">
<source>Audit</source>
<target>Revisjon</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">318</context>
2022-07-07 16:40:18 +02:00
</context-group>
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">498</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Toggle Audit</note>
<note priority="1" from="meaning">block.toggle-audit</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="5f32c623f92bf3ca31202cc6281d4abd5febaf6a" datatype="html">
<source>Details</source>
<target>Detaljer</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">325</context>
2022-07-07 16:40:18 +02:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">211</context>
2022-10-17 16:21:29 +04:00
</context-group>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">219</context>
2022-07-07 16:40:18 +02:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">344</context>
2022-07-07 16:40:18 +02:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
<context context-type="linenumber">93</context>
2022-07-07 16:40:18 +02:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
<context context-type="linenumber">103</context>
2022-07-07 16:40:18 +02:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/justice-list/justice-list.component.html</context>
<context context-type="linenumber">42</context>
2022-07-07 16:40:18 +02:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
<context context-type="linenumber">123</context>
2022-07-07 16:40:18 +02:00
</context-group>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
<context context-type="linenumber">264</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction Details</note>
<note priority="1" from="meaning">transaction.details</note>
2023-01-26 15:54:07 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="27387c2af5dcaf343a548feba821515f5dc00faa" datatype="html">
<source><x id="INTERPOLATION" equiv-text="transaction</ng-template> <ng-template #transactionsPlural let-i i18n="shared.trans"/> transaction</source>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">331</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blockchain-blocks/blockchain-blocks.component.html</context>
<context context-type="linenumber">54</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-blocks/mempool-blocks.component.html</context>
<context context-type="linenumber">31</context>
</context-group>
<note priority="1" from="description">shared.transaction-count.singular</note>
2023-01-26 15:54:07 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="14779b0ce4cbc4d975a35a8fe074426228a324f3" datatype="html">
<source><x id="INTERPOLATION" equiv-text="transactions</ng-template> </h2> <ngb-pagination class="pagination-container"/> transactions</source>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">332</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blockchain-blocks/blockchain-blocks.component.html</context>
<context context-type="linenumber">55</context>
2023-01-26 15:54:07 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mempool-blocks/mempool-blocks.component.html</context>
<context context-type="linenumber">32</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.transaction-count.plural</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="822972b5d47ee555d3be0c7ab9aae8090ecdf7bc" datatype="html">
<source>Error loading data.</source>
<target>Lasting av data feilet.</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">344</context>
2023-01-26 15:54:07 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">381</context>
2023-11-26 17:00:34 +09:00
</context-group>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
<context context-type="linenumber">70</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.html</context>
<context context-type="linenumber">66</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp-preview.component.html</context>
<context context-type="linenumber">61</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">error.general-loading-data</note>
2023-01-26 15:54:07 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="9f63968580fcea609d6b9e7a5b6ba7180b54e18f" datatype="html">
<source>Why is this block empty?</source>
<target>Hvorfor er denne blokken tom?</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">401</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">block.empty-block-explanation</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="958d4960ca7a46c7893e7b81ce7465872bb5a44f" datatype="html">
<source>Acceleration fees paid out-of-band</source>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/block/block.component.html</context>
<context context-type="linenumber">433</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Acceleration Fees</note>
</trans-unit>
<trans-unit id="8a7b4bd44c0ac71b2e72de0398b303257f7d2f54" datatype="html">
<source>Blocks</source>
<target>Blokker</target>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">4</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.ts</context>
<context context-type="linenumber">68</context>
2024-01-22 21:30:03 +07:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">67</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">87</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">94</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">master-page.blocks</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="179eb5c4a21ad324f75f723218a621d120e39d30" datatype="html">
<source>Height</source>
<target>Høyde</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">12</context>
2023-11-26 17:00:34 +09:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-adjustments-table/difficulty-adjustments-table.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">5</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">181</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">243</context>
2022-05-19 20:12:21 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">105</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">latest-blocks.height</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="e70fcca5a99575cffef3ff8cbd5e69f06ffd0f1c" datatype="html">
<source>Pool</source>
<target>Utvinningsgruppe</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">14</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">14</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">92</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.pool-name</note>
</trans-unit>
<trans-unit id="12f86e6747a5ad39e62d3480ddc472b1aeab5b76" datatype="html">
<source>Reward</source>
<target>Belønning</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">19</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">19</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">94</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">186</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">247</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">355</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">380</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">latest-blocks.reward</note>
</trans-unit>
<trans-unit id="c20172223f84462032664d717d739297e5a9e2fe" datatype="html">
<source>Fees</source>
<target>Avgifter</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">20</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">187</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">248</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">latest-blocks.fees</note>
</trans-unit>
<trans-unit id="e6213c3f05146287cf121868d9f3d3c3ff5f9714" datatype="html">
<source>TXs</source>
<target>TXs</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">23</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.html</context>
<context context-type="linenumber">23</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">188</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">249</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">107</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">284</context>
2023-02-27 23:09:11 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.txs</note>
2023-02-27 23:09:11 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.liquid.blocks" datatype="html">
<source>See the most recent Liquid<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> blocks along with basic stats such as block height, block size, and more.</source>
<target>Se de nyeste Liquid<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/>-blokkene sammen med grunnleggende statistikk som blokkhøyde, blokkstørrelse og mer.</target>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.ts</context>
<context context-type="linenumber">71</context>
2023-02-27 23:09:11 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="meta.description.bitcoin.blocks" datatype="html">
<source>See the most recent Bitcoin<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> blocks along with basic stats such as block height, block reward, block size, and more.</source>
<target>Se de nyeste Bitcoin<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/>-blokkene sammen med grunnleggende statistikk som blokkhøyde, blokkbelønning, blokkstørrelse og mer.</target>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/blocks-list/blocks-list.component.ts</context>
<context context-type="linenumber">73</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="cf8caac4de0166eae6cd0fdfd010ee92b995cd96" datatype="html">
<source>Calculator</source>
<target>Kalkulator</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/calculator/calculator.component.html</context>
<context context-type="linenumber">3</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">77</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.calculator</note>
</trans-unit>
<trans-unit id="clipboard.copied-message" datatype="html">
<source>Copied!</source>
<target>Kopiert!</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/clipboard/clipboard.component.ts</context>
<context context-type="linenumber">19</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="4d6ee53858628de558a18623894a03c8673bce9e" datatype="html">
<source>Price</source>
<target>Pris</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/clock/clock.component.html</context>
<context context-type="linenumber">41</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
</trans-unit>
<trans-unit id="d1d0bb0a34b216be66137562a0b18eaaca546113" datatype="html">
<source>High Priority</source>
<target>Høy prioritet</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/clock/clock.component.html</context>
<context context-type="linenumber">47</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">10</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">47</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">fees-box.high-priority</note>
</trans-unit>
<trans-unit id="b7dde2cf8ec2fcd328295c9c7fcc944c4d3720b6" datatype="html">
<source>Memory Usage</source>
<target>Minnebruk</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/clock/clock.component.html</context>
<context context-type="linenumber">65</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">288</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Memory usage</note>
<note priority="1" from="meaning">dashboard.memory-usage</note>
2023-01-26 15:54:07 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="60cd6fa18f925b42065d8cfb1a791efdc228b4c3" datatype="html">
<source>Unconfirmed</source>
<target>Ubekreftet</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/clock/clock.component.html</context>
<context context-type="linenumber">69</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">20</context>
2021-06-11 10:58:54 -05:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">282</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Unconfirmed count</note>
<note priority="1" from="meaning">dashboard.unconfirmed</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="736a52d86df31df97dbb673d5dd4cc30ee322805" datatype="html">
<source>Adjusted</source>
<target>Justert</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-adjustments-table/difficulty-adjustments-table.component.html</context>
<context context-type="linenumber">6</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.adjusted</note>
</trans-unit>
<trans-unit id="024cdb2814b0cb3f4ced148f1a0b9854447cb214" datatype="html">
<source>Change</source>
<target>Endring</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-adjustments-table/difficulty-adjustments-table.component.html</context>
<context context-type="linenumber">8</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.change</note>
</trans-unit>
<trans-unit id="63da83692b85cf17e0606153029a83fd4038d6dd" datatype="html">
<source>Difficulty Adjustment</source>
<target>Vanskelighetsgradjustering</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">1</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">1</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
<context context-type="linenumber">23</context>
2022-05-19 20:12:21 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.difficulty-adjustment</note>
</trans-unit>
<trans-unit id="0912816d94f2f05a7eee8f7622670e0c6bbbce16" datatype="html">
<source>Remaining</source>
<target>Gjenstående</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">7</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">74</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.remaining</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="1bb6965f8e1bbe40c076528ffd841da86f57f119" datatype="html">
<source><x id="INTERPOLATION" equiv-text="<span class="shared-block">blocks</span></ng-template> <ng-"/> <x id="START_TAG_SPAN" ctype="x-span" equiv-text="<span class="shared-block">"/>blocks<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="</span>"/></source>
<target><x id="INTERPOLATION" equiv-text="<span class="shared-block">blocks</span></ng-template> <ng-"/> <x id="START_TAG_SPAN" ctype="x-span" equiv-text="<span class="shared-block">"/>blokker<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="</span>"/></target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">10,11</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">67,68</context>
2022-10-17 16:21:29 +04:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">26,27</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/mempool-blocks/mempool-blocks.component.html</context>
<context context-type="linenumber">45,46</context>
2022-05-19 20:12:21 +04:00
</context-group>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
<context context-type="linenumber">78</context>
2023-03-14 14:54:49 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.blocks</note>
</trans-unit>
<trans-unit id="b7ef3894d9b6f157c400ddc937c70c9881ecd896" datatype="html">
<source><x id="INTERPOLATION" equiv-text="<span class="shared-block">block</span></ng-template> </div>"/> <x id="START_TAG_SPAN" ctype="x-span" equiv-text="<span class="shared-block">"/>block<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="</span>"/></source>
<target><x id="INTERPOLATION" equiv-text="<span class="shared-block">block</span></ng-template> </div>"/> <x id="START_TAG_SPAN" ctype="x-span" equiv-text="<span class="shared-block">"/>blokk<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="</span>"/></target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">11,12</context>
2022-05-19 20:12:21 +04:00
</context-group>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">68,69</context>
2021-06-11 10:58:54 -05:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">27,28</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.block</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="5e65ce907fc0e1a1a09d4130eb8c59d00a9457ef" datatype="html">
<source>Estimate</source>
<target>Anslag</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">16</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">81</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.estimate</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="680d5c75b7fd8d37961083608b9fcdc4167b4c43" datatype="html">
<source>Previous</source>
<target>Forrige</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">28</context>
2023-11-26 17:00:34 +09:00
</context-group>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">64</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.previous</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="5db469cd0357e5f578b85a996f7e99c9e4148ff5" datatype="html">
<source>Current Period</source>
<target>Nåværende periode</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">40</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.current-period</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="df71fa93f0503396ea2bb3ba5161323330314d6c" datatype="html">
<source>Next Halving</source>
<target>Neste halvering</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">47</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty-mining/difficulty-mining.component.html</context>
<context context-type="linenumber">88</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.next-halving</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="0c65c3ee0ce537e507e0b053b479012e5803d2cf" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> blocks expected</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokker forventet</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">50</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.expected-blocks</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ec9f27d00a7778cd1cfe1806105d2ca3314fa506" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> block expected</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokk forventet</target>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">51</context>
2023-02-27 23:09:11 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.expected-block</note>
2023-02-27 23:09:11 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="b89cb92adf0a831d4a263ecdba02139abbda02ae" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> blocks mined</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokker utvunnet</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">52</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.mined-blocks</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="4f7e823fd45c6def13a3f15f678888c7fe254fa5" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> block mined</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokk utvunnet</target>
2022-05-30 13:26:54 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">53</context>
2022-05-30 13:26:54 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.mined-block</note>
</trans-unit>
<trans-unit id="229dfb17b342aa8b9a1db27557069445ea1a7051" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> blocks remaining</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokker gjenstår</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">54</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.remaining-blocks</note>
</trans-unit>
<trans-unit id="13ff0d092caf85cd23815f0235e316dc3a6d1bbe" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> block remaining</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokk gjenstår</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">55</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.remaining-block</note>
</trans-unit>
<trans-unit id="4f78348af343fb64016891d67b53bdab473f9dbf" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> blocks ahead</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokker foran</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">56</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.blocks-ahead</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="15c5f3475966bf3be381378b046a65849f0f6bb6" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> block ahead</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokk foran</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">57</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.block-ahead</note>
2023-01-26 15:54:07 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="697b8cb1caaf1729809bc5c065d4dd873810550a" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> blocks behind</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokker bak</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">58</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.blocks-behind</note>
</trans-unit>
<trans-unit id="32137887e3f5a25b3a016eb03357f4e363fccb0b" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> block behind</source>
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> blokk bak</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty-tooltip.component.html</context>
<context context-type="linenumber">59</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.block-behind</note>
</trans-unit>
<trans-unit id="2d1bb593bedb956071b14cbb5cdd5e3150f0e575" datatype="html">
<source>Halving Countdown</source>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">2</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.halving-countdown</note>
</trans-unit>
<trans-unit id="8183ac396ad16924ae859b712bdc16b16a76ab87" datatype="html">
<source>difficulty</source>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">7</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">statistics.average-small</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="b9161223dda21fe34200a720dcb36830ca568104" datatype="html">
<source>halving</source>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">10</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">statistics.median-small</note>
</trans-unit>
<trans-unit id="5e78899c9b98f29856ce3c7c265e1344bc7a5a18" datatype="html">
<source>Average block time</source>
<target>Gjennomsnittlig blokktid</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">50</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.average-block-time</note>
</trans-unit>
<trans-unit id="8c134e132798ec5053a96a5a077056ace15b08d6" datatype="html">
<source>New subsidy</source>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">103</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">difficulty-box.new-subsidy</note>
</trans-unit>
<trans-unit id="ead7d1a15672d2e1859be66b014e6377c39ed0ca" datatype="html">
<source>Blocks remaining</source>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">111</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.blocks-remaining</note>
</trans-unit>
<trans-unit id="2133e2cd32cdb693a5bdbaeb425efe9e7172bd44" datatype="html">
<source>Block remaining</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/difficulty/difficulty.component.html</context>
<context context-type="linenumber">112</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.block-remaining</note>
</trans-unit>
<trans-unit id="6ff9e8b67bc2cda7569dc0996d4c2fd858c5d4e6" datatype="html">
<source>Either 2x the minimum, or the Low Priority rate (whichever is lower)</source>
<target>Enten 2x av minimum eller lav prioritetsrate (den som er lavest)</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">4</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction feerate tooltip (economy)</note>
</trans-unit>
<trans-unit id="eef30290726d3d569232f4c136082bb9daaf490b" datatype="html">
<source>No Priority</source>
<target>Ingen prioritet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">4</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">41</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">fees-box.no-priority</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="49bba8e970aa3b1bec6fcff7228ef95ceb335f59" datatype="html">
<source>Usually places your transaction in between the second and third mempool blocks</source>
<target>Plasserer vanligvis transaksjonen din mellom andre og tredje mempool-blokken</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">8</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction feerate tooltip (low priority)</note>
</trans-unit>
<trans-unit id="29949587189ee02db19274db4ac656913cb243c3" datatype="html">
<source>Low Priority</source>
<target>Lav prioritet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">8</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">45</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">fees-box.low-priority</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="eeeeabc97373285d75acf0f013f68434a6f1935b" datatype="html">
<source>Usually places your transaction in between the first and second mempool blocks</source>
<target>Plasserer vanligvis transaksjonen mellom den første og andre mempool-blokken</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">9</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction feerate tooltip (medium priority)</note>
</trans-unit>
<trans-unit id="ee847b69ef2dc81bb3e9b8cd30f02f8d63adbe07" datatype="html">
<source>Medium Priority</source>
<target>Medium prioritet</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">9</context>
2021-06-11 10:58:54 -05:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">46</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">fees-box.medium-priority</note>
</trans-unit>
<trans-unit id="a5a4d2c76b74faddf1aab8dc6e092cddee5a6142" datatype="html">
<source>Places your transaction in the first mempool block</source>
<target>Legger din transaksjon inn i den første mempool blokken</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/fees-box/fees-box.component.html</context>
<context context-type="linenumber">10</context>
2021-06-11 10:58:54 -05:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Transaction feerate tooltip (high priority)</note>
</trans-unit>
<trans-unit id="9dfdbeb922d811d7b7b3fecd48360a059e52aaba" datatype="html">
<source>Incoming Transactions</source>
<target>Innkommende transaksjoner</target>
2021-06-11 10:58:54 -05:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">5</context>
2021-07-25 01:49:35 +03:00
</context-group>
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">48</context>
2021-07-25 01:49:35 +03:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.incoming-transactions</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="a5950b2ce4c3ea32de91034de8269781eb333d73" datatype="html">
<source>Backend is synchronizing</source>
<target>Backend synkroniserer</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">8</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.backend-is-synchronizing</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="50904e472d4671388a20fbbb1ee9dfc0a4586fa1" datatype="html">
<source>vB/s</source>
<target>vB/s</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">13</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">vB/s</note>
<note priority="1" from="meaning">shared.vbytes-per-second</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="93168b4de564d2c5d21d67cf2fb263f27b45e4c8" datatype="html">
<source>WU/s</source>
<target>WU/s</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">14</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">WU/s</note>
<note priority="1" from="meaning">shared.weight-per-second</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="6f7832e2e8db3c4b16c41681ba334a2ab9726cc3" datatype="html">
<source>Mempool size</source>
<target>Mempool størrelse</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/footer/footer.component.html</context>
<context context-type="linenumber">24</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">Mempool size</note>
<note priority="1" from="meaning">dashboard.mempool-size</note>
</trans-unit>
<trans-unit id="c95f8a34509967d6cbcf118a9637b23a83633449" datatype="html">
<source>Mining</source>
<target>Utvinning</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">7</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="4592bd8fffebd3841fc8d59472caf4b4655e6184" datatype="html">
<source>Pools Ranking</source>
<target>Utvinningsgruppe-rangering</target>
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">10</context>
2021-12-03 08:54:13 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">36</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.pools</note>
</trans-unit>
<trans-unit id="43f992a71c7b7def78d430e5af489b914cc61c11" datatype="html">
<source>Pools Dominance</source>
<target>Utvinningsgruppe-dominans</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">12</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrates-chart-pools/hashrate-chart-pools.component.html</context>
<context context-type="linenumber">7</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.pools-dominance</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="5115edb23059f4dcfe6ce0a979e40962a149c35c" datatype="html">
<source>Hashrate & Difficulty</source>
<target>Hashrate og vanskelighetsgrad</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">14,15</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.hashrate-difficulty</note>
</trans-unit>
<trans-unit id="a3382a60534e9fff5c3a0fcde39bab356afc4a59" datatype="html">
<source>Lightning</source>
<target>Lightning</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">30</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">lightning</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="b420668a91f8ebaf6e6409c4ba87f1d45961d2bd" datatype="html">
<source>Lightning Nodes Per Network</source>
<target>Lightning-noder per nettverk</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">33</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.html</context>
<context context-type="linenumber">5</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
<context context-type="linenumber">73</context>
2023-11-26 17:00:34 +09:00
</context-group>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
<context context-type="linenumber">143</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">lightning.nodes-networks</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ea8db27e6db64f8b940711948c001a1100e5fe9f" datatype="html">
<source>Lightning Network Capacity</source>
<target>Lightningnettverk-kapasitet</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">35</context>
2021-12-03 08:54:13 +09:00
</context-group>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.html</context>
<context context-type="linenumber">5</context>
2023-03-14 14:54:49 +09:00
</context-group>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.ts</context>
<context context-type="linenumber">70</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.ts</context>
<context context-type="linenumber">133</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">lightning.network-capacity</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="8573a1576789bd2c4faeaed23037c4917812c6cf" datatype="html">
<source>Lightning Nodes Per ISP</source>
<target>Lightning-noder per ISP</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">37</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.ts</context>
<context context-type="linenumber">53</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">lightning.nodes-per-isp</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="9d3ad4c6623870d96b65fb7a708fed6ce7c20044" datatype="html">
<source>Lightning Nodes Per Country</source>
<target>Lightning-noder per land</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">39</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.html</context>
<context context-type="linenumber">5</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.ts</context>
<context context-type="linenumber">46</context>
2021-12-03 08:54:13 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">lightning.nodes-per-country</note>
</trans-unit>
<trans-unit id="af8560ca50882114be16c951650f83bca73161a7" datatype="html">
<source>Lightning Nodes World Map</source>
<target>Lightning-noder verdenskart</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">41</context>
2021-06-11 10:58:54 -05:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-map/nodes-map.component.html</context>
<context context-type="linenumber">5</context>
2022-10-17 16:21:29 +04:00
</context-group>
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-map/nodes-map.component.ts</context>
<context context-type="linenumber">51</context>
2021-07-25 01:49:35 +03:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">lightning.lightning.nodes-heatmap</note>
</trans-unit>
<trans-unit id="b482ceceb39c7a045cb2ab2c64f7091d21e63d44" datatype="html">
<source>Lightning Nodes Channels World Map</source>
<target>Lightning-kanaler Verdenskart</target>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/graphs/graphs.component.html</context>
<context context-type="linenumber">43</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-channels-map/nodes-channels-map.component.html</context>
<context context-type="linenumber">20</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">lightning.nodes-channels-world-map</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="79a9dc5b1caca3cbeb1733a19515edacc5fc7920" datatype="html">
<source>Hashrate</source>
<target>Hashrate</target>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">8</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">69</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">299</context>
2021-04-26 04:05:55 +04:00
</context-group>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">395</context>
2023-03-14 14:54:49 +09:00
</context-group>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">93</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool-preview.component.html</context>
<context context-type="linenumber">22</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.ts</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">213</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.ts</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">267</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.hashrate</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="3510fc6daa1d975f331e3a717bdf1a34efa06dff" datatype="html">
<source>Hashrate & Difficulty</source>
<target>Hashrate og vanskelighetsgrad</target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.html</context>
<context context-type="linenumber">27</context>
2023-03-14 14:54:49 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">75</context>
</context-group>
<note priority="1" from="description">mining.hashrate-difficulty</note>
2023-03-14 14:54:49 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.bitcoin.graphs.hashrate" datatype="html">
<source>See hashrate and difficulty for the Bitcoin<x id="PH" equiv-text="seoDescriptionNetwork(this.network)"/> network visualized over time.</source>
<target>Se hashrate og vanskelighetsgrad for Bitcoin<x id="PH" equiv-text="seoDescriptionNetwork(this.network)"/>-nettverket visualisert over tid.</target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">76</context>
2023-03-14 14:54:49 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="8105839921891777281" datatype="html">
<source>Hashrate (MA)</source>
<target>Hashrate (MA)</target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">318</context>
2023-03-14 14:54:49 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrate-chart/hashrate-chart.component.ts</context>
<context context-type="linenumber">418</context>
2023-03-14 14:54:49 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="mining.pools-historical-dominance" datatype="html">
<source>Pools Historical Dominance</source>
<target>Utvinningsgruppe historisk dominans</target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrates-chart-pools/hashrate-chart-pools.component.ts</context>
<context context-type="linenumber">74</context>
2023-03-14 14:54:49 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.descriptions.bitcoin.graphs.hashrate-pools" datatype="html">
<source>See Bitcoin mining pool dominance visualized over time: see how top mining pools' share of total hashrate has fluctuated over time.</source>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/hashrates-chart-pools/hashrate-chart-pools.component.ts</context>
<context context-type="linenumber">75</context>
2023-03-14 14:54:49 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="5ee5eb7db86675abd5f0b0db835bf362ee9b23ff" datatype="html">
<source>Indexing network hashrate</source>
<target>Indekserer nettverk-hashrate</target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/indexing-progress/indexing-progress.component.html</context>
<context context-type="linenumber">2</context>
2023-03-14 14:54:49 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="439adfcf08f5035e2fd9e4c15e40eef92f6cc780" datatype="html">
<source>Indexing pools hashrate</source>
<target>Indekserer utvinningsgruppe-hashrate</target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/indexing-progress/indexing-progress.component.html</context>
<context context-type="linenumber">3</context>
2023-03-14 14:54:49 +09:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="2b34680062c4aed90c4d846eab42d6e99501b783" datatype="html">
<source>Offline</source>
<target>Offline</target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">41</context>
2023-03-14 14:54:49 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">30</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
<context context-type="linenumber">47</context>
2023-03-14 14:54:49 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">master-page.offline</note>
2023-03-14 14:54:49 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="c5d46228bea3555d65c705bad40be80f8798a113" datatype="html">
<source>Reconnecting...</source>
<target>Kobler til igjen...</target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">42</context>
2023-03-14 14:54:49 +09:00
</context-group>
2022-06-08 00:44:04 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">31</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
<context context-type="linenumber">48</context>
2022-06-08 00:44:04 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">master-page.reconnecting</note>
2022-06-08 00:44:04 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="9daedf013e87630c4e0a9123dc62e5bbf15a59ad" datatype="html">
<source>Layer 2 Networks</source>
<target>Lag 2-nettverk</target>
2022-06-05 22:39:36 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">55</context>
2022-06-05 22:39:36 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">61</context>
2022-06-05 22:39:36 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">master-page.layer2-networks-header</note>
2022-06-05 22:39:36 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="f65253954b66e929a8b4d5ecaf61f9129f8cec64" datatype="html">
<source>Dashboard</source>
<target>Dashbord</target>
2022-06-08 00:44:04 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">64</context>
2022-06-08 00:44:04 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">71</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">master-page.dashboard</note>
2022-06-08 00:44:04 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="5d4f792f048fcaa6df5948575d7cb325c9393383" datatype="html">
<source>Graphs</source>
<target>Grafer</target>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">70</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">90</context>
2021-04-26 04:05:55 +04:00
</context-group>
2022-06-08 00:44:04 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/statistics/statistics.component.ts</context>
<context context-type="linenumber">66</context>
2022-06-08 00:44:04 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">master-page.graphs</note>
2022-06-08 00:44:04 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="fcfd4675b4c90f08d18d3abede9a9a4dff4cfdc7" datatype="html">
<source>Documentation</source>
<target>Dokumentasjon</target>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-master-page/liquid-master-page.component.html</context>
<context context-type="linenumber">81</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">93</context>
2021-07-25 01:49:35 +03:00
</context-group>
2024-04-03 18:47:16 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.html</context>
<context context-type="linenumber">4</context>
</context-group>
<note priority="1" from="description">documentation.title</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="b4f212e7d0333eb600f835e4664846f9a1a58424" datatype="html">
<source>Non-Dust Expired</source>
2022-06-08 00:44:04 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/expired-utxos-stats/expired-utxos-stats.component.html</context>
<context context-type="linenumber">3</context>
2022-06-08 00:44:04 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.non-dust-expired</note>
2022-06-08 00:44:04 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="506d3b3e461d170c39745288b9ea96b9ac9b7f78" datatype="html">
<source>Total amount of BTC held in non-dust Federation UTXOs that have expired timelocks</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/expired-utxos-stats/expired-utxos-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">5</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.expired-utxos-non-dust</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="0aa722d7f1a3122b0d3e360ed3e91049bef3d9f4" datatype="html">
<source>UTXOs</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/expired-utxos-stats/expired-utxos-stats.component.html</context>
<context context-type="linenumber">6</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/expired-utxos-stats/expired-utxos-stats.component.html</context>
<context context-type="linenumber">16</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-addresses-stats/federation-addresses-stats.component.html</context>
<context context-type="linenumber">9</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.utxos</note>
</trans-unit>
<trans-unit id="5754c4f243f1eca150768c8435b70657f42eceb8" datatype="html">
<source>Total Expired</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/expired-utxos-stats/expired-utxos-stats.component.html</context>
<context context-type="linenumber">12</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.total-expired</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="a1351919fe237825d7d5844cff22192f88bd1eb4" datatype="html">
<source>Total amount of BTC held in Federation UTXOs that have expired timelocks</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/expired-utxos-stats/expired-utxos-stats.component.html</context>
<context context-type="linenumber">15</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.expired-utxos</note>
</trans-unit>
<trans-unit id="993e5bc509c26db81d93018e24a6afe6e50cae52" datatype="html">
<source>Liquid Federation Wallet</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-addresses-stats/federation-addresses-stats.component.html</context>
<context context-type="linenumber">5</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-addresses-stats/federation-addresses-stats.component.html</context>
<context context-type="linenumber">19</context>
2021-07-25 01:49:35 +03:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-wallet/federation-wallet.component.html</context>
<context context-type="linenumber">3</context>
2021-07-25 01:49:35 +03:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-wallet/federation-wallet.component.ts</context>
<context context-type="linenumber">14</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.federation-wallet</note>
</trans-unit>
<trans-unit id="aaf6d7c1f6bc35ffe3e131be28b444f6f8bd76b4" datatype="html">
<source>addresses</source>
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-addresses-stats/federation-addresses-stats.component.html</context>
<context context-type="linenumber">8</context>
2021-07-25 01:49:35 +03:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.addresses</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="7a080851e25a41e898776a9c90cf8dbe81027f9a" datatype="html">
<source>Output</source>
<target>Utgang</target>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">8</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">43</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">76</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">transaction.output</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="4e3a7555e83abb62ac42d78275cf01b81793cd92" datatype="html">
<source>Related Peg-In</source>
2021-07-25 01:49:35 +03:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">11</context>
2021-07-25 01:49:35 +03:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.related-peg-in</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="2f933b826a570836cab04f683970a2d22068458c" datatype="html">
<source>Date</source>
<target>Dato</target>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">12</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-list/recent-pegs-list.component.html</context>
<context context-type="linenumber">13</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
<context context-type="linenumber">9</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.date</note>
</trans-unit>
<trans-unit id="f093a73f10804563b96cab97e4e0516ce684e036" datatype="html">
<source>Expires in</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">13</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.expires-in</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="7f37d56e12d893cd46fc8ccba015d51f32d83131" datatype="html">
<source>Expired since</source>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">14</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.expired-since</note>
</trans-unit>
<trans-unit id="1c6520aeea2eb946269acab0a2863162b8311e7d" datatype="html">
<source>Dust</source>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">15</context>
2022-07-07 16:40:18 +02:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.dust</note>
</trans-unit>
<trans-unit id="a5d0bd2f3fedabd093937eb13a9edb9bcd00b919" datatype="html">
<source>Change output</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">55</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.change-output</note>
</trans-unit>
<trans-unit id="1a8246eba9a999ee881248c4767d63b875ef07fe" datatype="html">
<source>blocks</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-utxos-list/federation-utxos-list.component.html</context>
<context context-type="linenumber">63</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.blocks</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="b4a7d4e1363be9ed70ec20dbf1a97bff3e94e5b7" datatype="html">
<source>Timelock-Expired UTXOs</source>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-wallet/federation-wallet.component.html</context>
<context context-type="linenumber">12</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.timelock-expired-utxos</note>
</trans-unit>
<trans-unit id="7882f2edb1d4139800b276b6b0bbf5ae0b2234ef" datatype="html">
<source>Addresses</source>
<target>Adresser</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/federation-wallet/federation-wallet.component.html</context>
<context context-type="linenumber">15</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2023-03-14 14:54:49 +09:00
<context context-type="linenumber">39</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">63</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">321</context>
2021-04-26 04:05:55 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">332</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.addresses</note>
</trans-unit>
<trans-unit id="a8b0889ea1b41888f1e247f2731cc9322198ca04" datatype="html">
<source>Recent Peg-In / Out's</source>
2021-08-03 18:38:34 +03:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-list/recent-pegs-list.component.html</context>
<context context-type="linenumber">4</context>
2021-08-03 18:38:34 +03:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-list/recent-pegs-list.component.ts</context>
<context context-type="linenumber">66</context>
2021-08-03 18:38:34 +03:00
</context-group>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-stats/recent-pegs-stats.component.html</context>
<context context-type="linenumber">5</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-stats/recent-pegs-stats.component.html</context>
<context context-type="linenumber">29</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.recent-pegs</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="3669efae1ff592688b4df067abf0a272e90af226" datatype="html">
<source>Fund / Redemption Tx</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-list/recent-pegs-list.component.html</context>
<context context-type="linenumber">15</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.fund-redemption-tx</note>
</trans-unit>
<trans-unit id="4dbfcaee1d2f0308bd20b3b6b6655ba1e04330dc" datatype="html">
<source>BTC Address</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-list/recent-pegs-list.component.html</context>
<context context-type="linenumber">16</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.bitcoin-address</note>
</trans-unit>
<trans-unit id="2e37a2401f3cb55f2b0c108f77c28bb9738f09e0" datatype="html">
<source>Peg out in progress...</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-list/recent-pegs-list.component.html</context>
<context context-type="linenumber">70</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.redemption-in-progress</note>
</trans-unit>
<trans-unit id="92b8788842b6cced2a7dad59e5fa1803daff1ca2" datatype="html">
<source>24h Peg-In Volume</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-stats/recent-pegs-stats.component.html</context>
<context context-type="linenumber">12</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.peg-ins-volume-day</note>
</trans-unit>
<trans-unit id="44cfc2e57619bf9beab1ef5b4bedfa52246f5e27" datatype="html">
<source>Peg-Ins</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-stats/recent-pegs-stats.component.html</context>
<context context-type="linenumber">13</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.peg-ins</note>
</trans-unit>
<trans-unit id="544fb5f2a64924b4b9d7d2bc25b8925492bd6d64" datatype="html">
<source>24h Peg-Out Volume</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-stats/recent-pegs-stats.component.html</context>
<context context-type="linenumber">18</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.peg-out-volume-day</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="3e7a5b4cf20d583207c96127eb0f0d1b91358544" datatype="html">
<source>Peg-Outs</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/recent-pegs-stats/recent-pegs-stats.component.html</context>
<context context-type="linenumber">19</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.peg-outs</note>
</trans-unit>
<trans-unit id="380175a30ef4d977ec376044b17cf505d0e8ede0" datatype="html">
<source>Unpeg</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-ratio-stats/reserves-ratio-stats.component.html</context>
<context context-type="linenumber">3</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.unpeg</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="34e09704961f3373354d01328a1bb907ffbe44a6" datatype="html">
<source>Unpeg Event</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-ratio-stats/reserves-ratio-stats.component.html</context>
<context context-type="linenumber">7</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.unpeg-event</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="a4c3af092f04fb531a39f0a85e2f7b13ef6e9512" datatype="html">
<source>Avg Peg Ratio</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-ratio-stats/reserves-ratio-stats.component.html</context>
<context context-type="linenumber">14</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.avg-peg-ratio</note>
</trans-unit>
<trans-unit id="6ffd2b9ed79c063071099b61933a45f68f7ff5a2" datatype="html">
<source>Emergency Keys</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-ratio-stats/reserves-ratio-stats.component.html</context>
<context context-type="linenumber">28</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.emergency-keys</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="81f05fa58fc9f3fb248f0b4f5710163461d06ea1" datatype="html">
<source>usage</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-ratio-stats/reserves-ratio-stats.component.html</context>
<context context-type="linenumber">31</context>
2021-04-26 04:05:55 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.usage</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="9076228015944198327" datatype="html">
<source>Assets vs Liabilities</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-ratio/reserves-ratio.component.ts</context>
<context context-type="linenumber">162</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="eb7a000cd340b44291d790f7b56f7b926edc275b" datatype="html">
<source>L-BTC in circulation</source>
<target>L-BTC i omløp</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-supply-stats/reserves-supply-stats.component.html</context>
2022-10-17 16:21:29 +04:00
<context context-type="linenumber">3</context>
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.lbtc-pegs-in-circulation</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="bda0c55e9a859780b954c2718f66496d8ea13b63" datatype="html">
<source>As of block</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-supply-stats/reserves-supply-stats.component.html</context>
<context context-type="linenumber">7</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-supply-stats/reserves-supply-stats.component.html</context>
<context context-type="linenumber">16</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.as-of-block</note>
</trans-unit>
<trans-unit id="0ae529953ee15ef7af41fe3a3c30a10de5347f34" datatype="html">
<source>BTC Holdings</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/components/liquid-reserves-audit/reserves-supply-stats/reserves-supply-stats.component.html</context>
<context context-type="linenumber">12</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.btc-holdings</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="a681a4e2011bb28157689dbaa387de0dd0aa0c11" datatype="html">
<source>Mining Dashboard</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">80</context>
2024-04-03 18:47:16 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.ts</context>
<context context-type="linenumber">28</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">48</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.mining-dashboard</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
<trans-unit id="142e923d3b04186ac6ba23387265d22a2fa404e0" datatype="html">
<source>Lightning Explorer</source>
2023-02-27 23:09:11 +04:00
<target>Lightning Explorer</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/master-page/master-page.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">83</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/lightning-dashboard/lightning-dashboard.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">33</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">49</context>
2023-11-26 17:00:34 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<note priority="1" from="description">master-page.lightning</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.mempool-block" datatype="html">
<source>See stats for <x id="PH" equiv-text="this.stateService.network==='liquid'||this.stateService.network==='liquidtestnet'?'Liquid':'Bitcoin'"/><x id="PH_1" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> transactions in the mempool: fee range, aggregate size, and more. Mempool blocks are updated in real-time as the network receives new transactions.</source>
2024-01-13 16:57:03 +00:00
<target>Se statistikk for <x id="PH" equiv-text="this.stateService.network==='liquid'||this.stateService.network==='liquidtestnet'?'Liquid':'Bitcoin'"/><x id="PH_1" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> transaksjoner i mempoolen: gebyrområde, samlet størrelse og mer. Mempool-blokker oppdateres i sanntid etter hvert som nettverket mottar nye transaksjoner.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">62</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="mempool-block.stack.of.blocks" datatype="html">
<source>Stack of <x id="INTERPOLATION" equiv-text="blocksInBlock"/> mempool blocks</source>
<target>Stabel med <x id="INTERPOLATION" equiv-text="blocksInBlock"/> mempoolblokker</target>
2021-06-11 23:27:29 -05:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">89</context>
2021-06-11 23:27:29 -05:00
</context-group>
2022-05-19 20:12:21 +04:00
</trans-unit>
<trans-unit id="mempool-block.block.no" datatype="html">
<source>Mempool block <x id="INTERPOLATION" equiv-text="this.mempoolBlockIndex + 1"/></source>
<target>Mempool blokk <x id="INTERPOLATION" equiv-text="this.mempoolBlockIndex + 1"/></target>
2021-06-11 23:27:29 -05:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-block/mempool-block.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">91</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
<trans-unit id="8177873832400820695" datatype="html">
<source>Count</source>
2024-01-13 16:57:03 +00:00
<target>Antall</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/mempool-graph/mempool-graph.component.ts</context>
<context context-type="linenumber">325</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.ts</context>
<context context-type="linenumber">50</context>
2020-12-05 00:36:00 +09:00
</context-group>
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="2348971518300945764" datatype="html">
<source>Range</source>
<target>Område</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-graph/mempool-graph.component.ts</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">326</context>
2020-12-08 11:58:43 +07:00
</context-group>
2021-12-26 11:15:19 +04:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="1033261550402895380" datatype="html">
<source>Sum</source>
<target>Sum</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mempool-graph/mempool-graph.component.ts</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">328</context>
</context-group>
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="26e78cd052d05a0c1a7db43fac8df52ec6950672" datatype="html">
<source>Reward stats</source>
2023-03-26 16:46:20 +09:00
<target>Belønnings-statistikk</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
2023-03-14 14:54:49 +09:00
<context context-type="linenumber">9</context>
2020-12-08 11:58:43 +07:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.reward-stats</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="8527213d7c7dbffe48a45c4d796ae221d419c71a" datatype="html">
<source>(144 blocks)</source>
2022-06-08 00:44:04 +04:00
<target>(144 blokker)</target>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
2023-03-14 14:54:49 +09:00
<context context-type="linenumber">10</context>
2021-04-26 04:05:55 +04:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.144-blocks</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="93ce500c36b94b52219495ae1491efc2fca40cb6" datatype="html">
<source>Recent Blocks</source>
2024-01-13 16:57:03 +00:00
<target>Nylige blokker</target>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">56</context>
2021-04-26 04:05:55 +04:00
</context-group>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">99</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">50</context>
2020-12-08 11:58:43 +07:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">dashboard.recent-blocks</note>
2021-12-26 11:15:19 +04:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="21d0c2d4d5429197892c827178819da2770f2f25" datatype="html">
<source>Adjustments</source>
2022-06-08 00:44:04 +04:00
<target>Justeringer</target>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">70</context>
2021-04-26 04:05:55 +04:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">dashboard.adjustments</note>
2020-12-08 11:58:43 +07:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.mining.dashboard" datatype="html">
<source>Get real-time Bitcoin mining stats like hashrate, difficulty adjustment, block rewards, pool dominance, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Få sanntids Bitcoin-utvinningsstatistikk som hashrate, vanskeliggradsjustering, blokkbelønninger, gruppedominans og mer.</target>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/mining-dashboard/mining-dashboard.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">29</context>
2023-02-27 23:09:11 +04:00
</context-group>
</trans-unit>
2022-07-07 16:40:18 +02:00
<trans-unit id="2711844b4304254e88358d1761f9c732e5aefc69" datatype="html">
<source>Pools luck (1 week)</source>
2023-03-09 11:49:26 +09:00
<target>Utvinningsgrupper flaks (1 uke)</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2022-07-07 16:40:18 +02:00
<context context-type="linenumber">9</context>
2020-12-08 11:58:43 +07:00
</context-group>
2022-07-07 16:40:18 +02:00
<note priority="1" from="description">mining.miners-luck-1w</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="4e338e7daa64c7a074cee3824fbd7425e5b7c9a5" datatype="html">
<source>Pools Luck</source>
2024-01-13 16:57:03 +00:00
<target>Gruppeflaks</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">9</context>
</context-group>
2021-04-26 04:05:55 +04:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">156</context>
2021-04-26 04:05:55 +04:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.miners-luck</note>
2020-12-08 11:58:43 +07:00
</trans-unit>
2022-07-07 16:40:18 +02:00
<trans-unit id="e910ea39a964514d51802d34cad96c75b14947d1" datatype="html">
<source>The overall luck of all mining pools over the past week. A luck bigger than 100% means the average block time for the current epoch is less than 10 minutes.</source>
2022-10-17 16:21:29 +04:00
<target>Den generelle flaksen til alle utvinningsgrupper den siste uken. En flaks større enn 100 % betyr at den gjennomsnittlige blokktiden for gjeldende epoke er mindre enn 10 minutter.</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">11</context>
2020-12-08 11:58:43 +07:00
</context-group>
2022-07-07 16:40:18 +02:00
<note priority="1" from="description">mining.pools-luck-desc</note>
</trans-unit>
<trans-unit id="9740454c3c55ca2cfa437ff9ec07374c9b9d25b5" datatype="html">
<source>Pools count (1w)</source>
2023-03-09 11:49:26 +09:00
<target>Antall utvinningsgrupper (1uke)</target>
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2022-07-07 16:40:18 +02:00
<context context-type="linenumber">17</context>
2021-05-08 01:12:57 +04:00
</context-group>
2022-07-07 16:40:18 +02:00
<note priority="1" from="description">mining.miners-count-1w</note>
2021-05-08 01:12:57 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ade0bf412a0fae1e4672505fc1fa79ade185db05" datatype="html">
<source>Pools Count</source>
2024-01-13 16:57:03 +00:00
<target>Antall grupper</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">17</context>
</context-group>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">162</context>
2022-07-07 16:40:18 +02:00
</context-group>
<note priority="1" from="description">mining.miners-count</note>
</trans-unit>
<trans-unit id="500e13dffc7300bf7e4822a6bbf29a71a55d7b75" datatype="html">
<source>How many unique pools found at least one block over the past week.</source>
2022-10-17 16:21:29 +04:00
<target>Antall unike grupper som har funnet minst én blokk i løpet av den siste uken.</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">19</context>
2022-07-07 16:40:18 +02:00
</context-group>
<note priority="1" from="description">mining.pools-count-desc</note>
</trans-unit>
<trans-unit id="9ef8b357c32266f8423e24bf654006d3aa8fcd0b" datatype="html">
<source>Blocks (1w)</source>
<target>Blokker (1uke)</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
<context context-type="linenumber">25</context>
</context-group>
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">25</context>
2021-05-08 01:12:57 +04:00
</context-group>
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">168</context>
2021-05-08 01:12:57 +04:00
</context-group>
2022-07-07 16:40:18 +02:00
<note priority="1" from="description">master-page.blocks</note>
</trans-unit>
<trans-unit id="c9e8defa185fa8e342548958bf206de97afc97a6" datatype="html">
<source>The number of blocks found over the past week.</source>
2022-07-07 18:30:31 +00:00
<target>Antall blokker funnet den siste uken.</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">27</context>
2022-07-07 16:40:18 +02:00
</context-group>
<note priority="1" from="description">mining.blocks-count-desc</note>
2021-05-08 01:12:57 +04:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="3c3a423d91e36ac6624e909fcd2669a25685f847" datatype="html">
<source>Rank</source>
2022-06-08 00:44:04 +04:00
<target>Rang</target>
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">90</context>
2021-05-08 01:12:57 +04:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">27</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">53</context>
2022-10-17 16:21:29 +04:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">mining.rank</note>
2021-05-08 01:12:57 +04:00
</trans-unit>
2023-02-27 23:09:11 +04:00
<trans-unit id="c16d236667af327bd474b149cb909d1cd06fa50c" datatype="html">
<source>Avg Health</source>
<target>Gj.sn. helse</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">96</context>
2023-02-27 23:09:11 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">96</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">96</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">357</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">382</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">latest-blocks.avg_health</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="1d9f405ab98a5f79d98b439de29fc8baca46b97c" datatype="html">
<source>Avg Block Fees</source>
<target>Gj.sn. blokkavgift</target>
2021-05-08 01:12:57 +04:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">97</context>
2021-05-08 01:12:57 +04:00
</context-group>
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">17</context>
2021-01-21 12:39:33 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">17</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">53</context>
</context-group>
<note priority="1" from="description">mining.fees-per-block</note>
2021-01-21 12:39:33 +09:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="5d680aaa8e24bb235cf4fbeff3df0bfc8e2f564e" datatype="html">
<source>Empty Blocks</source>
2024-01-13 16:57:03 +00:00
<target>Tomme blokker</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">98</context>
2022-07-07 16:40:18 +02:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">mining.empty-blocks</note>
2022-07-07 16:40:18 +02:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="d720761d772947b9a6a0ae3f1c68b2e7119259cf" datatype="html">
<source>All miners</source>
<target>Alle utvinnere</target>
2022-07-07 16:40:18 +02:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">138</context>
2022-07-07 16:40:18 +02:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">mining.all-miners</note>
2022-07-07 16:40:18 +02:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="mining.mining-pools" datatype="html">
<source>Mining Pools</source>
2022-10-17 16:21:29 +04:00
<target>Utvinningsgrupper</target>
2021-01-21 12:39:33 +09:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">59</context>
2021-01-21 12:39:33 +09:00
</context-group>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.bitcoin.graphs.pool-ranking" datatype="html">
<source>See the top Bitcoin mining pools ranked by number of blocks mined, over your desired timeframe.</source>
2024-01-13 16:57:03 +00:00
<target>Se de beste utvinningsgruppene rangert etter antall blokker utvunnet, over ønsket tidsramme.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">60</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2023-03-14 14:54:49 +09:00
<trans-unit id="312539377512157124" datatype="html">
<source><x id="INTERPOLATION" equiv-text="i"/> blocks</source>
2023-03-22 13:35:16 +09:00
<target><x id="INTERPOLATION" equiv-text="i"/> blokker</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">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">167</context>
2021-12-26 11:15:19 +04:00
</context-group>
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">170</context>
2021-12-26 11:15:19 +04:00
</context-group>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">206</context>
2023-03-14 14:54:49 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">209</context>
2023-03-14 14:54:49 +09:00
</context-group>
</trans-unit>
<trans-unit id="3666195172774554282" datatype="html">
<source>Other (<x id="PH" equiv-text="percentage"/>)</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">186</context>
2023-03-14 14:54:49 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">204</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool-ranking/pool-ranking.component.ts</context>
<context context-type="linenumber">208</context>
2023-03-14 14:54:49 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.ts</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">119</context>
2023-03-14 14:54:49 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.ts</context>
<context context-type="linenumber">136</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">178</context>
2023-03-14 14:54:49 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">195</context>
2023-03-14 14:54:49 +09:00
</context-group>
2021-12-26 11:15:19 +04:00
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="2158ea60725d3a97aed6f0f00aa7df48d7bb42ff" datatype="html">
<source>mining pool</source>
2023-02-27 23:09:11 +04:00
<target>utvinningssamfunn</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">3</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">mining.pools</note>
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="cafc87479686947e2590b9f588a88040aeaf660b" datatype="html">
<source>Tags</source>
2022-06-08 00:44:04 +04:00
<target>Tagger</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">18</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">22</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">30</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">304</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">312</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">mining.tags</note>
</trans-unit>
<trans-unit id="meta.description.mining.pool" datatype="html">
<source>See mining pool stats for <x id="PH" equiv-text="poolStats.pool.name"/>: most recent mined blocks, hashrate over time, total block reward to date, known coinbase addresses, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Se utvinningsgruppe-statistikk for <x id="PH" equiv-text="poolStats.pool.name"/>: siste utvunnede blokker, hashrate over tid, total blokkbelønning hittil, kjente coinbaseadresser og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool-preview.component.ts</context>
<context context-type="linenumber">86</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">94</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
<trans-unit id="4eb84de23219c85432e38fb4fbdeb6c0f103ff8b" datatype="html">
<source>Show all</source>
<target>Vis alt</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">53</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">68</context>
</context-group>
2024-01-22 21:30:03 +07:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline.component.html</context>
<context context-type="linenumber">57</context>
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">129</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">169</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">287</context>
</context-group>
<note priority="1" from="description">show-all</note>
</trans-unit>
<trans-unit id="1eede69e18c5ac9c0b0295b72cabb7e64e029e74" datatype="html">
<source>Hide</source>
<target>Gjemm</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">55</context>
</context-group>
<note priority="1" from="description">hide</note>
</trans-unit>
<trans-unit id="cc657077942054572b255be033d634cf601c50b6" datatype="html">
<source>Hashrate (24h)</source>
<target>Hashrate (24t)</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">95</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">356</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">381</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">mining.hashrate</note>
</trans-unit>
<trans-unit id="3dc78651b2810cbb6e830fe7e57499d8cf6a8e4d" datatype="html">
<source>Blocks (24h)</source>
2024-01-13 16:57:03 +00:00
<target>Blokker (24 timer)</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">120</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">406</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">431</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">24h</note>
</trans-unit>
<trans-unit id="f7b50e4989540954a9035833470efba042a2819c" datatype="html">
<source>1w</source>
<target>1uke</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">121</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">407</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">432</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">1w</note>
</trans-unit>
<trans-unit id="c34fb298028c4e1089bdfc36c8324086fe8c0527" datatype="html">
<source>Out-of-band Fees (1w)</source>
2021-12-26 11:15:19 +04:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">143</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">1w</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="bb524ddbf557b5f14c391e4de3a1e6d28230d319" datatype="html">
<source>1m</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">144</context>
</context-group>
<note priority="1" from="description">1m</note>
</trans-unit>
<trans-unit id="65d447765db0bf3390e9b3ecce142bf34bb602a3" datatype="html">
<source>Mined</source>
<target>Utvunnet</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">183</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
<context context-type="linenumber">245</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/rbf-list/rbf-list.component.html</context>
<context context-type="linenumber">23</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<context context-type="linenumber">38</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">86</context>
2024-04-03 18:47:16 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">106</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">latest-blocks.mined</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="d7bb114523b22ee8330164224b11d75e62966539" datatype="html">
<source>Coinbase tag</source>
<target>Coinbase tagg</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">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">184</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/components/pool/pool.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">246</context>
2020-12-05 00:11:40 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">latest-blocks.coinbasetag</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2024-01-22 21:30:03 +07:00
<trans-unit id="7989855514418840406" datatype="html">
<source>Not enough data yet</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.ts</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">144</context>
2024-04-03 18:47:16 +09:00
</context-group>
</trans-unit>
<trans-unit id="8831611540421575858" datatype="html">
<source>Pool Dominance</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.ts</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">224</context>
2024-04-03 18:47:16 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/pool/pool.component.ts</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">278</context>
2024-01-22 21:30:03 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">mining.pool-dominance</note>
2024-01-22 21:30:03 +07:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="f13cbfe8cfc955918e9f64466d2cafddb4760d9a" datatype="html">
<source>Broadcast Transaction</source>
<target>Send transaksjon</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/push-transaction/push-transaction.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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/push-transaction/push-transaction.component.html</context>
<context context-type="linenumber">8</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">51</context>
2023-01-26 15:54:07 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">Broadcast Transaction</note>
<note priority="1" from="meaning">shared.broadcast-transaction</note>
</trans-unit>
<trans-unit id="7e93f7285e22e5a3c58cdde2205d4d2b5bfc079c" datatype="html">
<source>Transaction hex</source>
<target>Transaksjon i hex</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/push-transaction/push-transaction.component.html</context>
<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>
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">269</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">transaction.hex</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.title.push-tx" datatype="html">
<source>Broadcast Transaction</source>
2024-01-13 16:57:03 +00:00
<target>Kringkast transaksjon</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/push-transaction/push-transaction.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">33</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2021-04-26 04:05:55 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.push-tx" datatype="html">
<source>Broadcast a transaction to the <x id="PH" equiv-text="this.stateService.network==='liquid'||this.stateService.network==='liquidtestnet'?'Liquid':'Bitcoin'"/><x id="PH_1" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> network using the transaction's hash.</source>
2024-01-13 16:57:03 +00:00
<target>Kringkast en transaksjon til <x id="PH" equiv-text="this.stateService.network==='liquid'||this.stateService.network==='liquidtestnet'?'Liquid':'Bitcoin'"/><x id="PH_1" equiv-text="seoDescriptionNetwork(this.stateService.network)"/>-nettverket ved å bruke transaksjonens hash.</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/push-transaction/push-transaction.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">34</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
</trans-unit>
<trans-unit id="5e3d5a82750902f159122fcca487b07f1af3141f" datatype="html">
<source>RBF Replacements</source>
2024-01-13 16:57:03 +00:00
<target>RBF-erstatninger</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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/rbf-list/rbf-list.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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/rbf-list/rbf-list.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">60</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">page.rbf-replacements</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="8a9b3afe9486474f0d7767605fe99af99c8ea430" datatype="html">
<source>Full RBF</source>
2024-01-13 16:57:03 +00:00
<target>Full 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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/rbf-list/rbf-list.component.html</context>
<context context-type="linenumber">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>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<context context-type="linenumber">35</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">87</context>
2021-07-17 15:37:34 +03:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">transaction.full-rbf</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="c88914ee712e3ab5ad5f88de8a6ed12050919ccb" datatype="html">
<source>There are no replacements in the mempool yet!</source>
2024-01-13 16:57:03 +00:00
<target>Det er ingen erstatninger i mempoolen ennå!</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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/rbf-list/rbf-list.component.html</context>
<context context-type="linenumber">34</context>
2021-12-26 11:15:19 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">rbf.no-replacements-yet</note>
</trans-unit>
<trans-unit id="meta.description.rbf-list" datatype="html">
<source>See the most recent RBF replacements on the Bitcoin<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/> network, updated in real-time.</source>
2024-01-13 16:57:03 +00:00
<target>Se de siste RBF-erstatningene på Bitcoin<x id="PH" equiv-text="seoDescriptionNetwork(this.stateService.network)"/>-nettverket, oppdatert i sanntid.</target>
2021-12-26 11:15:19 +04:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/rbf-list/rbf-list.component.ts</context>
<context context-type="linenumber">61</context>
2021-04-26 04:05:55 +04: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>
2024-04-03 18:47:16 +09:00
<trans-unit id="f0e7d6d900658ee5ce66d8fef3637caf13891c53" datatype="html">
2023-11-26 17:00:34 +09:00
<source>RBF</source>
2024-01-13 16:57:03 +00:00
<target>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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<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>
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline-tooltip.component.html</context>
<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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.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>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">29</context>
2021-12-03 08:54:13 +09:00
</context-group>
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">88</context>
2021-12-03 08:54:13 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">RBF</note>
<note priority="1" from="meaning">tx-features.tag.rbf</note>
2021-12-03 08:54:13 +09:00
</trans-unit>
2024-01-22 21:30:03 +07:00
<trans-unit id="5403a767248e304199592271bba3366d2ca3f903" datatype="html">
<source>Show less</source>
<target>Vis mindre</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline.component.html</context>
<context context-type="linenumber">61</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">190</context>
2024-01-22 21:30:03 +07:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">130</context>
</context-group>
<note priority="1" from="description">show-less</note>
</trans-unit>
<trans-unit id="ea7c261363dc5f6134b7bacba2a1ef97f4ff7859" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ x }}"/> remaining</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/rbf-timeline/rbf-timeline.component.html</context>
<context context-type="linenumber">86</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">343</context>
</context-group>
<note priority="1" from="description">x-remaining</note>
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="e48f3277d241b5e74b6e01a989a4ecb4495d3d25" datatype="html">
<source>Miners Reward</source>
2022-07-07 16:40:18 +02:00
<target>Utvinnerbelønning</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2022-07-07 16:40:18 +02:00
<context context-type="linenumber">5</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">5</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">46</context>
2022-05-19 20:12:21 +04:00
</context-group>
<note priority="1" from="description">mining.rewards</note>
</trans-unit>
<trans-unit id="79b0842a2010172290ad09062bf51f09d8842f65" datatype="html">
<source>Amount being paid to miners in the past 144 blocks</source>
2022-06-08 00:44:04 +04:00
<target>Beløp som er betalt til utvinnere for de siste 144 blokkene</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">6</context>
2022-05-19 20:12:21 +04:00
</context-group>
<note priority="1" from="description">mining.rewards-desc</note>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="a0d4ab5b063e7be1c9ea980f5fd6ce1b5384ad0b" datatype="html">
<source>Average fees per block in the past 144 blocks</source>
2023-02-27 23:09:11 +04:00
<target>Gjennomsnittlige avgifter per blokk i de siste 144 blokkene</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">18</context>
2022-05-19 20:12:21 +04:00
</context-group>
2023-01-26 15:54:07 +04:00
<note priority="1" from="description">mining.fees-per-block-desc</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="0705223420d290a218e4ed83bd4d904454a9cee8" datatype="html">
<source>BTC/block</source>
2023-02-27 23:09:11 +04:00
<target>BTC/blokk</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">21</context>
2022-05-19 20:12:21 +04:00
</context-group>
2023-01-26 15:54:07 +04:00
<note priority="1" from="description">BTC/block</note>
<note priority="1" from="meaning">shared.btc-block</note>
2022-05-19 20:12:21 +04:00
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="cf3a97b1c1546b843411cfe101bc55ba2ac46bac" datatype="html">
<source>Avg Tx Fee</source>
2023-02-27 23:09:11 +04:00
<target>Gj.sn. Tx-avgift</target>
2022-05-30 13:26:54 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2022-07-07 16:40:18 +02:00
<context context-type="linenumber">30</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">30</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
<context context-type="linenumber">60</context>
2022-05-30 13:26:54 +04:00
</context-group>
<note priority="1" from="description">mining.average-fee</note>
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="8be96dc461529381c812f64962c62f4228d01470" datatype="html">
<source>Fee paid on average for each transaction in the past 144 blocks</source>
2022-06-08 00:44:04 +04:00
<target>Avgift betalt i gjennomsnitt for hver transaksjon i de siste 144 blokkene</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">31</context>
2022-05-19 20:12:21 +04:00
</context-group>
<note priority="1" from="description">mining.average-fee</note>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="31443c29cb161e8aa661eb5035f675746ef95b45" datatype="html">
<source>sats/tx</source>
<target>sats/tx</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/reward-stats/reward-stats.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">33</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">sat/vB</note>
<note priority="1" from="meaning">shared.sat-vbyte</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="7deec1c1520f06170e1f8e8ddfbe4532312f638f" datatype="html">
<source>Explore the full Bitcoin ecosystem</source>
2023-02-27 23:09:11 +04:00
<target>Utforsk hele Bitcoin-økosystemet</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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/search-form/search-form.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">4</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
<context context-type="linenumber">11</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">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>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">search-form.searchbar-placeholder</note>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="7e892ba15f2c6c17e83510e273b3e10fc32ea016" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Search</source>
<target>Søk</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/search-form/search-form.component.html</context>
2023-11-26 17:00:34 +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>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">search-form.search-title</note>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="920339d7b35b44632c8ec42aa2bd2cf5929e7619" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ networkName }}"/> Block Height</source>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
<context context-type="linenumber">3</context>
</context-group>
<note priority="1" from="description">search.bitcoin-block-height</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="c6a48e5ee096fba914fb4927d16a5d2e0941e0fe" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ networkName }}"/> Transaction</source>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">21</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">search.bitcoin-transaction</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="1f8b2a9743e513d1e645f6986bae2130e914c34b" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ networkName }}"/> Address</source>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">27</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">search.bitcoin-address</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="ba18d02396f5998bb46cd5d771de107bfab6e177" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ networkName }}"/> Block</source>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">33</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">search.bitcoin-block</note>
</trans-unit>
2024-01-22 21:30:03 +07:00
<trans-unit id="fabeb487dec2ef8dc70cdaee28eacf9d76e78352" datatype="html">
<source>Other Network Address</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
<context context-type="linenumber">39</context>
</context-group>
<note priority="1" from="description">search.other-networks</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="1221b439226cb36736030a9398c7c3a07d61bdb4" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ networkName }}"/> Addresses</source>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">47</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">search.bitcoin-addresses</note>
</trans-unit>
<trans-unit id="67f25165b857428d046fe5eb67fc44c5c3d94e87" datatype="html">
<source>Lightning Nodes</source>
<target>Ligthning-noder</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">55</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">search.lightning-nodes</note>
</trans-unit>
<trans-unit id="db5ca37068eaee3f8b909d3b8b476164527cd8c3" datatype="html">
<source>Lightning Channels</source>
<target>Lightning-kanaler</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">63</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">search.lightning-channels</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="f091ae234382282726f5a93bb7b3802ed468e8b9" datatype="html">
<source>Liquid Asset</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
<context context-type="linenumber">71</context>
</context-group>
<note priority="1" from="description">search.liquid-asset</note>
</trans-unit>
2023-02-27 23:09:11 +04:00
<trans-unit id="2abc4d0d3ae0b49fa9e94a2efb8c2e1a47e680f4" datatype="html">
<source>Go to "<x id="INTERPOLATION" equiv-text="{{ x }}"/>"</source>
2023-03-08 16:26:56 +09:00
<target>Gå til "<x id="INTERPOLATION" equiv-text="{{ x }}"/>"</target>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/search-form/search-results/search-results.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">78</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">search.go-to</note>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="75c20c8a9cd9723d45bee0230dd582d7c2e4ecbc" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Mempool by vBytes (sat/vByte)</source>
<target>Mempool i vBytes (sat/vByte)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
2022-05-19 20:12:21 +04:00
<context context-type="linenumber">7</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">statistics.memory-by-vBytes</note>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="d0e134a0886ae71207e912575d226525062b62f1" datatype="html">
<source>Clock (Mempool)</source>
2024-01-13 16:57:03 +00:00
<target>Klokke (Mempool)</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
<context context-type="linenumber">17</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">75</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.clock-mempool</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="46ce8155c9ab953edeec97e8950b5a21e67d7c4e" datatype="html">
<source>TV view</source>
<target>TV-modus</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">20</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/television/television.component.ts</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">39</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">master-page.tvview</note>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="5ca707824ab93066c7d9b44e1b8bf216725c2c22" datatype="html">
2021-12-03 08:54:13 +09:00
<source>Filter</source>
2021-12-26 11:15:19 +04:00
<target>Filter</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">68</context>
2021-12-03 08:54:13 +09:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">statistics.component-filter.title</note>
2021-12-03 08:54:13 +09:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="add9d52e5bf541c941df44e251a5c1cafcc92e9d" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Invert</source>
<target>Inverter</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">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>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">statistics.component-invert.title</note>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="dc15ec15e6206b40133f2c1b06095ce75aaee1ef" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Transaction vBytes per second (vB/s)</source>
<target>Transaksjoner per sekund (vB/s)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">114</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">statistics.transaction-vbytes-per-second</note>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="68d44b7bd049ae93c2bc15973eb5266aec64693e" datatype="html">
<source>Cap outliers</source>
2024-01-13 16:57:03 +00:00
<target>Fjern avvikere</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.html</context>
<context context-type="linenumber">122</context>
</context-group>
<note priority="1" from="description">statistics.cap-outliers</note>
</trans-unit>
<trans-unit id="meta.description.bitcoin.graphs.mempool" datatype="html">
<source>See mempool size (in MvB) and transactions per second (in vB/s) visualized over time.</source>
2024-01-13 16:57:03 +00:00
<target>Se mempoolstørrelse (i MvB) og transaksjoner per sekund (i vB/s) visualisert over tid.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/statistics/statistics.component.ts</context>
<context context-type="linenumber">67</context>
</context-group>
</trans-unit>
<trans-unit id="meta.description.tv" datatype="html">
<source>See Bitcoin blocks and mempool congestion in real-time in a simplified format perfect for a TV.</source>
2024-01-13 16:57:03 +00:00
<target>Se Bitcoin-blokker og mempool i sanntid i et forenklet format perfekt for en TV.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/television/television.component.ts</context>
<context context-type="linenumber">40</context>
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="date-base.immediately" datatype="html">
<source>Immediately</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">90</context>
</context-group>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="date-base.just-now" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Just now</source>
2021-07-27 19:51:38 +03:00
<target>Akkurat nå</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">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>
</trans-unit>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="dateStrings.i18nYear"/> siden</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">145</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">146</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">147</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">148</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">149</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">150</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">151</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">155</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">156</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">157</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf 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">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">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>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">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>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">160</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">161</context>
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
2023-03-14 14:54:49 +09:00
<trans-unit id="time-until" datatype="html">
<source>In ~<x id="DATE" equiv-text="dateStrings.i18nYear"/></source>
2023-03-22 13:35:16 +09:00
<target>Om ~<x id="DATE" equiv-text="dateStrings.i18nYear"/></target>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">168</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">169</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">170</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">171</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">172</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">173</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">174</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">178</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">179</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">180</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">181</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">182</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">183</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">184</context>
</context-group>
</trans-unit>
<trans-unit id="time-span" datatype="html">
<source>After <x id="DATE" equiv-text="dateStrings.i18nYear"/></source>
<target>Etter <x id="DATE" equiv-text="dateStrings.i18nYear"/></target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">191</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">192</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
<context context-type="linenumber">193</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">194</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">195</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">196</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">197</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">201</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">202</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">203</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">204</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">205</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">206</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">207</context>
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="time-before" datatype="html">
<source><x id="DATE" equiv-text="dateStrings.i18nYear"/> before</source>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">214</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">215</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">216</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">217</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">218</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">219</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">220</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">224</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">225</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">226</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">227</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">228</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">229</context>
2021-07-17 15:37:34 +03:00
</context-group>
2021-08-03 18:38:34 +03:00
<context-group purpose="location">
2023-03-14 14:54:49 +09:00
<context context-type="sourcefile">src/app/components/time/time.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">230</context>
2021-08-03 18:38:34 +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
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="7e06b8dd9f29261827018351cd71efe1c87839de" datatype="html">
<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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction-preview.component.html</context>
<context context-type="linenumber">43</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">502</context>
2024-04-03 18:47:16 +09:00
</context-group>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">54</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">19</context>
2023-01-26 15:54:07 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">transactions-list.coinbase</note>
2023-01-26 15:54:07 +04:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="bisq.transaction.browser-title" datatype="html">
<source>Transaction: <x id="INTERPOLATION" equiv-text="this.txId"/></source>
<target>Transaksjon: <x id="INTERPOLATION" equiv-text="this.txId"/></target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction-preview.component.ts</context>
<context context-type="linenumber">89</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.ts</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">417</context>
2024-04-03 18:47:16 +09:00
</context-group>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.bitcoin.transaction" datatype="html">
2024-01-22 21:30:03 +07:00
<source>Get real-time status, addresses, fees, script info, and more for <x id="PH" equiv-text="network"/><x id="PH_1" equiv-text="seoDescription"/> transaction with txid <x id="PH_2" equiv-text="this.txId"/>.</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">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction-preview.component.ts</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">93</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.ts</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">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>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="0094b97dd052620710f173e7aedf6807a1eba1f5" datatype="html">
<source>This transaction has been replaced by:</source>
<target>Denne transaksjonen har blitt byttet ut med:</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">5</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">RBF replacement</note>
<note priority="1" from="meaning">transaction.rbf.replacement</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2024-04-09 16:58:02 +09:00
<trans-unit id="ec972116b4da9e2c5bc0e6e6586061d60cd13e56" datatype="html">
<source>Hide accelerator</source>
2024-04-03 18:47:16 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">84</context>
2024-04-03 18:47:16 +09:00
</context-group>
2024-04-09 16:58:02 +09:00
<note priority="1" from="description">hide-accelerator</note>
</trans-unit>
<trans-unit id="f61c6867295f3b53d23557021f2f4e0aa1d0b8fc" datatype="html">
<source>Type</source>
<target>Type</target>
2024-04-03 18:47:16 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">101</context>
2024-04-03 18:47:16 +09:00
</context-group>
<context-group purpose="location">
2024-04-09 16:58:02 +09:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
<context context-type="linenumber">276</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">transactions-list.vout.scriptpubkey-type</note>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="dd230222e3ae689913445ce93b6ae3f7cce7458b" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Descendant</source>
<target>Etterkommer</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">112</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">124</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Descendant</note>
<note priority="1" from="meaning">transaction.descendant</note>
2021-02-03 15:30:38 +07:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="8c16167a5d7c96d14ff280b09de312d18d5e2511" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Ancestor</source>
<target>Forfader</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">136</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">Transaction Ancestor</note>
<note priority="1" from="meaning">transaction.ancestor</note>
2021-02-03 15:30:38 +07:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="03721a62015a76e794be64ba2b7e053e801215ea" datatype="html">
<source>RBF History</source>
2024-01-13 16:57:03 +00:00
<target>RBF historie</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">155</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">RBF History</note>
<note priority="1" from="meaning">transaction.rbf-history</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="53fbdc20554c4e68ae509f652b38ab80021c0739" datatype="html">
<source>Flow</source>
2023-11-26 17:00:34 +09:00
<target>Strøm</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">164</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">284</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">Transaction flow</note>
<note priority="1" from="meaning">transaction.flow</note>
</trans-unit>
<trans-unit id="d0fd8887b50687cfc0fc1f6569f6fd6c5db4ffc0" datatype="html">
<source>Hide diagram</source>
2023-02-27 23:09:11 +04:00
<target>Skjul diagram</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">167</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">hide-diagram</note>
</trans-unit>
<trans-unit id="f0c5f6f270e70cbe063b5368fcf48f9afc1abd9b" datatype="html">
<source>Show more</source>
2023-02-27 23:09:11 +04:00
<target>Vis mer</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">188</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">171</context>
2023-01-26 15:54:07 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">289</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">show-more</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="31d8d7f29ddbd3f64d374a132ddacd5e4a0835a2" datatype="html">
<source>Inputs & Outputs</source>
<target>Innganger & Utganger</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">206</context>
2024-04-03 18:47:16 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">315</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">Transaction inputs and outputs</note>
<note priority="1" from="meaning">transaction.inputs-and-outputs</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="e7aa6db8df12d0158df972b6abfc65a8478b2b7d" datatype="html">
<source>Show diagram</source>
2023-02-27 23:09:11 +04:00
<target>Vis diagram</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">210</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">show-diagram</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="a8a4dd861f790141e19f773153cf42b5d0b0e6b6" datatype="html">
<source>Adjusted vsize</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">235</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">Transaction Adjusted VSize</note>
<note priority="1" from="meaning">transaction.adjusted-vsize</note>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="516a786e59a57efaf80e11370b4bade400f19445" datatype="html">
2021-12-03 08:54:13 +09:00
<source>Locktime</source>
2021-12-26 11:15:19 +04:00
<target>Locktime</target>
2021-08-03 18:38:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">257</context>
2021-08-03 18:38:34 +03:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.locktime</note>
2021-08-03 18:38:34 +03:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="3dd65e8fa7035988a691aadcb583862c2a9e336a" datatype="html">
<source>Sigops</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">261</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">Transaction Sigops</note>
<note priority="1" from="meaning">transaction.sigops</note>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="c9d9612bcd520103486b5fc84d84c9476a1b7f78" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Transaction not found.</source>
<target>Transaksjon ikke funnet</target>
2021-04-26 05:37:03 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">393</context>
2021-04-26 05:37:03 +09:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.error.transaction-not-found</note>
2021-02-03 15:30:38 +07:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="66b65556acb90d8764fe166a260af0309671698c" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Waiting for it to appear in the mempool...</source>
<target>Venter på at den kommer inn i mempool...</target>
2021-02-03 15:30:38 +07:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">394</context>
2021-02-03 15:30:38 +07:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transaction.error.waiting-for-it-to-appear</note>
2021-02-03 15:30:38 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="8a736bd53341b2dedaf9cdcfd9d1093cc16cb12c" datatype="html">
<source>Error loading transaction data.</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">400</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">transaction.error.loading-transaction-data</note>
</trans-unit>
2024-04-09 16:58:02 +09:00
<trans-unit id="885666551418fd59011ceb09d5c481095940193b" datatype="html">
<source>Features</source>
<target>Funksjoner</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">481</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
<context context-type="linenumber">120</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/filters.utils.ts</context>
<context context-type="linenumber">118</context>
</context-group>
<note priority="1" from="description">Transaction features</note>
<note priority="1" from="meaning">transaction.features</note>
</trans-unit>
<trans-unit id="bbd31e1edb0c089cca11d3d718b6588f3496e9e1" datatype="html">
<source>This transaction was projected to be included in the block</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">504</context>
</context-group>
<note priority="1" from="description">Expected in block tooltip</note>
</trans-unit>
<trans-unit id="e75410f8ab03085a3dbecf82de6acd9679fefb75" datatype="html">
<source>Expected in Block</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">504</context>
</context-group>
<note priority="1" from="description">Expected in Block</note>
<note priority="1" from="meaning">tx-features.tag.expected</note>
</trans-unit>
<trans-unit id="2533fb35288295dac23fe0bdfcc2685b025a9f2e" datatype="html">
<source>This transaction was seen in the mempool prior to mining</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">506</context>
</context-group>
<note priority="1" from="description">Seen in mempool tooltip</note>
</trans-unit>
<trans-unit id="08c516e1fe345b4ae1fcae5fd4e5a0cd22e646dd" datatype="html">
<source>Seen in Mempool</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">506</context>
</context-group>
<note priority="1" from="description">Seen in Mempool</note>
<note priority="1" from="meaning">tx-features.tag.seen</note>
</trans-unit>
<trans-unit id="5f79b588d43d16312a9a2e6df1e76922ffe3c45d" datatype="html">
<source>This transaction was missing from our mempool prior to mining</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">508</context>
</context-group>
<note priority="1" from="description">Not seen in mempool tooltip</note>
</trans-unit>
<trans-unit id="53d5fe49e4a07a663eb2f26ceeb76afceef86334" datatype="html">
<source>Not seen in Mempool</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">508</context>
</context-group>
<note priority="1" from="description">Not seen in Mempool</note>
<note priority="1" from="meaning">tx-features.tag.not-seen</note>
</trans-unit>
<trans-unit id="500acb5f67d1f175e1d5dd666c7b15c66611e411" datatype="html">
<source>This transaction may have been added out-of-band</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">511</context>
</context-group>
<note priority="1" from="description">Added transaction tooltip</note>
</trans-unit>
<trans-unit id="0badd8c91194cb72dd79e12955d4ed4b43a7cf41" datatype="html">
<source>This transaction may have been prioritized out-of-band</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">514</context>
</context-group>
<note priority="1" from="description">Prioritized transaction tooltip</note>
</trans-unit>
<trans-unit id="7ef1a8a56ad5696e527a8da06a13661f883ad6b2" datatype="html">
<source>This transaction conflicted with another version in our mempool</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">517</context>
</context-group>
<note priority="1" from="description">Conflict in mempool tooltip</note>
</trans-unit>
<trans-unit id="4e738ef3d2b4878f17f43002204f7b31aabb8e87" datatype="html">
<source>ETA</source>
<target>ETA</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">533</context>
</context-group>
<note priority="1" from="description">Transaction ETA</note>
<note priority="1" from="meaning">transaction.eta</note>
</trans-unit>
<trans-unit id="f9bad781ea9c5192160516ca55ddc5edc307ef07" datatype="html">
<source>In several hours (or more)</source>
<target>Om flere timer(eller mer)</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
<context context-type="linenumber">539</context>
</context-group>
<note priority="1" from="description">Transaction ETA in several hours or more</note>
<note priority="1" from="meaning">transaction.eta.in-several-hours</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="8b01e0411c7160bfee109e504c84ecee5079c326" datatype="html">
<source>Accelerated fee rate</source>
2024-01-13 16:57:03 +00:00
<target>Akselerert gebyrsats</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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transaction/transaction.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">617</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">Accelerated transaction fee rate</note>
<note priority="1" from="meaning">transaction.accelerated-fee-rate</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="7d745f2569c4ddc2992529f00ed991e36dada39a" datatype="html">
2021-04-26 04:05:55 +04:00
<source>(Newly Generated Coins)</source>
<target>(Nygenererte Mynter)</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">54</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
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>
2021-12-26 11:15:19 +04:00
<trans-unit id="5de25175982d51c72d25bd79933e7b412d51e343" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Peg-in</source>
<target>Peg-inn</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">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>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.peg-in</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="23f4a0693bc0ad8dbdccfc0b04238edfaf846bc5" datatype="html">
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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">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>
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>
2021-12-26 11:15:19 +04:00
<trans-unit id="3a5a04628e57fd93cfce206ccbc1432fed0925d3" datatype="html">
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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">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>
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>
2020-12-05 00:11:40 +09:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="c64b73564fd858ee5a4f73040893c9d625ca56ad" datatype="html">
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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">114</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
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>
2021-12-26 11:15:19 +04:00
<trans-unit id="a8bc418b73c6bfcefc1b07c84d7f1126ab2a3237" datatype="html">
2021-04-26 04:05:55 +04:00
<source>P2SH redeem script</source>
<target>P2SH redeem script</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">137</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.p2sh-redeem-script</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="d4b97cae5fffc21333bed5d04a95e103650ebfb2" datatype="html">
<source>P2TR tapscript</source>
2022-06-08 00:44:04 +04:00
<target>P2TR tapscript</target>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">141</context>
2022-05-19 20:12:21 +04:00
</context-group>
<note priority="1" from="description">transactions-list.p2tr-tapscript</note>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="e1d63108bdf06fa14ec13f038e23eebd4d391b16" datatype="html">
2021-04-26 04:05:55 +04:00
<source>P2WSH witness script</source>
<target>P2WSH witness script</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">143</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
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>
2021-12-26 11:15:19 +04:00
<trans-unit id="cb49c3831dcaed1b6ccaf5efe58730cf29a5d15d" datatype="html">
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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">148</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.nsequence</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="26cdad3f9e94369ff12c5c628d8eb5c724e3acb3" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Previous output script</source>
2021-05-08 01:12:57 +04:00
<target>Forrige utgangs-script</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">153</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
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>
2021-12-26 11:15:19 +04:00
<trans-unit id="e7699861471f18a60e583512c45d84b388cfa120" datatype="html">
2021-12-03 08:54:13 +09:00
<source>Previous output type</source>
2021-12-26 11:15:19 +04:00
<target>Tidligere utdatatype</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">157</context>
2021-12-03 08:54:13 +09:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.previous-output-type</note>
2021-12-03 08:54:13 +09:00
</trans-unit>
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="<ng-container *ngTemplateOutlet="pegOutLink">"/><x id="CLOSE_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="</ng-contain"/></source>
<target>Peg-out til <x id="START_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="<ng-container *ngTemplateOutlet="pegOutLink">"/> <x id="CLOSE_TAG_NG_CONTAINER" ctype="x-ng_container" equiv-text="</ng-contain"/></target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">205,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>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">transactions-list.peg-out-to</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="4bdf69370ca8b0cae3a17d7b84b59c49cd57288d" datatype="html">
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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">264</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
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>
2021-12-26 11:15:19 +04:00
<trans-unit id="e191b4f47f3ea7532f83fd498f4860db664ab75c" datatype="html">
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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">268</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
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>
2020-12-05 00:11:40 +09:00
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="d70397ee91f6c9ec91f1c1dff88126f8f9b7c2c4" datatype="html">
<source>Show more inputs to reveal fee data</source>
2023-02-27 23:09:11 +04:00
<target>Vis mer inndata for å avsløre avgiftsdata</target>
2022-05-30 13:26:54 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/transactions-list/transactions-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">306</context>
2022-05-30 13:26:54 +04:00
</context-group>
<note priority="1" from="description">transactions-list.load-to-reveal-fee-info</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="ac0c4b49e44c42db35ddf590fb5f78375a891b01" datatype="html">
<source>other inputs</source>
2023-02-27 23:09:11 +04:00
<target>andre innganger</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">
2022-10-17 16:21:29 +04:00
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">12</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<note priority="1" from="description">transaction.other-inputs</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="8900247c0476fea8fcbee57a72a1d1da5ddd40ff" datatype="html">
<source>other outputs</source>
2023-02-27 23:09:11 +04:00
<target>andre utganger</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2022-10-17 16:21:29 +04:00
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">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>
2022-10-17 16:21:29 +04:00
<note priority="1" from="description">transaction.other-outputs</note>
</trans-unit>
<trans-unit id="3e242f213dd1a0754aad9164aa80887d67708500" datatype="html">
<source>Input</source>
2023-02-27 23:09:11 +04:00
<target>Inngang</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">
2022-10-17 16:21:29 +04:00
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">42</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">86</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">transaction.input</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="395b6ec0ab68cd45fad7ab791393d85d4077f94b" datatype="html">
<source>1 block earlier</source>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">123</context>
2023-01-26 15:54:07 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.one-block-earlier</note>
</trans-unit>
<trans-unit id="f6f7403b9d7495e7282520b50133c3c3843a6b62" datatype="html">
<source>1 block later</source>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">127</context>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">shared.one-block-later</note>
</trans-unit>
<trans-unit id="84c7fcc1f282a501eb33fc17a8b2bda177de5a7e" datatype="html">
<source>in the same block</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">131</context>
</context-group>
<note priority="1" from="description">shared.in-the-same-block</note>
</trans-unit>
<trans-unit id="95bf37451da5bff541c9380f803a695f2aac28a2" datatype="html">
<source>blocks earlier</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">137</context>
</context-group>
<note priority="1" from="description">shared.n-blocks-earlier</note>
</trans-unit>
<trans-unit id="5a67f718fe7d4f423417d1c0162f1afb24e9dac8" datatype="html">
<source>spent </source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">148</context>
</context-group>
<note priority="1" from="description">shared.spent</note>
</trans-unit>
<trans-unit id="21ea333dd6a24e18e5af771634afbaeeeb369a8d" datatype="html">
<source>blocks later</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-bowtie-graph-tooltip/tx-bowtie-graph-tooltip.component.html</context>
<context context-type="linenumber">150</context>
</context-group>
<note priority="1" from="description">shared.n-blocks-later</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
<trans-unit id="25d58cd5c18fd9c1c89d6062d67dcc2482161410" datatype="html">
<source>This transaction saved <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedSegwitGains * 100 | number: '1.0-0' }}"/>% on fees by using native SegWit</source>
2023-03-22 13:35:16 +09:00
<target>Denne transaksjonen sparte <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedSegwitGains * 100 | number: '1.0-0' }}"/>% på avgifter ved å bruke native 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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
2022-10-17 16:21:29 +04:00
<context context-type="linenumber">2</context>
</context-group>
<note priority="1" from="description">ngbTooltip about segwit gains</note>
</trans-unit>
<trans-unit id="0ca27703757bf9a636a0b9b61e6a0cf248781cb4" datatype="html">
<source>SegWit</source>
<target>SegWit</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">2</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">4</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<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>
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>
2022-10-17 16:21:29 +04:00
<trans-unit id="b6a3f6afdac6873e2d261647d834c02c91376893" datatype="html">
<source>This transaction saved <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedSegwitGains * 100 | number: '1.0-0' }}"/>% on fees by using SegWit and could save <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialSegwitGains * 100 | number : '1.0-0' }}"/>% more by fully upgrading to native SegWit</source>
2023-03-22 13:35:16 +09:00
<target>Denne transaksjonen sparte <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedSegwitGains * 100 | number: '1.0-0' }}"/>% på avgifter ved å bruke SegWit og kunne spart <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialSegwitGains * 100 | number : '1.0-0' }}"/>% mer ved å fullstendig oppgradere til native 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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
2022-10-17 16:21:29 +04:00
<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>
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>
2022-10-17 16:21:29 +04:00
<trans-unit id="a67530e246368aa7e5d010061fd84c3c4fe755c2" datatype="html">
<source>This transaction could save <x id="INTERPOLATION" equiv-text="{{ segwitGains.potentialSegwitGains * 100 | number : '1.0-0' }}"/>% on fees by upgrading to native SegWit or <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialP2shSegwitGains * 100 | number: '1.0-0' }}"/>% by upgrading to SegWit-P2SH</source>
2023-03-22 13:35:16 +09:00
<target>Denne transaksjonen kan spare <x id="INTERPOLATION" equiv-text="{{ segwitGains.potentialSegwitGains * 100 | number : '1.0-0' }}"/>% på avgifter ved å oppgradere til native SegWit eller <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialP2shSegwitGains * 100 | number: '1.0-0' }}"/>% ved å oppgradere til SegWit-P2SH</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
2022-10-17 16:21:29 +04: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>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">ngbTooltip about missed out gains</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="17e9c05e053cbd29d3835d8ecb19508d0f07241b" datatype="html">
<source>This transaction uses Taproot and thereby saved at least <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedTaprootGains * 100 | number: '1.0-0' }}"/>% on fees</source>
2023-03-22 13:35:16 +09:00
<target>Denne transaksjonen bruker Taproot og sparer dermed minst <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedTaprootGains * 100 | number: '1.0-0' }}"/>% på avgifter</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
2022-10-17 16:21:29 +04:00
<context context-type="linenumber">12</context>
2021-12-03 08:54:13 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<note priority="1" from="description">Tooltip about fees saved with taproot</note>
2021-12-03 08:54:13 +09:00
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="47b821c7df420c96de0b22844a88c04d52628540" datatype="html">
<source>This transaction uses Taproot and already saved at least <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedTaprootGains * 100 | number: '1.0-0' }}"/>% on fees, but could save an additional <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialTaprootGains * 100 | number: '1.0-0' }}"/>% by fully using Taproot</source>
2023-03-22 13:35:16 +09:00
<target>Denne transaksjonen bruker Taproot og har allerede spart minst <x id="INTERPOLATION" equiv-text="{{ segwitGains.realizedTaprootGains * 100 | number: '1.0-0' }}"/>% på avgifter, men kan spare ytterligere <x id="INTERPOLATION_1" equiv-text="{{ segwitGains.potentialTaprootGains * 100 | number: '1.0-0' }}"/>% ved å bruke Taproot fullt ut</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">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
2022-10-17 16:21:29 +04:00
<context context-type="linenumber">14</context>
</context-group>
<note priority="1" from="description">Tooltip about fees that saved and could be saved with taproot</note>
</trans-unit>
<trans-unit id="aa31fc4d29f35b2fd36080bb6ff84be8eaab66fd" datatype="html">
<source>This transaction could save <x id="INTERPOLATION" equiv-text="{{ segwitGains.potentialTaprootGains * 100 | number: '1.0-0' }}"/>% on fees by using Taproot</source>
2023-03-22 13:35:16 +09:00
<target>Denne transaksjonen kunne spart <x id="INTERPOLATION" equiv-text="{{ segwitGains.potentialTaprootGains * 100 | number: '1.0-0' }}"/>% på avgifter ved å bruke Taproot</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">16</context>
</context-group>
<note priority="1" from="description">Tooltip about fees that could be saved with taproot</note>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="b0fb884cf71b19e3a4d146146d260ccedd9d50a5" datatype="html">
<source>This transaction does not use Taproot</source>
2023-02-27 23:09:11 +04:00
<target>Denne transaksjonen bruker ikke Taproot</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
<context context-type="linenumber">18</context>
</context-group>
<note priority="1" from="description">Tooltip about using taproot</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="e6da407140d70e08b6fba731455f8e0d72f900b5" datatype="html">
<source>This transaction uses Taproot</source>
<target>Denne transaksjonen bruker Taproot</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">21</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">Tooltip about taproot</note>
</trans-unit>
<trans-unit id="07883574bb93ea23b764861f56a525bdaf907513" datatype="html">
<source>This transaction supports Replace-By-Fee (RBF) allowing fee bumping</source>
2023-02-27 23:09:11 +04:00
<target>Denne transaksjonen støtter Replace-By-Fee (RBF) som tillater avgiftsendring</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
2023-01-26 15:54:07 +04:00
<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>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">RBF tooltip</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="85ce9e4f45873116b746899169cbc3445321d60c" datatype="html">
2021-04-26 04:05:55 +04:00
<source>This transaction does NOT support Replace-By-Fee (RBF) and cannot be fee bumped using this method</source>
<target>Denne transaksjonen støtter IKKE Replace-By-Fee (RBF), avgiften kan derfor ikke endres.</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/components/tx-features/tx-features.component.html</context>
2023-01-26 15:54:07 +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>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">RBF disabled tooltip</note>
2021-04-26 04:05:55 +04:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="b2035d486e8d59980736a224891d9790c981691a" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Optimal</source>
<target>Optimal</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
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>
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>
2020-12-05 00:11:40 +09:00
</trans-unit>
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>
2023-03-22 13:35:16 +09:00
<target>Bare ~<x id="INTERPOLATION" equiv-text="{{ medianFeeNeeded | feeRounding }}"/> sat/vB var nødvendig for å komme inn i denne blokken</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
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>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
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>
2020-12-05 00:11:40 +09:00
</context-group>
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>
2021-12-26 11:15:19 +04:00
<trans-unit id="0fa66b0c410bef320d3f370d7c98c51754b5f28f" datatype="html">
<source>Overpaid <x id="INTERPOLATION" equiv-text="{{ overpaidTimes }}"/>x</source>
2023-03-22 13:35:16 +09:00
<target>Overbetalt <x id="INTERPOLATION" equiv-text="{{ overpaidTimes }}"/>x</target>
Implement i18n support in frontend using Angular + Transifex + NGINX
This PR adds basic i18n support into the mempool frontend, together with
a smooth workflow for developers and translators to collaborate:
* Using the existing @angular/localize module, developers add i18n
metadata to any frontend strings their new features or changes modify
* Using the new npm script `i18n-extract-from-source`, developers
extract the i18n data from source code into `src/locale/messages.xlf`
* After pushing the updated `src/locale/messages.xlf` to GitHub, the
Transifex service will update its database from the new source data
* Using the Transifex website UI, translators can work together to
translate all the mempool frontend strings into their native languages
* Using the new npm script `i18n-pull-from-transifex`, developers can
pull in completed translations from Transifex, and commit them into git.
This flow requires an API key from Transifex, which can be obtained at
https://www.transifex.com/user/settings/api/ to be used with the python
script installed by `pip install transifex-client` - after preparing
these, run the npm script which will ask you for the API key the first
time. When downloading is complete, you can test building the frontend,
and if successful, commit the new strings files into git.
This PR implements a new locale selector in the footer of the homepage
dashboard, and includes WIP translations for the following languages:
* Czech (cs)
* German (de)
* Japanese (ja)
* Norwegian (nn)
* Spanish (es)
* Swedish (sv)
* Ukrainian (uk)
* Persian (fa)
* Portugese (pt)
* Turkish (tr)
* Dutch (nl)
* French (fr)
* Chinese (zh)
* Slovenian (sl)
* Korean (ko)
* Polish (pl)
The user-agent's `Accept-Language` header is used to automatically
detect their preferred language, which can be manually overriden by the
pull-down selector, which saves their preference to a cookie, which is
used by nginx to serve the correct HTML bundle to the user.
Remaining tasks include adding i18n metadata for strings in the Bisq and
Liquid frontend code, mouseover hover tooltip strings, hard-coded og
metadata inside HTML templates, and many other places. This will be done
in a separate PR.
When upgrading to add i18n support, mempool instance operators must take
care to install the new nginx.conf and nginx-mempool.conf files, and
tweak for their specific site configuration.
Fixes #81
2020-12-02 04:19:33 +09:00
<context-group purpose="location">
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">
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>
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>
2021-04-26 04:05:55 +04:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="86d26b45470e43b409e589517922276109138e87" datatype="html">
2021-07-27 19:51:38 +03:00
<source>Transaction Fees</source>
2021-08-18 00:54:34 +03:00
<target>Transaksjonsavgift</target>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">6</context>
2021-07-17 15:37:34 +03:00
</context-group>
2021-12-26 11:15:19 +04:00
<note priority="1" from="description">fees-box.transaction-fees</note>
2021-07-17 15:37:34 +03:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="4fe744df6d36b5e9b0afab728b77fc635b99f040" datatype="html">
<source>Recent Replacements</source>
2024-01-13 16:57:03 +00:00
<target>Nylige erstatninger</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">65</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">dashboard.recent-rbf-replacements</note>
</trans-unit>
<trans-unit id="23c872b0336e20284724607f2887da39bd8142c3" datatype="html">
<source>Previous fee</source>
2024-01-13 16:57:03 +00:00
<target>Tidligere avgift</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">72</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">dashboard.previous-transaction-fee</note>
</trans-unit>
<trans-unit id="df33bef035883b7afeb388977087f99ab5a54409" datatype="html">
<source>New fee</source>
<target>Ny avgift</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">73</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">dashboard.new-transaction-fee</note>
</trans-unit>
<trans-unit id="aa6ce7e6e6fe5cd080713965451f25bca15a2a25" datatype="html">
<source>Recent Transactions</source>
<target>Nylige transaksjoner</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">131</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">dashboard.recent-transactions</note>
</trans-unit>
<trans-unit id="2d70cb7985eaebe99c35bcdfa7dc49b2662c345b" datatype="html">
<source>Liquid Federation Holdings</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">165</context>
2024-04-03 18:47:16 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">305</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">liquid.federation-holdings</note>
</trans-unit>
<trans-unit id="bbdf5ec7a729b8323727675b26e4dffccaaf60f0" datatype="html">
<source>Federation Timelock-Expired UTXOs</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">174</context>
2024-04-03 18:47:16 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">314</context>
2023-11-26 17:00:34 +09:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">liquid.federation-expired-utxos</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="061051c88f1c686bcf3b40a81c8e824ef2ca7ae0" datatype="html">
<source>L-BTC Supply Against BTC Holdings</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">184</context>
2023-11-26 17:00:34 +09:00
</context-group>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">324</context>
2020-12-08 11:58:43 +07:00
</context-group>
2024-04-03 18:47:16 +09:00
<note priority="1" from="description">dashboard.lbtc-supply-against-btc-holdings</note>
2020-12-08 11:58:43 +07:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="1f9a922cb4010ee20eb9a241a22307b670f7628c" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Minimum fee</source>
<target>Minimumsavgift</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">275</context>
2020-12-08 11:58:43 +07:00
</context-group>
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>
2021-04-26 04:05:55 +04:00
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="4c3955cfe5955657297481efaf3ada8c55c75b2c" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Purging</source>
<target>Fjerner</target>
2020-12-08 11:58:43 +07:00
<context-group purpose="location">
2021-04-26 04:05:55 +04:00
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">276</context>
2020-12-08 11:58:43 +07:00
</context-group>
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>
2020-12-08 11:58:43 +07:00
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="af1176facd00a0580509fb2900ab0cf7f9b39ae7" datatype="html">
<source>Indexing in progress</source>
<target>Indeksering pågår</target>
2021-12-03 08:54:13 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.html</context>
2024-04-05 16:46:23 +09:00
<context context-type="linenumber">364</context>
2021-12-03 08:54:13 +09:00
</context-group>
2023-02-27 23:09:11 +04:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
<context context-type="linenumber">102</context>
2023-02-27 23:09:11 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.html</context>
<context context-type="linenumber">52</context>
</context-group>
<note priority="1" from="description">lightning.indexing-in-progress</note>
2023-11-26 17:00:34 +09:00
</trans-unit>
2024-04-05 16:46:23 +09:00
<trans-unit id="4136162380400286378" datatype="html">
<source>Consolidation</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.ts</context>
<context context-type="linenumber">79</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/filters.utils.ts</context>
<context context-type="linenumber">107</context>
</context-group>
</trans-unit>
<trans-unit id="7816493330657272952" datatype="html">
<source>Coinjoin</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.ts</context>
<context context-type="linenumber">80</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/filters.utils.ts</context>
<context context-type="linenumber">106</context>
</context-group>
</trans-unit>
<trans-unit id="146442697456175258" datatype="html">
<source>Data</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/dashboard/dashboard.component.ts</context>
<context context-type="linenumber">81</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/filters.utils.ts</context>
<context context-type="linenumber">121</context>
</context-group>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="999bb1a0150c2815a6b4dd64a1850e763603e525" datatype="html">
<source><x id="START_PARAGRAPH" ctype="x-p" equiv-text="For any such requ"/><x id="START_BOLD_TEXT" ctype="x-b" equiv-text="mempool.space mer"/>mempool.space merely provides data about the Bitcoin network.<x id="CLOSE_BOLD_TEXT" ctype="x-b" equiv-text="</b>"/> It cannot help you with retrieving funds, wallet issues, etc.<x id="CLOSE_PARAGRAPH" ctype="x-p" equiv-text="</p>"/><x id="START_PARAGRAPH" ctype="x-p" equiv-text="For any such requ"/>For any such requests, you need to get in touch with the entity that helped make the transaction (wallet software, exchange company, etc).<x id="CLOSE_PARAGRAPH" ctype="x-p" equiv-text="</p>"/></source>
2024-01-13 16:57:03 +00:00
<target><x id="START_PARAGRAPH" ctype="x-p" equiv-text="For any such requ"/><x id="START_BOLD_TEXT" ctype="x-b" equiv-text="mempool.space mer"/>mempool.space gir bare data om Bitcoin-nettverket.<x id="CLOSE_BOLD_TEXT" ctype="x-b" equiv-text="</b>"/> Det kan ikke hjelpe deg med å hente midler, lommebokproblemer osv.<x id="CLOSE_PARAGRAPH" ctype="x-p" equiv-text="</p>"/><x id="START_PARAGRAPH" ctype="x-p" equiv-text="For any such requ"/>For slike forespørsler må du ta kontakt med enheten som bidro til transaksjonen (lommebokprogramvare, børsselskap osv.).<x id="CLOSE_PARAGRAPH" ctype="x-p" equiv-text="</p>"/></target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">15,16</context>
2023-03-14 14:54:49 +09:00
</context-group>
2023-02-27 23:09:11 +04:00
<note priority="1" from="description">faq.big-disclaimer</note>
</trans-unit>
2022-07-07 16:40:18 +02:00
<trans-unit id="cd2330c7e9c74256f6a91e83bccf10e2905f8556" datatype="html">
<source>REST API service</source>
2022-07-07 18:30:31 +00:00
<target>REST API-tjeneste</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">50</context>
2020-12-05 00:11:40 +09:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">api-docs.title</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="b151944861534c4a9e9623537dba0a95f60e4455" datatype="html">
<source>Endpoint</source>
<target>Endepunkt</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">60</context>
2020-12-05 00:11:40 +09:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">115</context>
2022-05-19 20:12:21 +04:00
</context-group>
<note priority="1" from="description">Api docs endpoint</note>
2020-12-05 00:11:40 +09:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="eec715de352a6b114713b30b640d319fa78207a0" datatype="html">
<source>Description</source>
<target>Beskrivelse</target>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">79</context>
2021-07-17 15:37:34 +03:00
</context-group>
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">119</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group.component.html</context>
<context context-type="linenumber">17</context>
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="a706b1ded7506620b153dbcdea8108e6691bbbd9" datatype="html">
<source>Default push: <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/><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="</code>"/> to express what you want pushed. Available: <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/>blocks<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/>, <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/>mempool-blocks<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/>, <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/>live-2h-chart<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/>, and <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/>stats<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/>.<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="<code>"/><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="</code>"/> 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="<code>"/>address-transactions<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/> for new mempool transactions, and <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/>block-transactions<x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/> for new block confirmed transactions.</source>
<target>Standard push: <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/> <x id="INTERPOLATION" equiv-text="'track-ad"/> handling: 'want', data: ['blocks', ...] <x id="INTERPOLATION_1" equiv-text="{{ '}' }}"/> <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/> for å uttrykke hva du vil ha pushet. Tilgjengelig: <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/> blocks <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/> , <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/> mempool-blocks <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/> , <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/> live-2h-chart <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/>, og <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/> stats <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/>. <x id="LINE_BREAK" ctype="lb" equiv-text="Push transa"/> <x id="LINE_BREAK" ctype="lb" equiv-text="Push transa"/> Push-transaksjoner relatert til adresse: <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/><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="</code>"/> for å motta alle nye transaksjoner som inneholder den adressen som inngang eller utgang. Returnerer en tabell av transaksjoner. <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/>adress-transactions <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/> for nye mempool-transaksjoner, og <x id="START_TAG_CODE" ctype="x-code" equiv-text="<code>"/>block-transactions <x id="CLOSE_TAG_CODE" ctype="x-code" equiv-text="</code>"/> for nye blokkbekreftede transaksjoner.</target>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/api-docs/api-docs.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">120</context>
2021-07-17 15:37:34 +03:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">api-docs.websocket.websocket</note>
</trans-unit>
<trans-unit id="0a668c1c2a17e557a18fc06619998e002f50df1e" datatype="html">
<source>Code Example</source>
<target>Kodeeksempel</target>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">6</context>
2021-07-17 15:37:34 +03:00
</context-group>
2022-05-19 20:12:21 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">13</context>
2022-05-19 20:12:21 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">29</context>
2022-05-19 20:12:21 +04:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">36</context>
2022-10-17 16:21:29 +04:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">API Docs code example</note>
2021-07-17 15:37:34 +03:00
</trans-unit>
2022-05-19 20:12:21 +04:00
<trans-unit id="d6b673097fb7e79231afc43857e376f69ab9f3e3" datatype="html">
<source>Install Package</source>
<target>Installer pakke</target>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">23</context>
2021-07-17 15:37:34 +03:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">API Docs install lib</note>
</trans-unit>
<trans-unit id="4edb71f23e3ff228dbabd05e8ffc364fae8ae467" datatype="html">
<source>Response</source>
<target>Respons</target>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
2022-05-19 20:12:21 +04:00
<context context-type="sourcefile">src/app/docs/code-template/code-template.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">43</context>
2021-07-17 15:37:34 +03:00
</context-group>
2022-05-19 20:12:21 +04:00
<note priority="1" from="description">API Docs API response</note>
2021-07-17 15:37:34 +03:00
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.title.docs.faq" datatype="html">
2022-06-05 22:39:36 +04:00
<source>FAQ</source>
2024-01-13 16:57:03 +00:00
<target>FAQ</target>
2022-06-05 22:39:36 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">46</context>
2022-06-05 22:39:36 +04:00
</context-group>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.docs.faq" datatype="html">
<source>Get answers to common questions like: What is a mempool? Why isn't my transaction confirming? How can I run my own instance of The Mempool Open Source Project? And more.</source>
2024-01-13 16:57:03 +00:00
<target>Få svar på vanlige spørsmål som: Hva er en mempool? Hvorfor bekreftes ikke transaksjonen min? Hvordan kan jeg kjøre min egen instans av Mempool Open Source Project? Og mer.</target>
2022-06-05 22:39:36 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">47</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
<trans-unit id="meta.title.docs.rest" datatype="html">
<source>REST API</source>
2024-01-13 16:57:03 +00:00
<target>REST API</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">51</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
<trans-unit id="meta.description.docs.rest-liquid" datatype="html">
<source>Documentation for the liquid.network REST API service: get info on addresses, transactions, assets, blocks, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Dokumentasjon for liquid.network REST API-tjenesten: få informasjon om adresser, transaksjoner, eiendeler, blokker og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
<context context-type="linenumber">53</context>
</context-group>
</trans-unit>
<trans-unit id="meta.description.docs.rest-bitcoin" datatype="html">
<source>Documentation for the mempool.space REST API service: get info on addresses, transactions, blocks, fees, mining, the Lightning network, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Dokumentasjon for mempool.space REST API-tjenesten: få informasjon om adresser, transaksjoner, blokker, avgifter, utvinning, Lightning-nettverket og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
<context context-type="linenumber">55</context>
</context-group>
</trans-unit>
<trans-unit id="meta.title.docs.websocket" datatype="html">
<source>WebSocket API</source>
2024-01-13 16:57:03 +00:00
<target>WebSocket API</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
<context context-type="linenumber">59</context>
</context-group>
</trans-unit>
<trans-unit id="meta.description.docs.websocket-liquid" datatype="html">
<source>Documentation for the liquid.network WebSocket API service: get real-time info on blocks, mempools, transactions, addresses, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Dokumentasjon for liquid.network WebSocket API-tjenesten: få sanntidsinformasjon om blokker, mempooler, transaksjoner, adresser og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
<context context-type="linenumber">61</context>
</context-group>
</trans-unit>
<trans-unit id="meta.description.docs.websocket-bitcoin" datatype="html">
<source>Documentation for the mempool.space WebSocket API service: get real-time info on blocks, mempools, transactions, addresses, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Dokumentasjon for mempool.space WebSocket API-tjenesten: få sanntidsinformasjon om blokker, mempooler, transaksjoner, adresser og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
<context context-type="linenumber">63</context>
2022-06-05 22:39:36 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
</trans-unit>
<trans-unit id="meta.title.docs.electrum" datatype="html">
<source>Electrum RPC</source>
2024-01-13 16:57:03 +00:00
<target>Electrum RPC</target>
2022-06-05 22:39:36 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">67</context>
2023-01-26 15:54:07 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
</trans-unit>
<trans-unit id="meta.description.docs.electrumrpc" datatype="html">
<source>Documentation for our Electrum RPC interface: get instant, convenient, and reliable access to an Esplora instance.</source>
2024-01-13 16:57:03 +00:00
<target>Dokumentasjon for vårt Electrum RPC-grensesnitt: få umiddelbar, praktisk og pålitelig tilgang til en Esplora-instans.</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/docs/docs/docs.component.ts</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">68</context>
2022-06-05 22:39:36 +04:00
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="4ca458fe3274d1c79640b052d57cf3b900b650b6" datatype="html">
<source>Base fee</source>
2023-02-27 23:09:11 +04:00
<target>Grunnavgift</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">29</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">41</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.base-fee</note>
</trans-unit>
<trans-unit id="6acd06bd5a3af583cd46c6d9f7954d7a2b44095e" datatype="html">
<source>mSats</source>
2023-02-27 23:09:11 +04:00
<target>mSats</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">35</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">47</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">93</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">226</context>
2023-01-26 15:54:07 +04:00
</context-group>
2022-10-17 16:21:29 +04:00
<note priority="1" from="description">shared.m-sats</note>
</trans-unit>
<trans-unit id="fb2137ba0df55f21a9d6b6ad08d56d74ad852e0e" datatype="html">
<source>This channel supports zero base fee routing</source>
2023-02-27 23:09:11 +04:00
<target>Denne kanalen støtter null grunnavgiftsruting</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">44</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.zero-base-fee-tooltip</note>
</trans-unit>
<trans-unit id="3ec76ccfe1fdcbfd7ea152392f6472d93d4e8cab" datatype="html">
<source>Zero base fee</source>
2023-02-27 23:09:11 +04:00
<target>Null grunnavgift</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">45</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.zero-base-fee</note>
</trans-unit>
<trans-unit id="b5e42e06ea8a4012a38eef209104bbd9dd1a0fc0" datatype="html">
<source>This channel does not support zero base fee routing</source>
2023-02-27 23:09:11 +04:00
<target>Denne kanalen støtter ikke null grunnavgift ruting</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">50</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.non-zero-base-fee-tooltip</note>
</trans-unit>
<trans-unit id="09a1bc9c4198e87e9e974a51e86b181429b480d3" datatype="html">
<source>Non-zero base fee</source>
2023-02-27 23:09:11 +04:00
<target>Ikke-null grunnavgift</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">51</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.non-zero-base-fee</note>
</trans-unit>
<trans-unit id="055060668d0b9902c37abfb6168a08a36eba4496" datatype="html">
<source>Min HTLC</source>
2023-02-27 23:09:11 +04:00
<target>Min. HTLC</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">57</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.min-htlc</note>
</trans-unit>
<trans-unit id="c3d94c1a5aef6211f4a902027bd08540d7222b0d" datatype="html">
<source>Max HTLC</source>
2023-02-27 23:09:11 +04:00
<target>Maks HTLC</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">63</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.max-htlc</note>
</trans-unit>
<trans-unit id="9fe79011b50c2ca1f9b7db7066046631bfc6b3cb" datatype="html">
<source>Timelock delta</source>
2023-02-27 23:09:11 +04:00
<target>Timelock delta</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">69</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.timelock-delta</note>
</trans-unit>
<trans-unit id="205c1b86ac1cc419c4d0cca51fdde418c4ffdc20" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> channels</source>
2023-03-22 13:35:16 +09:00
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> kanaler</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-box/channel-box.component.html</context>
2023-01-26 15:54:07 +04:00
<context context-type="linenumber">79</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">123</context>
2022-10-17 16:21:29 +04:00
</context-group>
2024-04-03 18:47:16 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-channels-map/nodes-channels-map.component.ts</context>
<context context-type="linenumber">313</context>
</context-group>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-map/nodes-map.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">213</context>
2023-03-14 14:54:49 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<note priority="1" from="description">lightning.x-channels</note>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="4e64e04c01e8f5fc09c41cb8942dcc3af0398b28" datatype="html">
<source>Starting balance</source>
2023-02-27 23:09:11 +04:00
<target>Startbalanse</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-close-box/channel-close-box.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">3</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">Channel starting balance</note>
<note priority="1" from="meaning">lightning.starting-balance</note>
</trans-unit>
<trans-unit id="5c4bfd47a4f4d7cb99912f028494fe2530d36d57" datatype="html">
<source>Closing balance</source>
2023-02-27 23:09:11 +04:00
<target>Sluttbalanse</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-close-box/channel-close-box.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">26</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">Channel closing balance</note>
<note priority="1" from="meaning">lightning.closing-balance</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="3bbd25c289760a3ba57e30df5ad5fe8977ab25a5" datatype="html">
<source>lightning channel</source>
2023-02-27 23:09:11 +04:00
<target>Lightning-kanal</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">3</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.channel</note>
</trans-unit>
<trans-unit id="43c4133c7a0263d2e33dd4c2e74d40784b2e4b1c" datatype="html">
<source>Inactive</source>
2023-02-27 23:09:11 +04:00
<target>Inaktiv</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">10</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">13</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">68</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">status.inactive</note>
</trans-unit>
<trans-unit id="b36e1450940b7f6028d8587568c7d669b53f7a06" datatype="html">
<source>Active</source>
2023-02-27 23:09:11 +04:00
<target>Aktiv</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">11</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">14</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">69</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">status.active</note>
</trans-unit>
<trans-unit id="4804b8e78964cee9e5c85f31fd982639b97780b2" datatype="html">
<source>Closed</source>
2023-02-27 23:09:11 +04:00
<target>Avsluttet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">12</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">15</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">8</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">71</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/justice-list/justice-list.component.html</context>
<context context-type="linenumber">11</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">status.closed</note>
</trans-unit>
<trans-unit id="1b051734b0ee9021991c91b3ed4e81c244322462" datatype="html">
<source>Created</source>
2023-02-27 23:09:11 +04:00
<target>Opprettet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">23</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">36</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.created</note>
</trans-unit>
<trans-unit id="ce9dfdc6dccb28dc75a78c704e09dc18fb02dcfa" datatype="html">
<source>Capacity</source>
2023-02-27 23:09:11 +04:00
<target>Kapasitet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">27</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">55</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">43</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/justice-list/justice-list.component.html</context>
<context context-type="linenumber">12</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics-chart/node-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">159</context>
2023-03-14 14:54:49 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics-chart/node-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">229</context>
2023-03-14 14:54:49 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics/node-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">4</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics/node-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">46</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-list/nodes-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">6</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">31</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">63</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">57</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">60</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-03-08 16:26:56 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-channels/top-nodes-per-channels.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">13</context>
2023-03-08 16:26:56 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">213</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">293</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.capacity</note>
</trans-unit>
<trans-unit id="8fd0077b032e360ece45c4fd655f85b2400dcb83" datatype="html">
<source>ppm</source>
2023-02-27 23:09:11 +04:00
<target>ppm</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">34</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">36</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">32</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">78</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.ppm</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.lightning.channel" datatype="html">
<source>Overview for Lightning channel <x id="PH" equiv-text="params.get('short_id')"/>. See channel capacity, the Lightning nodes involved, related on-chain transactions, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Oversikt for Lightning-kanalen <x id="PH" equiv-text="params.get('short_id')"/>. Se kanalkapasitet, Lightning-nodene som er involvert, relaterte transaksjoner i kjeden og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel-preview.component.ts</context>
<context context-type="linenumber">37</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.ts</context>
<context context-type="linenumber">38</context>
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="13142ad9637003749d667393aaae7a286d1eba5b" datatype="html">
<source>Lightning channel</source>
2023-02-27 23:09:11 +04:00
<target>Lightningkanal</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">4</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">116</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.channel</note>
</trans-unit>
<trans-unit id="8dad9f60ff582b632a864f22c7466327793c3f09" datatype="html">
<source>Last update</source>
2023-02-27 23:09:11 +04:00
<target>Siste oppdatering</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">40</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">80</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">62</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">59</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/oldest-nodes/oldest-nodes.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">14</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-capacity/top-nodes-per-capacity.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">16</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-channels/top-nodes-per-channels.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">16</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.last-update</note>
</trans-unit>
<trans-unit id="0c134c6787c6b763446c096ea5233ace6fd9116d" datatype="html">
<source>Closing date</source>
2023-02-27 23:09:11 +04:00
<target>Sluttdato</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">44</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">42</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.closing_date</note>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="1f0b0f2c90de4f3f0eb2c138eed38f4e9ac7a13e" datatype="html">
<source>Closed by</source>
2023-02-27 23:09:11 +04:00
<target>Avsluttet av</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">59</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">lightning.closed_by</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="cdd2ea2e12437df848ec474ac15af48859bd09a0" datatype="html">
<source>Opening transaction</source>
2023-02-27 23:09:11 +04:00
<target>Åpningstransaksjon</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">91</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/justice-list/justice-list.component.html</context>
<context context-type="linenumber">62</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.opening-transaction</note>
</trans-unit>
<trans-unit id="50411064ac48e15659d1985b414ae91af0c8cd36" datatype="html">
<source>Closing transaction</source>
2023-03-08 16:26:56 +09:00
<target>Avsluttningstransaksjon</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">100</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/justice-list/justice-list.component.html</context>
<context context-type="linenumber">69</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.closing-transaction</note>
</trans-unit>
<trans-unit id="6008566722612122663" datatype="html">
<source>Channel: <x id="PH" equiv-text="value.short_id"/></source>
2023-02-27 23:09:11 +04:00
<target>Kanal: <x id="PH" equiv-text="value.short_id"/></target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/channel.component.ts</context>
<context context-type="linenumber">37</context>
</context-group>
</trans-unit>
2023-02-27 23:09:11 +04:00
<trans-unit id="2408280550320842855" datatype="html">
<source>Mutually closed</source>
<target>Gjensidig avsluttet</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/closing-type/closing-type.component.ts</context>
<context context-type="linenumber">20</context>
</context-group>
</trans-unit>
<trans-unit id="4610828009441770083" datatype="html">
<source>Force closed</source>
<target>Tvungen avsluttning</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/closing-type/closing-type.component.ts</context>
<context context-type="linenumber">24</context>
</context-group>
</trans-unit>
<trans-unit id="96508700250272816" datatype="html">
<source>Force closed with penalty</source>
<target>Tvunget avsluttning med straff</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channel/closing-type/closing-type.component.ts</context>
<context context-type="linenumber">28</context>
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="c9039b1b13b3ef165b66b3c5d79f810ab1ebb050" datatype="html">
<source>Open</source>
2023-02-27 23:09:11 +04:00
<target>Åpen</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">5</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">open</note>
</trans-unit>
<trans-unit id="a43e63c25599408ef14b33c80dd523021b21f846" datatype="html">
<source>No channels to display</source>
2023-02-27 23:09:11 +04:00
<target>Ingen kanaler å vise</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">29</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.empty-channels-list</note>
</trans-unit>
<trans-unit id="fbaaeb297e70b9a800acf841b9d26c19d60651ef" datatype="html">
<source>Alias</source>
2023-02-27 23:09:11 +04:00
<target>Alias</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">38</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">72</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-list/nodes-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">5</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">60</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">57</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/oldest-nodes/oldest-nodes.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">10</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-capacity/top-nodes-per-capacity.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">11</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-channels/top-nodes-per-channels.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">11</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.alias</note>
</trans-unit>
<trans-unit id="0cd107458dce99721e72971d426a5a3106074331" datatype="html">
<source>Channel ID</source>
2023-02-27 23:09:11 +04:00
<target>Kanal-ID</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-list/channels-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">44</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/lightning/justice-list/justice-list.component.html</context>
<context context-type="linenumber">15</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<note priority="1" from="description">channels.id</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2023-02-27 23:09:11 +04:00
<trans-unit id="cfcc7201138b0ef9901e9604c35f550e91629295" datatype="html">
<source>avg</source>
<target>gj.sn</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">3</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">statistics.average-small</note>
</trans-unit>
<trans-unit id="ba9117dcc11814c44437cf9d7561874ba8b98a2a" datatype="html">
<source>med</source>
<target>median</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">6</context>
2023-02-27 23:09:11 +04:00
</context-group>
<note priority="1" from="description">statistics.median-small</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="ab456546aa39de3328fcfdf077f410b5ff1aa773" datatype="html">
<source>Avg Capacity</source>
2023-02-27 23:09:11 +04:00
<target>Gj.sn. kapasitet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">13</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">107</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.average-capacity</note>
</trans-unit>
<trans-unit id="f68705670e611f13da1a43e90f9c97d8761dd9ef" datatype="html">
<source>Avg Fee Rate</source>
2023-02-27 23:09:11 +04:00
<target>Gj.sn. avgiftssats</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">26</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">114</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.average-feerate</note>
</trans-unit>
<trans-unit id="db1f0c0605ab0c4a904523635982253ff72eed40" datatype="html">
<source>The average fee rate charged by routing nodes, ignoring fee rates > 0.5% or 5000ppm</source>
2023-02-27 23:09:11 +04:00
<target>Gjennomsnittlig avgiftssats som belastes av rutingsnoder, ignorerer avgiftssatser > 0,5 % eller 5000 ppm</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">28</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.average-feerate-desc</note>
</trans-unit>
<trans-unit id="140fb39368f210ec945417f3eb23bf9564396e5c" datatype="html">
<source>Avg Base Fee</source>
2023-03-08 16:26:56 +09:00
<target>Gj.sn. basisavgift</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">41</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">121</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.average-basefee</note>
</trans-unit>
<trans-unit id="0a46218f4a7b17b6445460898d75ab78e7e7979b" datatype="html">
<source>The average base fee charged by routing nodes, ignoring base fees > 5000ppm</source>
2023-02-27 23:09:11 +04:00
<target>Den gjennomsnittlige basisavgiften som belastes av rutingsnoder, ignorerer basisavgifter > 5000 ppm</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">43</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.average-basefee-desc</note>
</trans-unit>
<trans-unit id="2e72b276a3c5cc2ec27b4c8189639ba2fe62b6cb" datatype="html">
<source>Med Capacity</source>
2023-02-27 23:09:11 +04:00
<target>Median kapasitet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">59</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.median-capacity</note>
</trans-unit>
<trans-unit id="2c1c39e28735f607d62dbf3272eb792451c265a5" datatype="html">
<source>Med Fee Rate</source>
2023-02-27 23:09:11 +04:00
<target>Median avgiftssats</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">72</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.average-feerate</note>
</trans-unit>
<trans-unit id="cb4dae32e1b4d6a2ba6287d9f7bd859ca7259468" datatype="html">
<source>The median fee rate charged by routing nodes, ignoring fee rates > 0.5% or 5000ppm</source>
2023-02-27 23:09:11 +04:00
<target>Medianavgiftssatsen som belastes av rutingsnoder, ignorerer avgiftssatser > 0,5 % eller 5000 ppm</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">74</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.median-feerate-desc</note>
</trans-unit>
<trans-unit id="a541dbcef4908bf2e767e77d7a09cc62450e8e56" datatype="html">
<source>Med Base Fee</source>
2023-02-27 23:09:11 +04:00
<target>Median basisavgift</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">87</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.median-basefee</note>
</trans-unit>
<trans-unit id="b8539025268617abfcab1c3f2a2c60cd8d7485fb" datatype="html">
<source>The median base fee charged by routing nodes, ignoring base fees > 5000ppm</source>
2023-02-27 23:09:11 +04:00
<target>Median grunnavgift belastet av rutingnoder, ignorerer basisavgifter > 5000 ppm</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/channels-statistics/channels-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">89</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">ln.median-basefee-desc</note>
</trans-unit>
<trans-unit id="de1c07e9943fc284461bb8fb4860faecf52a1568" datatype="html">
<source>Lightning node group</source>
2023-02-27 23:09:11 +04:00
<target>Ligthningnode-gruppe</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">3</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">2</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.node-group</note>
</trans-unit>
<trans-unit id="6e2329529b1953198c7dfa0edb260554310bc636" datatype="html">
<source>Nodes</source>
2023-02-27 23:09:11 +04:00
<target>Noder</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">25</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">23</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/justice-list/justice-list.component.html</context>
<context context-type="linenumber">14</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics/node-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">16</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics/node-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">53</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">30</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">13</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">56</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">22</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.node-count</note>
</trans-unit>
<trans-unit id="14a12efce56ffe89f839e50320bcf47e4e9ca4e4" datatype="html">
<source>Liquidity</source>
2023-02-27 23:09:11 +04:00
<target>Likviditet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">29</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">27</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">17</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">26</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">18</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/oldest-nodes/oldest-nodes.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">12</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-capacity/top-nodes-per-capacity.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">12</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.liquidity</note>
</trans-unit>
<trans-unit id="807cf11e6ac1cde912496f764c176bdfdd6b7e19" datatype="html">
<source>Channels</source>
2023-02-27 23:09:11 +04:00
<target>Kanaler</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">40</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">40</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics-chart/node-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">151</context>
2023-03-14 14:54:49 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics-chart/node-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">206</context>
2023-03-14 14:54:49 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics/node-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">28</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics/node-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">60</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-list/nodes-list.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">7</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">30</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">64</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">35</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">31</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">61</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/oldest-nodes/oldest-nodes.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">13</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-capacity/top-nodes-per-capacity.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">14</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-channels/top-nodes-per-channels.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">12</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">205</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">270</context>
2023-03-14 14:54:49 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<note priority="1" from="description">lightning.channels</note>
</trans-unit>
<trans-unit id="e4706894b195010f6814e54bf6570c729d69aaca" datatype="html">
<source>Average size</source>
2023-02-27 23:09:11 +04:00
<target>Gjennomsnittsstørrelse</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">44</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">32</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.active-channels-avg</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="ec42ed2d917189340598d7993c29b30c7fd32af4" datatype="html">
<source>Connect</source>
2024-01-13 16:57:03 +00:00
<target>Koble til</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group.component.html</context>
<context context-type="linenumber">73</context>
</context-group>
<note priority="1" from="description">Connect</note>
<note priority="1" from="meaning">lightning.connect-to-node</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="ed31c09fd77c36238c13d83635f3fe5294c733d2" datatype="html">
<source>Location</source>
2023-03-08 16:26:56 +09:00
<target>Plassering</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/group/group.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">74</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">38</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">50</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">51</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">65</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">62</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/oldest-nodes/oldest-nodes.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">15</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-capacity/top-nodes-per-capacity.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">17</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-channels/top-nodes-per-channels.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">17</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.location</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="34e302a08660d9860dda71e3f350351d34bda498" datatype="html">
<source>Penalties</source>
2024-01-13 16:57:03 +00:00
<target>Straffer</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/justice-list/justice-list.component.html</context>
<context context-type="linenumber">4</context>
</context-group>
<note priority="1" from="description">lightning.liquidity-ranking</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="29c05e9a540827cdfa8e3b2e5e2f27aeb478916c" datatype="html">
<source>Network Statistics</source>
2023-02-27 23:09:11 +04:00
<target>Nettverksstatistikk</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/lightning-dashboard/lightning-dashboard.component.html</context>
<context context-type="linenumber">10</context>
</context-group>
<note priority="1" from="description">lightning.network-statistics-title</note>
</trans-unit>
<trans-unit id="066e05b9a5db60850d907783fde6913e2e47cd5b" datatype="html">
<source>Channels Statistics</source>
2023-02-27 23:09:11 +04:00
<target>Kanalstatistikk</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/lightning-dashboard/lightning-dashboard.component.html</context>
<context context-type="linenumber">24</context>
</context-group>
<note priority="1" from="description">lightning.channel-statistics-title</note>
</trans-unit>
<trans-unit id="0f33aeb084ac4d83cb0fe6f72648a8585b1b5e88" datatype="html">
<source>Lightning Network History</source>
2023-02-27 23:09:11 +04:00
<target>Lightning-nettverk historie</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/lightning-dashboard/lightning-dashboard.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">52</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.network-history</note>
</trans-unit>
<trans-unit id="2d9883d230a47fbbb2ec969e32a186597ea27405" datatype="html">
<source>Liquidity Ranking</source>
2023-02-27 23:09:11 +04:00
<target>Likviditetsrangering</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/lightning-dashboard/lightning-dashboard.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">66</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-03-08 16:26:56 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-capacity/top-nodes-per-capacity.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">4</context>
2023-03-08 16:26:56 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-capacity/top-nodes-per-capacity.component.ts</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">34</context>
2023-03-08 16:26:56 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-rankings-dashboard/nodes-rankings-dashboard.component.html</context>
<context context-type="linenumber">8</context>
</context-group>
<note priority="1" from="description">lightning.liquidity-ranking</note>
</trans-unit>
<trans-unit id="c50bf442cf99f6fc5f8b687c460f33234b879869" datatype="html">
<source>Connectivity Ranking</source>
2023-02-27 23:09:11 +04:00
<target>Tilkoblingsrangering</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/lightning-dashboard/lightning-dashboard.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">80</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-channels/top-nodes-per-channels.component.html</context>
<context context-type="linenumber">4</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-channels/top-nodes-per-channels.component.ts</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">38</context>
2023-11-26 17:00:34 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-rankings-dashboard/nodes-rankings-dashboard.component.html</context>
<context context-type="linenumber">22</context>
</context-group>
<note priority="1" from="description">lightning.connectivity-ranking</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.lightning.dashboard" datatype="html">
2024-01-13 16:57:03 +00:00
<source>Get stats on the Lightning network (aggregate capacity, connectivity, etc), Lightning nodes (channels, liquidity, etc) and Lightning channels (status, fees, etc).</source>
<target>Få statistikk om Lightning-nettverket (samlet kapasitet, tilkobling osv.), Lightning-noder (kanaler, likviditet osv.) og Lightning-kanaler (status, avgifter osv.).</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/lightning-dashboard/lightning-dashboard.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">34</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="7b8687bbc13bbf62288689606dcab9784a3eb53b" datatype="html">
<source>Fee distribution</source>
2023-02-27 23:09:11 +04:00
<target>Avgiftsfordeling</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-fee-chart/node-fee-chart.component.html</context>
<context context-type="linenumber">2</context>
</context-group>
<note priority="1" from="description">lightning.node-fee-distribution</note>
</trans-unit>
2023-02-27 23:09:11 +04:00
<trans-unit id="7254919336112973896" datatype="html">
<source>Outgoing Fees</source>
<target>Utgående avgifter</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-fee-chart/node-fee-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">179</context>
2023-02-27 23:09:11 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-fee-chart/node-fee-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">217</context>
2023-02-27 23:09:11 +04:00
</context-group>
</trans-unit>
<trans-unit id="484887099976974152" datatype="html">
<source>Incoming Fees</source>
<target>Inngående avgifter</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-fee-chart/node-fee-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">187</context>
2023-02-27 23:09:11 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-fee-chart/node-fee-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">231</context>
2023-02-27 23:09:11 +04:00
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="027f48063a5512e5c26b6ca88f7d7734e2d333a7" datatype="html">
<source>Percentage change past week</source>
2023-02-27 23:09:11 +04:00
<target>Prosentvis endring siste uke</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics/node-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">5</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics/node-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">17</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node-statistics/node-statistics.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">29</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">mining.percentage-change-last-week</note>
</trans-unit>
<trans-unit id="be6ebbb11d55adb8e821d503f8e10ccf43ed8b00" datatype="html">
<source>Lightning node</source>
2023-02-27 23:09:11 +04:00
<target>Lightning-node</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">3</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">4</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">306</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.node</note>
</trans-unit>
<trans-unit id="af15c87bfed273bc095ba572cf27e3aaffc33b22" datatype="html">
<source>Active capacity</source>
2023-02-27 23:09:11 +04:00
<target>Aktiv kapasitet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">20</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">31</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.active-capacity</note>
</trans-unit>
<trans-unit id="52ffa66bd0399a49d5aa8d6f8fa077a6e8db09c0" datatype="html">
<source>Active channels</source>
2023-02-27 23:09:11 +04:00
<target>Aktive kanaler</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">26</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">38</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.active-channels</note>
</trans-unit>
<trans-unit id="a43f25a9ac40e8e2441ff0be7a36b8e5d15534df" datatype="html">
<source>Country</source>
2023-02-27 23:09:11 +04:00
<target>Land</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">44</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">country</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.lightning.node" datatype="html">
<source>Overview for the Lightning network node named <x id="PH" equiv-text="node.alias"/>. See channels, capacity, location, fee stats, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Oversikt for Lightning-nettverksnoden <x id="PH" equiv-text="node.alias"/>. Se kanaler, kapasitet, plassering, gebyrstatistikk og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node-preview.component.ts</context>
<context context-type="linenumber">52</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">64</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="43b48b9c15083a164b401bf3775a4b99f3917699" datatype="html">
<source>Average channel size</source>
2023-03-08 16:26:56 +09:00
<target>Gj.sn. kanalstørrelse</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">44</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.active-channels-avg</note>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="008e9fb48f07f545af73b3f676dc60cc3a829765" datatype="html">
<source>Avg channel distance</source>
2023-03-08 16:26:56 +09:00
<target>Gj.sn. kanalavstand</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">60</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-01-26 15:54:07 +04:00
<note priority="1" from="description">lightning.avg-distance</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
<trans-unit id="8fa4d523f7b91df4390120b85ed0406138273e1a" datatype="html">
<source>Color</source>
2023-02-27 23:09:11 +04:00
<target>Farge</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">86</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.color</note>
</trans-unit>
<trans-unit id="5b9904cb31f6f28314443f6385dc5facab7ea851" datatype="html">
<source>ISP</source>
2023-02-27 23:09:11 +04:00
<target>ISP</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">92</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">54</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">isp</note>
</trans-unit>
<trans-unit id="86d9619247d148019e5599707c39a36e880a2d23" datatype="html">
<source>Exclusively on Tor</source>
2023-02-27 23:09:11 +04:00
<target>Eksklusivt på Tor</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">100</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">tor</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="a737eb6814b234b0fd00e81b645b95a396711f15" datatype="html">
<source>Decoded</source>
2024-01-13 16:57:03 +00:00
<target>Dekodet</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">134</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">Decoded</note>
<note priority="1" from="meaning">lightning.decoded</note>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="e128630e07a4c467f51b246a31c5734d5fb1a2c2" datatype="html">
<source>Liquidity ad</source>
2023-02-27 23:09:11 +04:00
<target>Likviditetsannonse</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">184</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">node.liquidity-ad</note>
</trans-unit>
<trans-unit id="bc84b5a9a70217104a53c7139e30b392be6520b7" datatype="html">
<source>Lease fee rate</source>
2023-02-27 23:09:11 +04:00
<target>Leieavgiftssats</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">190</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">Liquidity ad lease fee rate</note>
<note priority="1" from="meaning">liquidity-ad.lease-fee-rate</note>
</trans-unit>
<trans-unit id="ee807dd54b4a45eeba284744c64774de1ab5e4f1" datatype="html">
<source>Lease base fee</source>
2023-02-27 23:09:11 +04:00
<target>Leiegrunnavgift</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">198</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">liquidity-ad.lease-base-fee</note>
</trans-unit>
<trans-unit id="5e348f3d51c3bb283c16572bee1e293ea991cf49" datatype="html">
<source>Funding weight</source>
2023-02-27 23:09:11 +04:00
<target>Finansieringsvekt</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">204</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">liquidity-ad.funding-weight</note>
</trans-unit>
<trans-unit id="8af4768ed9112268945c697923ce017fbe23e1b7" datatype="html">
<source>Channel fee rate</source>
2023-02-27 23:09:11 +04:00
<target>Kanalavgiftssats</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">214</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">Liquidity ad channel fee rate</note>
<note priority="1" from="meaning">liquidity-ad.channel-fee-rate</note>
</trans-unit>
<trans-unit id="4e6d03f01a59434dee25104fe9478041db186ca8" datatype="html">
<source>Channel base fee</source>
2023-02-27 23:09:11 +04:00
<target>Kanalbaseavgift</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">222</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">liquidity-ad.channel-base-fee</note>
</trans-unit>
<trans-unit id="e8e09fa12864e94f094a2a7c8c97cfdf0cff8aab" datatype="html">
<source>Compact lease</source>
2023-02-27 23:09:11 +04:00
<target>Kompakt leieavtale</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">234</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">liquidity-ad.compact-lease</note>
</trans-unit>
<trans-unit id="aa687f4987e2d4e0010be692d402174962ece70e" datatype="html">
<source>TLV extension records</source>
2023-02-27 23:09:11 +04:00
<target>TLV-utvidelsesposter</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">245</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">node.tlv.records</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="b371db1a7ab2167dc8dd91b48ea929d71bb4ef4c" datatype="html">
<source>Open channels</source>
2023-02-27 23:09:11 +04:00
<target>Åpne kanaler</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">286</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.open-channels</note>
</trans-unit>
<trans-unit id="a2dff531c3d7477178553f579e0ec7c3ac7a6f30" datatype="html">
<source>Closed channels</source>
2023-03-08 16:26:56 +09:00
<target>Avsluttede kanaler</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">290</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.open-channels</note>
</trans-unit>
<trans-unit id="2519445964020754921" datatype="html">
<source>Node: <x id="PH" equiv-text="node.alias"/></source>
2023-02-27 23:09:11 +04:00
<target>Node: <x id="PH" equiv-text="node.alias"/></target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/node/node.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">63</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
<trans-unit id="7cac1c3013423d82d5149a5854d709bd08411430" datatype="html">
<source>(Tor nodes excluded)</source>
2023-02-27 23:09:11 +04:00
<target>(Tor-noder ekskludert)</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-channels-map/nodes-channels-map.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">22</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-map/nodes-map.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">7</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">10</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">37</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.tor-nodes-excluded</note>
</trans-unit>
<trans-unit id="8199511328474154549" datatype="html">
<source>Lightning Nodes Channels World Map</source>
2023-03-08 16:26:56 +09:00
<target>Lightning-kanaler verdenskart</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-channels-map/nodes-channels-map.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">73</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
<trans-unit id="meta.description.lightning.node-map" datatype="html">
<source>See the channels of non-Tor Lightning network nodes visualized on a world map. Hover/tap on points on the map for node names and details.</source>
2024-01-13 16:57:03 +00:00
<target>Se kanalene til ikke-Tor Lightning-nettverksnoder visualisert på et verdenskart. Hold musepekeren/trykk på punkter på kartet for nodenavn og detaljer.</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-channels-map/nodes-channels-map.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">74</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
<trans-unit id="4390631969351833104" datatype="html">
<source>No geolocation data available</source>
2023-02-27 23:09:11 +04:00
<target>Ingen geolokaliseringsdata tilgjengelig</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-channels-map/nodes-channels-map.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">245</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
<trans-unit id="a4d393ee035f4225083c22cc3909b26a05a87528" datatype="html">
<source>Active channels map</source>
2023-02-27 23:09:11 +04:00
<target>Kart over aktive kanaler</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-channels/node-channels.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">3</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.active-channels-map</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.lightning.node-channel-map" datatype="html">
<source>See the locations of non-Tor Lightning network nodes visualized on a world map. Hover/tap on points on the map for node names and details.</source>
2024-01-13 16:57:03 +00:00
<target>Se plasseringen til ikke-Tor Lightning-nettverksnoder visualisert på et verdenskart. Hold musepekeren/trykk på punkter på kartet for nodenavn og detaljer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-map/nodes-map.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">52</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
<trans-unit id="meta.description.lightning.nodes-network" datatype="html">
<source>See the number of Lightning network nodes visualized over time by network: clearnet only (IPv4, IPv6), darknet (Tor, I2p, cjdns), and both.</source>
2024-01-13 16:57:03 +00:00
<target>Se antall Lightning-nettverksnoder visualisert over tid etter nettverk: bare clearnet (IPv4, IPv6), darknet (Tor, I2p, cjdns) og begge deler.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">74</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="6391724349488018234" datatype="html">
<source>Indexing in progress</source>
2023-02-27 23:09:11 +04:00
<target>Indeksering pågår</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">133</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">123</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
2023-03-08 16:26:56 +09:00
<trans-unit id="599038141003770125" datatype="html">
<source>Clearnet and Darknet</source>
<target>Clearnet og Darknet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">176</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">315</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
2023-03-08 16:26:56 +09:00
<trans-unit id="1282458597026430784" datatype="html">
<source>Clearnet Only (IPv4, IPv6)</source>
<target>Bare Clearnet (IPv4, IPv6)</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">197</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">307</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
2023-03-08 16:26:56 +09:00
<trans-unit id="2165336009914523952" datatype="html">
<source>Darknet Only (Tor, I2P, cjdns)</source>
<target>Bare Darknet (Tor, I2P, cjdns)</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">218</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-networks-chart/nodes-networks-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">299</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
<trans-unit id="0bd8b27f60a1f098a53e06328426d818e3508ff9" datatype="html">
<source>Share</source>
2023-03-08 16:26:56 +09:00
<target>Andel</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">29</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">55</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.share</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.lightning.nodes-country-overview" datatype="html">
<source>See a geographical breakdown of the Lightning network: how many Lightning nodes are hosted in countries around the world, aggregate BTC capacity for each country, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Se en geografisk inndeling av Lightning-nettverket: hvor mange Lightning-noder er det i land rundt om i verden, samlet BTC-kapasitet for hvert land, og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.ts</context>
<context context-type="linenumber">47</context>
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="5222540403093176126" datatype="html">
2023-03-14 14:54:49 +09:00
<source><x id="PH" equiv-text="nodeCount"/> nodes</source>
2023-03-22 13:35:16 +09:00
<target><x id="PH" equiv-text="nodeCount"/> noder</target>
2023-03-14 14:54:49 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.ts</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">104</context>
2023-03-14 14:54:49 +09:00
</context-group>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.ts</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">137</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">163</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">196</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
<trans-unit id="7032954508645880700" datatype="html">
<source><x id="PH" equiv-text="this.amountShortenerPipe.transform(country.capacity / 100000000, 2)"/> BTC capacity</source>
2023-03-22 13:35:16 +09:00
<target><x id="PH" equiv-text="this.amountShortenerPipe.transform(country.capacity / 100000000, 2)"/> BTC-kapasitet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country-chart/nodes-per-country-chart.component.ts</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">105</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
<trans-unit id="7ede3edfacd291eb9db08e11845d9efdf197f417" datatype="html">
<source>Lightning nodes in <x id="INTERPOLATION" equiv-text="{{ country?.name }}"/></source>
2023-02-27 23:09:11 +04:00
<target>Lightning-noder i <x id="INTERPOLATION" equiv-text="{{ country?.name }}"/></target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
<context context-type="linenumber">3,4</context>
</context-group>
<note priority="1" from="description">lightning.nodes-in-country</note>
</trans-unit>
<trans-unit id="4498ec29c37744fef46809ebc3db67c5fb789917" datatype="html">
<source>ISP Count</source>
2023-02-27 23:09:11 +04:00
<target>Antall ISPer</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">34</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.isp-count</note>
</trans-unit>
<trans-unit id="90a6a964ba53464578003e3b4b2873ef5d2132a1" datatype="html">
<source>Top ISP</source>
2023-02-27 23:09:11 +04:00
<target>Topp ISP</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">38</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.top-isp</note>
</trans-unit>
<trans-unit id="7246059109648045954" datatype="html">
<source>Lightning nodes in <x id="PH" equiv-text="response.country.en"/></source>
2023-02-27 23:09:11 +04:00
<target>Lightning-noder i <x id="PH" equiv-text="response.country.en"/></target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">43</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.lightning.nodes-country" datatype="html">
<source>Explore all the Lightning nodes hosted in <x id="PH" equiv-text="response.country.en"/> and see an overview of each node's capacity, number of open channels, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Utforsk alle Lightning-nodene som er i <x id="PH" equiv-text="response.country.en"/> og se en oversikt over hver nodes kapasitet, antall åpne kanaler og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-country/nodes-per-country.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">44</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="6b4442323c695a8211357c7e4486dd620c443822" datatype="html">
<source>Clearnet Capacity</source>
2023-03-08 16:26:56 +09:00
<target>Clearnet kapasitet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">6</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">81</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.clearnet-capacity</note>
</trans-unit>
<trans-unit id="ccabb31683868066778a1d664aa53ee9fcf77d6b" datatype="html">
<source>How much liquidity is running on nodes advertising at least one clearnet IP address</source>
2023-02-27 23:09:11 +04:00
<target>Hvor mye likviditet er det på noder som annonserer minst én clearnet IP-adresse</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">8</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.clearnet-capacity-desc</note>
</trans-unit>
<trans-unit id="462d2233ddacc9869eb28e09b3b12f1d85556937" datatype="html">
<source>Unknown Capacity</source>
2023-02-27 23:09:11 +04:00
<target>Ukjent kapasitet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">13</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">87</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.unknown-capacity</note>
</trans-unit>
<trans-unit id="26fb07e8754b87bba4bf12c5137ffa77dac389a8" datatype="html">
<source>How much liquidity is running on nodes which ISP was not identifiable</source>
2023-02-27 23:09:11 +04:00
<target>Hvor mye likviditet er det på på noder der ISP ikke var identifiserbar</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">15</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.unknown-capacity-desc</note>
</trans-unit>
<trans-unit id="df3728b721159d25e68f5daf44aaab7fa25f1415" datatype="html">
<source>Tor Capacity</source>
2023-02-27 23:09:11 +04:00
<target>Tor kapasitet</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">20</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">93</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.tor-capacity</note>
</trans-unit>
<trans-unit id="23549ef4e1f846f06abcf07ceecb115945a0cf61" datatype="html">
<source>How much liquidity is running on nodes advertising only Tor addresses</source>
2023-02-27 23:09:11 +04:00
<target>Hvor mye likviditet er det på noder som kun annonserer Tor-adresser</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">22</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.tor-capacity-desc</note>
</trans-unit>
<trans-unit id="e008f2a76179fdcd7110b41ca624131f91075949" datatype="html">
<source>Top 100 ISPs hosting LN nodes</source>
2023-02-27 23:09:11 +04:00
<target>Topp 100 ISPer som er vert for LN-noder</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">31</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.top-100-isp-ln</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="meta.description.lightning.nodes-per-isp" datatype="html">
<source>Browse the top 100 ISPs hosting Lightning nodes along with stats like total number of nodes per ISP, aggregate BTC capacity per ISP, and more</source>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
2024-04-03 18:47:16 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.ts</context>
<context context-type="linenumber">54</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="3627306100664959238" datatype="html">
<source><x id="PH" equiv-text="this.amountShortenerPipe.transform(isp[2] / 100000000, 2)"/> BTC</source>
2023-03-22 13:35:16 +09:00
<target><x id="PH" equiv-text="this.amountShortenerPipe.transform(isp[2] / 100000000, 2)"/> BTC</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">164</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp-chart/nodes-per-isp-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">197</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
<trans-unit id="c18497e4f0db0d0ad0c71ba294295f42b3d312c9" datatype="html">
<source>Lightning ISP</source>
2023-02-27 23:09:11 +04:00
<target>Lightning ISP</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">3</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.node-isp</note>
</trans-unit>
<trans-unit id="41074627e075a9b1bd8197c474ea68a2b8276e54" datatype="html">
<source>Top country</source>
2023-02-27 23:09:11 +04:00
<target>Topp land</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">39</context>
2022-10-17 16:21:29 +04:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">35</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.top-country</note>
</trans-unit>
<trans-unit id="5fad6872a652d922ad8822f4016e104b9a8cc113" datatype="html">
<source>Top node</source>
2023-02-27 23:09:11 +04:00
<target>Topp node</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp-preview.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">45</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.top-node</note>
</trans-unit>
<trans-unit id="5735693498020397727" datatype="html">
<source>Lightning nodes on ISP: <x id="PH" equiv-text="response.isp"/> [AS<x id="PH_1" equiv-text="this.route.snapshot.params.isp"/>]</source>
2023-03-22 13:35:16 +09:00
<target>Lightning-noder på ISP: <x id="PH" equiv-text="response.isp"/> [AS <x id="PH_1" equiv-text="this.route.snapshot.params.isp"/>]</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp-preview.component.ts</context>
<context context-type="linenumber">44</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">46</context>
2022-10-17 16:21:29 +04:00
</context-group>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.lightning.nodes-isp" datatype="html">
<source>Browse all Bitcoin Lightning nodes using the <x id="PH" equiv-text="response.isp"/> [AS<x id="PH_1" equiv-text="this.route.snapshot.params.isp"/>] ISP and see aggregate stats like total number of nodes, total capacity, and more for the ISP.</source>
2024-01-13 16:57:03 +00:00
<target>Bla gjennom alle Bitcoin Lightning-noder ved å bruke <x id="PH" equiv-text="response.isp"/> [AS<x id="PH_1" equiv-text="this.route.snapshot.params.isp"/>] ISP og se samlet statistikk som totalt antall noder, total kapasitet, og mer for Internett-leverandøren.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp-preview.component.ts</context>
<context context-type="linenumber">45</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">47</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="d82f436f033a7d81680b8430275f94dda530151c" datatype="html">
<source>Lightning nodes on ISP: <x id="INTERPOLATION" equiv-text="{{ isp?.name }}"/></source>
2023-02-27 23:09:11 +04:00
<target>Lightning-noder på ISP: <x id="INTERPOLATION" equiv-text="{{ isp?.name }}"/></target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
<context context-type="linenumber">2,4</context>
</context-group>
<note priority="1" from="description">lightning.nodes-for-isp</note>
</trans-unit>
<trans-unit id="ca0b795795658155d44ddca02e95f1feeeb4a88f" datatype="html">
<source>ASN</source>
2023-02-27 23:09:11 +04:00
<target>ASN</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">10</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.asn</note>
</trans-unit>
2023-01-26 15:54:07 +04:00
<trans-unit id="e422817608e8d55e08b45a1da2e118eb42815af4" datatype="html">
<source>Active nodes</source>
2023-02-27 23:09:11 +04:00
<target>Aktive noder</target>
2023-01-26 15:54:07 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-per-isp/nodes-per-isp.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">14</context>
2023-01-26 15:54:07 +04:00
</context-group>
<note priority="1" from="description">lightning.active-node-count</note>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="5b727d251b06e9959cf24a90250a480d425339de" datatype="html">
<source>Top 100 oldest lightning nodes</source>
2023-02-27 23:09:11 +04:00
<target>Topp 100 eldste lightning-noder</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/oldest-nodes/oldest-nodes.component.html</context>
2023-11-26 17:00:34 +09:00
<context context-type="linenumber">3</context>
2022-10-17 16:21:29 +04:00
</context-group>
<note priority="1" from="description">lightning.top-100-oldest-nodes</note>
</trans-unit>
<trans-unit id="4157312397261844620" datatype="html">
<source>Oldest lightning nodes</source>
2023-02-27 23:09:11 +04:00
<target>Eldste ligthning-noder</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/oldest-nodes/oldest-nodes.component.ts</context>
<context context-type="linenumber">27</context>
</context-group>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.lightning.ranking.oldest" datatype="html">
<source>See the oldest nodes on the Lightning network along with their capacity, number of channels, location, etc.</source>
2024-01-13 16:57:03 +00:00
<target>Se de eldste nodene på Lightning-nettverket sammen med deres kapasitet, antall kanaler, plassering osv.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/oldest-nodes/oldest-nodes.component.ts</context>
<context context-type="linenumber">28</context>
</context-group>
</trans-unit>
<trans-unit id="meta.description.lightning.ranking.liquidity" datatype="html">
<source>See Lightning nodes with the most BTC liquidity deployed along with high-level stats like number of open channels, location, node age, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Se Lightning-noder med mest BTC-likviditet utplassert sammen med statistikk som antall åpne kanaler, plassering, nodens alder og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-capacity/top-nodes-per-capacity.component.ts</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">35</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
<trans-unit id="meta.description.lightning.ranking.channels" datatype="html">
<source>See Lightning nodes with the most channels open along with high-level stats like total node capacity, node age, and more.</source>
2024-01-13 16:57:03 +00:00
<target>Se Lightning-noder med flest åpne kanaler sammen med statistikk som total nodekapasitet, nodealder og mer.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-ranking/top-nodes-per-channels/top-nodes-per-channels.component.ts</context>
2024-01-22 21:30:03 +07:00
<context context-type="linenumber">39</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
2022-10-17 16:21:29 +04:00
<trans-unit id="47a30fc5a836252f8fe03e2949756b150684d934" datatype="html">
<source>Oldest nodes</source>
2023-02-27 23:09:11 +04:00
<target>Eldste noder</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-rankings-dashboard/nodes-rankings-dashboard.component.html</context>
<context context-type="linenumber">36</context>
</context-group>
<note priority="1" from="description">lightning.top-channels-age</note>
</trans-unit>
<trans-unit id="4034215342842066505" datatype="html">
<source>Top lightning nodes</source>
2023-02-27 23:09:11 +04:00
<target>Topp lightning-noder</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/nodes-rankings-dashboard/nodes-rankings-dashboard.component.ts</context>
<context context-type="linenumber">22</context>
</context-group>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="meta.description.lightning.rankings-dashboard" datatype="html">
2024-01-13 16:57:03 +00:00
<source>See the top Lightning network nodes ranked by liquidity, connectivity, and age.</source>
<target>Se de beste Lightning-nettverksnodene rangert etter likviditet, tilkobling og alder.</target>
2022-10-17 16:21:29 +04:00
<context-group purpose="location">
2023-11-26 17:00:34 +09:00
<context context-type="sourcefile">src/app/lightning/nodes-rankings-dashboard/nodes-rankings-dashboard.component.ts</context>
<context context-type="linenumber">23</context>
2022-10-17 16:21:29 +04:00
</context-group>
2023-11-26 17:00:34 +09:00
</trans-unit>
<trans-unit id="meta.description.lightning.stats-chart" datatype="html">
<source>See the capacity of the Lightning network visualized over time in terms of the number of open channels and total bitcoin capacity.</source>
2024-01-13 16:57:03 +00:00
<target>Se kapasiteten til Lightning-nettverket visualisert over tid i form av antall åpne kanaler og total bitcoin-kapasitet.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/lightning/statistics-chart/lightning-statistics-chart.component.ts</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">71</context>
2023-11-26 17:00:34 +09:00
</context-group>
</trans-unit>
<trans-unit id="8e623d3cfecb7c560c114390db53c1f430ffd0de" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> confirmation</source>
2024-01-13 16:57:03 +00:00
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> bekreftelse</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/confirmations/confirmations.component.html</context>
<context context-type="linenumber">4</context>
</context-group>
<note priority="1" from="description">Transaction singular confirmation count</note>
<note priority="1" from="meaning">shared.confirmation-count.singular</note>
</trans-unit>
<trans-unit id="bc5b0a2631f0b7bc71aaec6aa6f01af21f9a80d4" datatype="html">
<source><x id="INTERPOLATION" equiv-text="{{ i }}"/> confirmations</source>
2024-01-13 16:57:03 +00:00
<target><x id="INTERPOLATION" equiv-text="{{ i }}"/> bekreftelser</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/confirmations/confirmations.component.html</context>
<context context-type="linenumber">5</context>
</context-group>
<note priority="1" from="description">Transaction plural confirmation count</note>
<note priority="1" from="meaning">shared.confirmation-count.plural</note>
</trans-unit>
<trans-unit id="a001c3d27d5fe4a7a362a6089b5b5020ef8c1c95" datatype="html">
<source>Replaced</source>
2024-01-13 16:57:03 +00:00
<target>Erstattet</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/confirmations/confirmations.component.html</context>
<context context-type="linenumber">12</context>
</context-group>
<note priority="1" from="description">Transaction replaced state</note>
<note priority="1" from="meaning">transaction.replaced</note>
</trans-unit>
<trans-unit id="ef772ce5cf98a47b29175e3d46b8a9816c7990a2" datatype="html">
<source>Unconfirmed</source>
<target>Ubekreftet</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/confirmations/confirmations.component.html</context>
<context context-type="linenumber">18</context>
</context-group>
<note priority="1" from="description">Transaction unconfirmed state</note>
<note priority="1" from="meaning">transaction.unconfirmed</note>
</trans-unit>
<trans-unit id="57a6f49237ac457ecc67fabdf1361a112ccdbf93" datatype="html">
<source>sat/WU</source>
2024-01-13 16:57:03 +00:00
<target>sat/WU</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/fee-rate/fee-rate.component.html</context>
2024-04-03 18:47:16 +09:00
<context context-type="linenumber">4</context>
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/fee-rate/fee-rate.component.html</context>
<context context-type="linenumber">8</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">sat/WU</note>
<note priority="1" from="meaning">shared.sat-weight-units</note>
</trans-unit>
<trans-unit id="5ce2bda884ea801c34a1a6c23627d9a5e08f0a82" datatype="html">
<source>My Account</source>
2024-01-13 16:57:03 +00:00
<target>Min konto</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">28</context>
2023-11-26 17:00:34 +09:00
</context-group>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">36</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">shared.my-account</note>
</trans-unit>
<trans-unit id="1773b1dad3e4b72bca77621985366b9e6a92ae28" datatype="html">
<source>Explore</source>
2024-01-13 16:57:03 +00:00
<target>Utforsk</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">47</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.explore</note>
</trans-unit>
<trans-unit id="52dd0ddd9ab3ea7caafcb4d6ac95e9459ef635f5" datatype="html">
<source>Connect to our Nodes</source>
2024-01-13 16:57:03 +00:00
<target>Koble til nodene våre</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">52</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.connect-to-our-nodes</note>
</trans-unit>
<trans-unit id="1cd6dc07ed789f4013d299b031200224977cbb8b" datatype="html">
<source>API Documentation</source>
2024-01-13 16:57:03 +00:00
<target>API-dokumentasjon</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">53</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.api-documentation</note>
</trans-unit>
<trans-unit id="04dfb6eb5a67d7fa19fb24f0e50324ea63fd8f08" datatype="html">
<source>Learn</source>
2024-01-13 16:57:03 +00:00
<target>Lær</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">56</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.learn</note>
</trans-unit>
<trans-unit id="14f76d294f3ae892e8033d60bb960701cafca66f" datatype="html">
<source>What is a mempool?</source>
2024-01-13 16:57:03 +00:00
<target>Hva er en mempool?</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">57</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">faq.what-is-a-mempool</note>
</trans-unit>
<trans-unit id="8ac787087e3eec254d15a4e16492f8877107087b" datatype="html">
<source>What is a block explorer?</source>
2024-01-13 16:57:03 +00:00
<target>Hva er en blokkutforsker?</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">58</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">faq.what-is-a-block-exlorer</note>
</trans-unit>
<trans-unit id="0ab3729578bb613995fc5c90c4d7aa45588dd2a1" datatype="html">
<source>What is a mempool explorer?</source>
2024-01-13 16:57:03 +00:00
<target>Hva er en mempool utforsker?</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">59</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">faq.what-is-a-mempool-exlorer</note>
</trans-unit>
<trans-unit id="8fe988a9cb02c11f99631ca85721d34d67fc32ff" datatype="html">
<source>Why isn't my transaction confirming?</source>
2024-01-13 16:57:03 +00:00
<target>Hvorfor bekreftes ikke transaksjonen min?</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">60</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">faq.why-isnt-my-transaction-confirming</note>
</trans-unit>
<trans-unit id="03f766a5a2abdbfbdcc2b6135691b9fb1f2ed530" datatype="html">
<source>More FAQs »</source>
2024-01-13 16:57:03 +00:00
<target>Flere vanlige spørsmål »</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">61</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">faq.more-faq</note>
</trans-unit>
<trans-unit id="7a1c82a943fc99d3080aeffeeb7d21f0726ad8cc" datatype="html">
<source>Networks</source>
2024-01-13 16:57:03 +00:00
<target>Nettverk</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">65</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.networks</note>
</trans-unit>
<trans-unit id="f96488094a57809ea9bfe4a2f2bf91af66a0d0a3" datatype="html">
<source>Mainnet Explorer</source>
2024-01-13 16:57:03 +00:00
<target>Mainnet utforsker</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">66</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.mainnet-explorer</note>
</trans-unit>
<trans-unit id="a31347c0f3ec966c373229584cfb7bd6725a0e64" datatype="html">
<source>Testnet Explorer</source>
2024-01-13 16:57:03 +00:00
<target>Testnet utforsker</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">67</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.testnet-explorer</note>
</trans-unit>
<trans-unit id="c9bf4b5d16994e42297cbe174e831a7edd9cfe72" datatype="html">
<source>Signet Explorer</source>
2024-01-13 16:57:03 +00:00
<target>Signet utforsker</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">68</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.signet-explorer</note>
</trans-unit>
<trans-unit id="c127ef3218deed36fb86af83def0b54846f92252" datatype="html">
<source>Liquid Testnet Explorer</source>
2024-01-13 16:57:03 +00:00
<target>Liquid testnet utforsker</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">69</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.liquid-testnet-explorer</note>
</trans-unit>
<trans-unit id="3c07f1c84d76a9999153e87343fd642852bb6d34" datatype="html">
<source>Liquid Explorer</source>
2024-01-13 16:57:03 +00:00
<target>Liquid utforsker</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">70</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.liquid-explorer</note>
</trans-unit>
<trans-unit id="fefee13017c2b85143cd131ee253e327a14053a0" datatype="html">
<source>Tools</source>
2024-01-13 16:57:03 +00:00
<target>Verktøy</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">74</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.tools</note>
</trans-unit>
<trans-unit id="8c23995422ac012b80a2369a878b199c39271906" datatype="html">
<source>Clock (Mined)</source>
2024-01-13 16:57:03 +00:00
<target>Klokke (utvunnet)</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">76</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.clock-mined</note>
</trans-unit>
<trans-unit id="9a91783e9c0f790ed49edae730f9156070ed9dd5" datatype="html">
<source>Legal</source>
2024-01-13 16:57:03 +00:00
<target>Lovlig</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">81</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">footer.legal</note>
</trans-unit>
<trans-unit id="94731fb77c18c6d537337dddc3699f67a0587985" datatype="html">
<source>Terms of Service</source>
<target>Bruksvilkår</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">82</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">Terms of Service</note>
<note priority="1" from="meaning">shared.terms-of-service</note>
</trans-unit>
<trans-unit id="8f3ac0544491bf048120928d39e02a6baeb0b278" datatype="html">
<source>Privacy Policy</source>
<target>Personvernerklæring</target>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">83</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">Privacy Policy</note>
<note priority="1" from="meaning">shared.privacy-policy</note>
</trans-unit>
<trans-unit id="6a0a8485405b9b289101e52a46e282342c8dc9e0" datatype="html">
<source>Trademark Policy</source>
2024-01-13 16:57:03 +00:00
<target>Varemerkepolitikk</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">84</context>
2023-11-26 17:00:34 +09:00
</context-group>
<note priority="1" from="description">Trademark Policy</note>
<note priority="1" from="meaning">shared.trademark-policy</note>
</trans-unit>
2024-04-03 18:47:16 +09:00
<trans-unit id="3acac5d996ebd58adf283129c084bd8f837689f1" datatype="html">
<source>Third-party Licenses</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/global-footer/global-footer.component.html</context>
2024-04-09 16:58:02 +09:00
<context context-type="linenumber">85</context>
2024-04-03 18:47:16 +09:00
</context-group>
<note priority="1" from="description">Third-party Licenses</note>
<note priority="1" from="meaning">shared.trademark-policy</note>
</trans-unit>
2023-11-26 17:00:34 +09:00
<trans-unit id="64dd13424d9486cf3d680d934987ec685bac0b3d" datatype="html">
<source>This is a test network. Coins have no value.</source>
2024-01-13 16:57:03 +00:00
<target>Dette er et testnettverk. Mynter har ingen verdi.</target>
2023-11-26 17:00:34 +09:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/components/testnet-alert/testnet-alert.component.html</context>
<context context-type="linenumber">3</context>
</context-group>
<note priority="1" from="description">warning-testnet</note>
2022-10-17 16:21:29 +04:00
</trans-unit>
2024-04-05 16:46:23 +09:00
<trans-unit id="3399131819685362332" datatype="html">
<source>Address Types</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/filters.utils.ts</context>
<context context-type="linenumber">119</context>
</context-group>
</trans-unit>
<trans-unit id="7779249123661446825" datatype="html">
<source>Behavior</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/filters.utils.ts</context>
<context context-type="linenumber">120</context>
</context-group>
</trans-unit>
<trans-unit id="6290595884142884507" datatype="html">
<source>Heuristics</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/filters.utils.ts</context>
<context context-type="linenumber">122</context>
</context-group>
</trans-unit>
<trans-unit id="2259944601214794924" datatype="html">
<source>Sighash Flags</source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/filters.utils.ts</context>
<context context-type="linenumber">123</context>
</context-group>
</trans-unit>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> år</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> år</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> måned</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> måneder</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> uke</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> uker</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> dag</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> dager</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> time</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> timer</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> minutt</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> minutter</target>
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>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> sekund</target>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">15</context>
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
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>
2023-03-22 13:35:16 +09:00
<target><x id="DATE" equiv-text="counter"/> sekunder</target>
2021-07-17 15:37:34 +03:00
<context-group purpose="location">
<context context-type="sourcefile">src/app/shared/i18n/dates.ts</context>
2021-07-20 15:43:01 +03:00
<context context-type="linenumber">16</context>
2021-07-17 15:37:34 +03:00
</context-group>
</trans-unit>
2021-12-26 11:15:19 +04:00
<trans-unit id="2799825781368047816" datatype="html">
2021-04-26 04:05:55 +04:00
<source>Transaction fee</source>
2021-05-08 01:12:57 +04:00
<target>Transaksjonsavgift</target>
2020-12-05 00:11:40 +09:00
<context-group purpose="location">
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>
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>
