Main Views
QA Views
About Transvision
BETA
Displaying 16 results for the string Glean in nb-NO:
| Entity | nb-NO | en-US |
|---|---|---|
|
Entity
#
all locales
devtools • client • perftools.ftl perftools-thread-jvm-glean.title |
nb-NO
The main threads for the Glean telemetry SDK
|
en-US
The main threads for the Glean telemetry SDK
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl -glean-brand-name |
nb-NO
Glean
|
en-US
Glean
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-about-data-explanation |
nb-NO
For å se gjennom listen over innsamlede data, se
<a data-l10n-name="glean-dictionary-link">{ -glean-brand-name }-ordbok</a>.
|
en-US
To browse the list of collected data, please consult the
<a data-l10n-name="glean-dictionary-link">{ -glean-brand-name } Dictionary</a>.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-adhoc-explanation |
nb-NO
For mer <i>ad hoc</i>-testing,
kan du også bestemme gjeldende verdi for et bestemt instrument
ved å åpne en devtools-konsoll her på <code>about:glean</code>
og bruke <code>testGetValue()</code> API som
<code>Glean.metricCategory.metricName.testGetValue()</code>.
|
en-US
For more <i>ad hoc</i> testing,
you can also determine the current value of a particular piece of instrumentation
by opening a devtools console here on <code>about:glean</code>
and using the <code>testGetValue()</code> API like
<code>Glean.metricCategory.metricName.testGetValue()</code>.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-adhoc-explanation2 |
nb-NO
For mer <i>ad hoc</i>-testing,
kan du også bestemme gjeldende verdi for et bestemt instrument
ved å åpne en konsollen i utviklerverktøy her på <code>about:glean</code>
og bruke <code>testGetValue()</code> API som
<code>Glean.metricCategory.metricName.testGetValue()</code>
for en analyseresultat kalt <code>metric.category.metric_name</code>.
|
en-US
For more <i>ad hoc</i> testing,
you can also determine the current value of a particular piece of instrumentation
by opening a devtools console here on <code>about:glean</code>
and using the <code>testGetValue()</code> API like
<code>Glean.metricCategory.metricName.testGetValue()</code>
for a metric named <code>metric.category.metric_name</code>.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-adhoc-note |
nb-NO
Merk at når du bruker konsollen i utviklerverktøy, bruker du Glean JS API-et.
Dette betyr at analyseresultatkategorier og navn formateres
med <code>camelCase</code> i motsetning til i Rust- og i C++-API-ene.
|
en-US
Please note that you are using the Glean JS API by using the devtools console.
This means the metric category and metric name are formatted in
<code>camelCase</code> unlike in the Rust and C++ APIs.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-glean-android |
nb-NO
<code>MOZ_GLEAN_ANDROID</code>: { $glean-android-define-value }
|
en-US
<code>MOZ_GLEAN_ANDROID</code>: { $glean-android-define-value }
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-header |
nb-NO
Om { -glean-brand-name }
|
en-US
About { -glean-brand-name }
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-interface-description |
nb-NO
<a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name }</a>
er et datainnsamlingsbibliotek som brukes i { -vendor-short-name }-prosjekter.
Dette grensesnittet er designet for å brukes av utviklere og testere for å manuelt
<a data-l10n-name="fog-link">teste instrumentering</a>.
|
en-US
The <a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name }</a>
is a data collection library used in { -vendor-short-name } projects.
This interface is designed to be used by developers and testers to manually
<a data-l10n-name="fog-link">test instrumentation</a>.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-label-for-controls-submit |
nb-NO
Trykk på den foregående knappen for å merke alle { -glean-brand-name }-pingene med taggen din og sende inn den valgte pingen.
(Alle pinger som sendes inn fra da og til du starter applikasjonen på nytt, vil bli merket med
<code>{ $debug-tag }</code>.)
|
en-US
Press the preceding button to tag all { -glean-brand-name } pings with your tag and submit the selected ping.
(All pings submitted from then until you restart the application will be tagged with
<code>{ $debug-tag }</code>.)
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-li-for-visit-gdpv |
nb-NO
<a data-l10n-name="gdpv-tagged-pings-link">Besøk siden { glean-debug-ping-viewer-brand-name } for ping med taggen din</a>.
Det bør ikke ta mer enn noen få sekunder fra du trykker på knappen til pinget ditt kommer.
Noen ganger kan det ta en liten håndfull minutter.
|
en-US
<a data-l10n-name="gdpv-tagged-pings-link">Visit the { glean-debug-ping-viewer-brand-name } page for pings with your tag</a>.
It shouldn’t take more than a few seconds from pushing the button to your ping arriving.
Sometimes it may take a small handful of minutes.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-manual-testing |
nb-NO
Fullstendige instruksjoner er dokumentert i
<a data-l10n-name="fog-instrumentation-test-doc-link">{ -fog-brand-name } instrumenteringstestdokumenter</a>
og i <a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name }-dokumentasjonen</a>,
men kort sagt, for å manuelt teste at instrumenteringen fungerer, bør du:
|
en-US
Full instructions are documented in the
<a data-l10n-name="fog-instrumentation-test-doc-link">{ -fog-brand-name } instrumentation testing docs</a>
and in the <a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name } documentation</a>,
but, in short, to manually test that your instrumentation works, you should:
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-page-title2 |
nb-NO
Om { -glean-brand-name }
|
en-US
About { -glean-brand-name }
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-upload-fake-enabled |
nb-NO
Dataopplasting er deaktivert,
men vi lyver og forteller { glean-sdk-brand-name } at det er aktivert
slik at data fortsatt registreres lokalt.
Merk: Hvis du angir en feilsøkingskode, vil ping bli lastet opp til
<a data-l10n-name="glean-debug-ping-viewer">{ glean-debug-ping-viewer-brand-name }</a> uavhengig av innstillinger.
|
en-US
Data upload is disabled,
but we’re lying and telling the { glean-sdk-brand-name } it is enabled
so that data is still recorded locally.
Note: If you set a debug tag, pings will be uploaded to the
<a data-l10n-name="glean-debug-ping-viewer">{ glean-debug-ping-viewer-brand-name }</a> regardless of settings.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl glean-debug-ping-viewer-brand-name |
nb-NO
Ping-viser for { -glean-brand-name }-feilsøking
|
en-US
{ -glean-brand-name } Debug Ping Viewer
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl glean-sdk-brand-name |
nb-NO
{ -glean-brand-name } SDK
|
en-US
{ -glean-brand-name } SDK
|
Displaying 16 results for the string Glean in en-US:
| Entity | nb-NO | en-US |
|---|---|---|
|
Entity
#
all locales
devtools • client • perftools.ftl perftools-thread-jvm-glean.title |
nb-NO
The main threads for the Glean telemetry SDK
|
en-US
The main threads for the Glean telemetry SDK
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl -glean-brand-name |
nb-NO
Glean
|
en-US
Glean
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-about-data-explanation |
nb-NO
For å se gjennom listen over innsamlede data, se
<a data-l10n-name="glean-dictionary-link">{ -glean-brand-name }-ordbok</a>.
|
en-US
To browse the list of collected data, please consult the
<a data-l10n-name="glean-dictionary-link">{ -glean-brand-name } Dictionary</a>.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-adhoc-explanation |
nb-NO
For mer <i>ad hoc</i>-testing,
kan du også bestemme gjeldende verdi for et bestemt instrument
ved å åpne en devtools-konsoll her på <code>about:glean</code>
og bruke <code>testGetValue()</code> API som
<code>Glean.metricCategory.metricName.testGetValue()</code>.
|
en-US
For more <i>ad hoc</i> testing,
you can also determine the current value of a particular piece of instrumentation
by opening a devtools console here on <code>about:glean</code>
and using the <code>testGetValue()</code> API like
<code>Glean.metricCategory.metricName.testGetValue()</code>.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-adhoc-explanation2 |
nb-NO
For mer <i>ad hoc</i>-testing,
kan du også bestemme gjeldende verdi for et bestemt instrument
ved å åpne en konsollen i utviklerverktøy her på <code>about:glean</code>
og bruke <code>testGetValue()</code> API som
<code>Glean.metricCategory.metricName.testGetValue()</code>
for en analyseresultat kalt <code>metric.category.metric_name</code>.
|
en-US
For more <i>ad hoc</i> testing,
you can also determine the current value of a particular piece of instrumentation
by opening a devtools console here on <code>about:glean</code>
and using the <code>testGetValue()</code> API like
<code>Glean.metricCategory.metricName.testGetValue()</code>
for a metric named <code>metric.category.metric_name</code>.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-adhoc-note |
nb-NO
Merk at når du bruker konsollen i utviklerverktøy, bruker du Glean JS API-et.
Dette betyr at analyseresultatkategorier og navn formateres
med <code>camelCase</code> i motsetning til i Rust- og i C++-API-ene.
|
en-US
Please note that you are using the Glean JS API by using the devtools console.
This means the metric category and metric name are formatted in
<code>camelCase</code> unlike in the Rust and C++ APIs.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-glean-android |
nb-NO
<code>MOZ_GLEAN_ANDROID</code>: { $glean-android-define-value }
|
en-US
<code>MOZ_GLEAN_ANDROID</code>: { $glean-android-define-value }
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-header |
nb-NO
Om { -glean-brand-name }
|
en-US
About { -glean-brand-name }
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-interface-description |
nb-NO
<a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name }</a>
er et datainnsamlingsbibliotek som brukes i { -vendor-short-name }-prosjekter.
Dette grensesnittet er designet for å brukes av utviklere og testere for å manuelt
<a data-l10n-name="fog-link">teste instrumentering</a>.
|
en-US
The <a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name }</a>
is a data collection library used in { -vendor-short-name } projects.
This interface is designed to be used by developers and testers to manually
<a data-l10n-name="fog-link">test instrumentation</a>.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-label-for-controls-submit |
nb-NO
Trykk på den foregående knappen for å merke alle { -glean-brand-name }-pingene med taggen din og sende inn den valgte pingen.
(Alle pinger som sendes inn fra da og til du starter applikasjonen på nytt, vil bli merket med
<code>{ $debug-tag }</code>.)
|
en-US
Press the preceding button to tag all { -glean-brand-name } pings with your tag and submit the selected ping.
(All pings submitted from then until you restart the application will be tagged with
<code>{ $debug-tag }</code>.)
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-li-for-visit-gdpv |
nb-NO
<a data-l10n-name="gdpv-tagged-pings-link">Besøk siden { glean-debug-ping-viewer-brand-name } for ping med taggen din</a>.
Det bør ikke ta mer enn noen få sekunder fra du trykker på knappen til pinget ditt kommer.
Noen ganger kan det ta en liten håndfull minutter.
|
en-US
<a data-l10n-name="gdpv-tagged-pings-link">Visit the { glean-debug-ping-viewer-brand-name } page for pings with your tag</a>.
It shouldn’t take more than a few seconds from pushing the button to your ping arriving.
Sometimes it may take a small handful of minutes.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-manual-testing |
nb-NO
Fullstendige instruksjoner er dokumentert i
<a data-l10n-name="fog-instrumentation-test-doc-link">{ -fog-brand-name } instrumenteringstestdokumenter</a>
og i <a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name }-dokumentasjonen</a>,
men kort sagt, for å manuelt teste at instrumenteringen fungerer, bør du:
|
en-US
Full instructions are documented in the
<a data-l10n-name="fog-instrumentation-test-doc-link">{ -fog-brand-name } instrumentation testing docs</a>
and in the <a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name } documentation</a>,
but, in short, to manually test that your instrumentation works, you should:
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-page-title2 |
nb-NO
Om { -glean-brand-name }
|
en-US
About { -glean-brand-name }
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl about-glean-upload-fake-enabled |
nb-NO
Dataopplasting er deaktivert,
men vi lyver og forteller { glean-sdk-brand-name } at det er aktivert
slik at data fortsatt registreres lokalt.
Merk: Hvis du angir en feilsøkingskode, vil ping bli lastet opp til
<a data-l10n-name="glean-debug-ping-viewer">{ glean-debug-ping-viewer-brand-name }</a> uavhengig av innstillinger.
|
en-US
Data upload is disabled,
but we’re lying and telling the { glean-sdk-brand-name } it is enabled
so that data is still recorded locally.
Note: If you set a debug tag, pings will be uploaded to the
<a data-l10n-name="glean-debug-ping-viewer">{ glean-debug-ping-viewer-brand-name }</a> regardless of settings.
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl glean-debug-ping-viewer-brand-name |
nb-NO
Ping-viser for { -glean-brand-name }-feilsøking
|
en-US
{ -glean-brand-name } Debug Ping Viewer
|
|
Entity
#
all locales
toolkit • toolkit • about • aboutGlean.ftl glean-sdk-brand-name |
nb-NO
{ -glean-brand-name } SDK
|
en-US
{ -glean-brand-name } SDK
|
APIThese results are also available as an API request to search in
nb-NO or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.