Project Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
darktable 27% 3,293 102,761 671,095 3,293 0 0 0

Overview

Language code zh_Hant
Aliased language codes tchinese, zh_cht, zhtw, zh_tw, zh_hant_tw, zh_hant@zh, zh_cmn_hant, cht, zho
Text direction Left to right
Number of speakers 38,612,556
Plural: Default plural 2 translations
Number of plurals 1
Plural type None
Plurals
Plural formula 0
Plural: Qt Linguist plural 0 translations
Number of plurals 1
Plural type None
Plurals
Plural formula 0
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 4,547 138,716 909,877
Approved 0% 0 0% 0 0% 0
Waiting for review 27% 1,254 25% 35,955 26% 238,782
Translated 27% 1,254 25% 35,955 26% 238,782
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 72% 3,293 74% 102,761 73% 671,095
Last 12 months Previous

Activity in last 12 months

0 changes 166 changes 0 changes 0 changes 0 changes 0 changes 192 changes 0 changes 1,330 changes 0 changes 0 changes 0 changes 0 changes 0 changes 15 changes 0 changes 0 changes 414 changes 0 changes 443 changes 0 changes 3 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

138 k
Hosted words
4,547
Hosted strings
27%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+27%
—
Contributors
+100%
User avatar elstoc

Resource updated

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
Parsing of the "po/content.zh_Hant.po" file was enforced. yesterday
User avatar None

String added in the repository

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
opencl\_synch\_cache
: If set to "true", this parameter will force darktable to fetch image buffers from your GPU after each module and store them in its pixelpipe cache. This is a resource consuming operation, but can make sense depending on your GPU (including if the GPU is rather slow). In this case darktable might in fact save some time when module parameters have changed, as it can go back to some cached intermediate state and reprocess only part of the pixelpipe. In many cases this parameter should be set to "active module" (the default), which will only cache the input of the currently-focused module.
 
yesterday
User avatar None

String added in the repository

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
cldevice\_version\_canonicalname\_building
: This option is used when compiling OpenCL kernels and may be provided for performance tuning or to work around bugs. You must remove any existing kernels in order to recompile them with the new options. Provide an empty string to recompile without any options. Remove the setting entirely to recompile with default options, default is `-cl-fast-relaxed-math`
 
yesterday
User avatar None

String added in the repository

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
: The default of 400MB should be fine for most systems. If you find you run into performance problems due to darktable falling back to CPU, try changing it to 600 or disabling "tune for memory size".
 
yesterday
User avatar None

String added in the repository

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
: If you are certain that no apps (or your OS) make use of the specific device you can set this parameter to 1 for the otherwise-unused device so that darktable will use all of that device's memory.
 
yesterday
User avatar None

String added in the repository

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
: If you set this parameter to zero (`0`) then, on the first run of a pixelpipe, darktable will attempt to determine how much GPU memory is actually available and use this (with a safety-margin of 100MB) as the maximum amount of memory that darktable will use, for the remainder of your session. This is usually safe unless you start other applications (that use a reasonable amount of GPU memory) while darktable is running. Otherwise, use of this option could lead to out-of-memory errors, which will cause darktable to fall back to CPU, significantly reducing performance. You may switch this option off and on again to prompt darktable to perform its memory calculation again (at the start of the next pipe run). Note that there are known issues with memory auto-detection on newer Nvidia drivers so auto-detection should be used with care and is therefore disabled by default.
 
yesterday
User avatar None

String added in the repository

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
forced headroom (default 400)
: The amount of memory (in MB) that will **not** be used by darktable during OpenCL processing. This setting is only valid if you set [preferences > processing > tune OpenCL performance](../preferences-settings/processing/#cpu--gpu--memory) to "memory size".
 
yesterday
User avatar None

String added in the repository

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
A second device-specifc configuration key is also provided, which takes into account both the device name **and** the device id (just in case you have two identical devices). In this case, the usual key name `cldevice_version_canonicalname` is followed by `_idX` with X being the device id. For example, if the above example device was referred to as device 0, the second configuration setting would (by default) be `cldevice_v4_quadrortx4000_id0=400`.
 
yesterday
User avatar None

String added in the repository

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
i. benchmark
: When darktable detects a new device on your system it will do a small benchmark and store the result here. You can change this back to 0 to force darktable to redo the benchmark but in most cases **you should not edit this setting**.
 
yesterday
User avatar None

String added in the repository

  1. darktable
  2. dtdocs
  3. Chinese (Traditional)
h. disable device
: _0 = enable device; 1 = disable device_
: If darktable detects a malfunctioning device it will automatically mark it as such by setting this parameter to 1. If you have a device that reports a lot of errors you can manually disable it by setting this field to 1.
 
yesterday
Browse all changes for this language