BETA

Transvision

Filter by folder:

Show all results devtools toolkit

Displaying 16 results for the string Glean in ko:

Entity ko en-US
Entity # all locales devtools • client • perftools.ftl
perftools-thread-jvm-glean.title
ko
Glean 원격 분석 SDK의 메인 스레드
en-US
The main threads for the Glean telemetry SDK
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
-glean-brand-name
ko
Glean
en-US
Glean
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
about-glean-about-data-explanation
ko
수집된 데이터 목록을 찾아보려면 <a data-l10n-name="glean-dictionary-link">{ -glean-brand-name } 사전</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
ko
더 많은 <i>임시</i> 테스트를 위해 여기 <code>about:glean</code>에서 개발자 도구 콘솔을 열고 <code>Glean.metricCategory.metricName.testGetValue()</code> 같은 <code>testGetValue()</code> API를 사용하여 특정 계측 부분의 현재 값을 확인할 수도 있습니다.
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
ko
더 많은 <i>임시</i> 테스트를 위해 여기 <code>about:glean</code>에서 개발자 도구 콘솔을 열고 <code>metric.category.metric_name</code>이라는 메트릭에 대해 <code>Glean.metricCategory.metricName.testGetValue()</code> 같은 <code>testGetValue()</code> API를 사용하여 특정 계측 부분의 현재 값을 확인할 수도 있습니다.
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
ko
devtools 콘솔을 사용하여 Glean JS API를 사용하고 있습니다. 이는 메트릭 카테고리와 메트릭 이름이 Rust 및 C++ API와 달리 <code>camelCase</code> 형식으로 지정됨을 의미합니다.
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
ko
<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
ko
{ -glean-brand-name } 정보
en-US
About { -glean-brand-name }
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
about-glean-interface-description
ko
<a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name }</a>는 { -vendor-short-name } 프로젝트에서 사용되는 데이터 수집 라이브러리입니다. 이 인터페이스는 개발자와 테스터가 <a data-l10n-name="fog-link">테스트 계측</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
ko
이전 버튼을 눌러 모든 { -glean-brand-name } 핑에 태그를 지정하고 선택한 핑을 제출하세요. (그때부터 애플리케이션을 다시 시작할 때까지 제출된 모든 핑은 <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
ko
<a data-l10n-name="gdpv-tagged-pings-link">태그가 있는 핑에 대한 { glean-debug-ping-viewer-brand-name } 페이지를 방문하세요</a>. 버튼을 누른 후 핑이 도착할 때까지 몇 초 이상 걸리지 않습니다. 때로는 몇 분 정도 걸릴 수 있습니다.
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
ko
전체 지침은 <a data-l10n-name="fog-instrumentation-test-doc-link">{ -fog-brand-name } 계측 테스트 문서</a> 및 <a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name } 문서</a>에 문서화되어 있습니다. 하지만 간단히 말해서 계측이 작동하는지 수동으로 테스트하려면 다음을 수행해야 합니다:
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
ko
{ -glean-brand-name } 정보
en-US
About { -glean-brand-name }
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
about-glean-upload-fake-enabled
ko
데이터 업로드가 비활성화되었지만 데이터가 여전히 로컬에 기록되도록 { glean-sdk-brand-name }에게 활성화되었다고 말하고 있습니다. 참고: 디버그 태그를 설정하면 설정과 상관없이 핑이 <a data-l10n-name="glean-debug-ping-viewer">{ glean-debug-ping-viewer-brand-name }</a>에 업로드됩니다.
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
ko
{ -glean-brand-name } 디버그 핑 뷰어
en-US
{ -glean-brand-name } Debug Ping Viewer
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
glean-sdk-brand-name
ko
{ -glean-brand-name } SDK
en-US
{ -glean-brand-name } SDK

Displaying 16 results for the string Glean in en-US:

Entity ko en-US
Entity # all locales devtools • client • perftools.ftl
perftools-thread-jvm-glean.title
ko
Glean 원격 분석 SDK의 메인 스레드
en-US
The main threads for the Glean telemetry SDK
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
-glean-brand-name
ko
Glean
en-US
Glean
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
about-glean-about-data-explanation
ko
수집된 데이터 목록을 찾아보려면 <a data-l10n-name="glean-dictionary-link">{ -glean-brand-name } 사전</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
ko
더 많은 <i>임시</i> 테스트를 위해 여기 <code>about:glean</code>에서 개발자 도구 콘솔을 열고 <code>Glean.metricCategory.metricName.testGetValue()</code> 같은 <code>testGetValue()</code> API를 사용하여 특정 계측 부분의 현재 값을 확인할 수도 있습니다.
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
ko
더 많은 <i>임시</i> 테스트를 위해 여기 <code>about:glean</code>에서 개발자 도구 콘솔을 열고 <code>metric.category.metric_name</code>이라는 메트릭에 대해 <code>Glean.metricCategory.metricName.testGetValue()</code> 같은 <code>testGetValue()</code> API를 사용하여 특정 계측 부분의 현재 값을 확인할 수도 있습니다.
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
ko
devtools 콘솔을 사용하여 Glean JS API를 사용하고 있습니다. 이는 메트릭 카테고리와 메트릭 이름이 Rust 및 C++ API와 달리 <code>camelCase</code> 형식으로 지정됨을 의미합니다.
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
ko
<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
ko
{ -glean-brand-name } 정보
en-US
About { -glean-brand-name }
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
about-glean-interface-description
ko
<a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name }</a>는 { -vendor-short-name } 프로젝트에서 사용되는 데이터 수집 라이브러리입니다. 이 인터페이스는 개발자와 테스터가 <a data-l10n-name="fog-link">테스트 계측</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
ko
이전 버튼을 눌러 모든 { -glean-brand-name } 핑에 태그를 지정하고 선택한 핑을 제출하세요. (그때부터 애플리케이션을 다시 시작할 때까지 제출된 모든 핑은 <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
ko
<a data-l10n-name="gdpv-tagged-pings-link">태그가 있는 핑에 대한 { glean-debug-ping-viewer-brand-name } 페이지를 방문하세요</a>. 버튼을 누른 후 핑이 도착할 때까지 몇 초 이상 걸리지 않습니다. 때로는 몇 분 정도 걸릴 수 있습니다.
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
ko
전체 지침은 <a data-l10n-name="fog-instrumentation-test-doc-link">{ -fog-brand-name } 계측 테스트 문서</a> 및 <a data-l10n-name="glean-sdk-doc-link">{ glean-sdk-brand-name } 문서</a>에 문서화되어 있습니다. 하지만 간단히 말해서 계측이 작동하는지 수동으로 테스트하려면 다음을 수행해야 합니다:
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
ko
{ -glean-brand-name } 정보
en-US
About { -glean-brand-name }
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
about-glean-upload-fake-enabled
ko
데이터 업로드가 비활성화되었지만 데이터가 여전히 로컬에 기록되도록 { glean-sdk-brand-name }에게 활성화되었다고 말하고 있습니다. 참고: 디버그 태그를 설정하면 설정과 상관없이 핑이 <a data-l10n-name="glean-debug-ping-viewer">{ glean-debug-ping-viewer-brand-name }</a>에 업로드됩니다.
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
ko
{ -glean-brand-name } 디버그 핑 뷰어
en-US
{ -glean-brand-name } Debug Ping Viewer
Entity # all locales toolkit • toolkit • about • aboutGlean.ftl
glean-sdk-brand-name
ko
{ -glean-brand-name } SDK
en-US
{ -glean-brand-name } SDK
Please enable JavaScript. Some features won't be available without it.