Sheet nl_appearance
The nl_appearance sheet controls global appearance, language settings, and other visual configuration as well as your project's identity.
Table Customization
on sheet nl_appearance
A fixed set of named configuration items. The Item column contains predefined keywords, case-sensitive; you only edit the Value column (or Value:en, Value:fr, etc. for per-language overrides in multilingual projects). Skip any items you are happy with at their default. Typically you will want to fill in at least [object Object] and [object Object].
Column Item
member of table Customization on sheet nl_appearance
Predefined keywords, each controlling one aspect of the app. See the overview table below for the full list, defaults, and expected value format.
Project name, About section, How to cite, Data sheets names, Color theme hue, Date format, Month names, Precache max file size, Precache max total sizeHow to use: Enter only the rows you want to change from their defaults. Copy the item name exactly as shown - item names are case-sensitive.
Customization options overview
| Item | Default | Value format and description |
|---|---|---|
Project name | New project | Short project name shown in the app header. |
About section | Plain text or Markdown for the About page, or for longer texts an F: directive ( | |
How to cite | Plain text or Markdown citation string shown to users in the About page. | |
Data sheets names | checklist | Comma-separated list of data sheets names, only needed if you have renamed the tab away from the default |
Color theme hue | 212 | Integer 0-360. Use an online HSL picker (e.g. https://hslpicker.com) to find your hue. |
Date format | YYYY-MM-DD | day.js format string, e.g. MMM D, YYYY or DD/MM/YYYY. |
Month names | Comma-separated list of exactly 12 month names starting with January, e.g. Janvier, Février, Mars, ... | |
Precache max file size | 0.5 | Maximum size in MB of a single media file to cache for offline use. Format as a number. |
Precache max total size | 200 | Maximum total size in MB of all precached media assets. Format as a number. |
Column Value
member of table Customization on sheet nl_appearance
The configured value for the item on the same row. See the Item overview table for the expected format and default of each item. Supports multilingual column suffixes for settings that are per-language (Value:en, Value:fr, etc.).
How to use: Fill in only the items you need to change from their defaults. Leave the Value cell empty for items you are happy with at their default.
Bilingual customization values
| Item | Value:en | Value:fr |
|---|---|---|
Project name | Birds of Lamèque Island | Oiseaux de l'Île-de-Lamèque |
About section | This checklist is a collaborative effort of ... | F:about.fr.md |
How to cite | Birds of Lamèque Island checklist. Author: Anicet Paulin (2024). https://example.com/lameque-checklist | Liste des oiseaux de l'Île-de-Lamèque. Auteur : Anicet Paulin (2024). https://example.com/lameque-checklist |
Date format | MMM D, YYYY | DD/MM/YYYY |
Color theme hue | 200 | 97 |
Data sheets names | landbirds, seabirds | landbirds, seabirds |
Month names | January, February, March, April, May, June, July, August, September, October, November, December | Janvier, Février, Mars, Avril, Mai, Juin, Juillet, Août, Septembre, Octobre, Novembre, Décembre |
Table Category display
on sheet nl_appearance
Defines how the raw values of a category column (see Data type) are displayed - both textually (replacing stored codes with human-readable labels) and graphically (with colored badge styling). Each row targets one value, or a wildcard group of values, for a specific column.
In every row Raw value is matched against the cell content from the data sheet, and the two optional outputs - Label and the color columns - are applied when it matches. Fill in Label to substitute a human-readable string in place of the raw value; leave it empty to keep the raw value as-is. Fill in color columns to render the value as a styled badge; leave them empty for plain text. Any combination is valid: label only, styling only, or both at once.
This means you can freely choose how you store data: use compact controlled-vocabulary codes (IUCN Red List codes, Darwin Core terms, habitat codes, etc. keeping those controlled machine-readable vocabularies for DwC-A export) and translate them to human-readable labels here, or write full labels directly and skip the translation step. Styling is always optional - for large or open-ended vocabularies it is perfectly valid to use category without any color definitions.
This table can be left completely empty if no special display or styling is required. The categorical filter will still work as expected.
WARNING
Data type must be set to category for this table to have any effect. Neither label substitution nor badge styling applies to columns with any other data type.
- Columns:
- Column name |
- Raw value |
- Label |
- Background color |
- Text color |
- Border color
Column Column name
member of table Category display on sheet nl_appearance
The data path of the column whose values this row applies to. Multiple rows sharing the same Column name are evaluated in order; the first matching row wins.
Two shorthand notations are supported in addition to exact column names:
- Numbered-array shorthand (
habit#): a trailing#matches all numbered instances of that column (habit1,habit2, etc.). This notation is resolved at render time. - One-level child wildcard (
status.*): a trailing.*is expanded at compile time into one logical copy of this row for every direct child ofstatusdeclared in Custom data definition (e.g.status.nc,status.vu,status.fj). Only immediate children are matched — grandchildren such asstatus.nc.subare excluded. If an explicit row for a given child already exists anywhere in this table, that explicit row takes precedence and the wildcard does not generate a duplicate. The wildcard must appear as the last two characters after a valid prefix; patterns such as*.status,status.*.sub, orstatus*are rejected with an error.
dataPathWithWildcardAccepted content: Accepts a plain data path, a data path ending with # for numbered-array columns, or a data path ending with .* for one-level child wildcard expansion. Any other use of * is an error.
How to use: Use the exact column name as declared with category data type in Custom data definition for a single-column row. Use the # suffix for numbered-array columns (habit# covers habit1, habit2, …). Use the .* suffix when several sibling columns share identical badge definitions — instead of repeating the rows once per column, write them once with e.g. status.* and the compiler generates the copies automatically. Explicit rows always override wildcard-generated ones, so you can use a wildcard as a base and override individual children where needed.
TIP
The .* wildcard only covers direct children. If your data structure has status.nc, status.vu, and status.fj as leaf columns in Custom data definition, a single status.* row covers all three. A deeper path such as status.nc.sub would not be covered.
WARNING
The .* wildcard is expanded from the Custom data definition table. A column must be declared there for the wildcard to reach it. Columns that exist only in your data sheet but are not declared in Custom data definition are never matched.
Wildcard covering sibling status columns
Instead of repeating the same three badge rows for status.nc, status.vu, and status.fj separately, a single status.* row covers all three. An explicit override for status.nc takes precedence over the wildcard for that column only.
| Column name | Raw value | Label | Background color | Text color | comment |
|---|---|---|---|---|---|
status.* | e | Endemic | #000000 | #cd3030 | Applies to status.nc, status.vu, status.fj, and any future status.* child |
status.* | n | Native | #000000 | #FFFFFF | |
status.* | i | Introduced | #cd3030 | #ffcdcd | |
status.nc | e | Endemic NC | #000000 | #aa0000 | Explicit override for status.nc only; wildcard row is skipped for this column |
Column Raw value
member of table Category display on sheet nl_appearance
The value (or wildcard pattern) matched against the raw cell content from the data sheet. This column is required on every row - it is always the matcher.
The * character is the only wildcard and matches any sequence of characters (including none). A pattern with no * must match the entire cell value exactly (case-insensitive). A single bare * matches everything and can serve as a catch-all fallback placed last among a column's rows.
Accepted content: Case-insensitive pattern. * matches any sequence of characters. A pattern with no * requires full equality. First match among all rows for the column wins.
How to use: For coded vocabularies (IUCN codes, Darwin Core terms, breeding codes, etc.), enter the exact code stored in your data sheet and fill in Label to display a human-readable replacement. For data already stored as readable values, enter the value directly - use * wildcards to style a whole family of values with one row (*tree* matches tree, treelet, epiphytic tree, etc.). Place a row with * last among a column's rows as a catch-all to style any value not matched by earlier rows.
IUCN Red List - code translation and badge styling
Each of the first rows stores a short IUCN code in the data sheet and translates it to its full label while applying a color. The Conservation Dependent row stores the full label directly (no translation needed) and only adds a color. The final * row is a catch-all that colors any unexpected value grey. A multilingual project could use translated labels (e.g. Label:en, Label:fr) columns.
| Column name | Raw value | Label | Background color | Text color |
|---|---|---|---|---|
redlist | LC | Least Concern | #006666 | white |
redlist | NT | Near Threatened | #006666 | #9acd9a |
redlist | VU | Vulnerable | #cd9a00 | #ffffcd |
redlist | EN | Endangered | #cd6630 | #ffcd9a |
redlist | CR | Critically Endangered | #cd3030 | #ffcdcd |
redlist | DD | Data Deficient | gray | white |
redlist | NE | Not Evaluated | gray | white |
redlist | Conservation Dependent | #006666 | white | |
redlist | * | gray | white |
Habit - wildcard styling, no translation
The data sheet already contains readable values. Label is left empty on every row so values are displayed as stored. * wildcards in Raw value apply one color to a whole family of values without listing each variant individually.
| Column name | Raw value | Label | Background color | Text color | comment |
|---|---|---|---|---|---|
habit# | *tree* | #668dbb | white | Matches 'tree', 'treelet', 'epiphytic tree', etc. | |
habit# | shrub | #5e9f5c | white | Exact match for 'shrub' | |
habit# | *herb* | #9acd9a | white | Matches 'herb', 'herbaceous climber', etc. | |
habit# | * | #cccccc | black | Catch-all for any other value |
Column Label
member of table Category display on sheet nl_appearance
The human-readable text displayed to users in place of the raw cell value. When filled in, the raw value is replaced by this label throughout the app - in the checklist display, the detail panel, search results, and filter chips. When left empty, the raw value is displayed as-is.
How to use: Fill this in to translate codes into readable labels (e.g. LC → Least Concern, N → Native). Leave empty when the data already contains the labels you want to display, or when you only want to apply badge styling without renaming the value. For multilingual projects, add one Label:langcode column per language (e.g. Label:en, Label:fr).
Column Background color
member of table Category display on sheet nl_appearance
(empty)CSS color for the category badge background. Accepts any valid CSS color notation: named colors (green), hex (#5e9f5c), RGB, HSL, etc. Leave empty for a transparent background (value renders as plain text).
CSS colorHow to use: Choose a color that provides sufficient contrast with the Text color for readability. Leave empty on rows that only define a label translation with no badge styling.
Column Text color
member of table Category display on sheet nl_appearance
(empty)CSS color for the category badge text. Leave empty to use the default text color.
CSS colorHow to use: Use white or bright colors for dark backgrounds and black or dark colors for light backgrounds.
Column Border color
member of table Category display on sheet nl_appearance
(empty)CSS color for the category badge border. Leave empty to use the default border. Set to the same color as the background to produce a borderless badge.
CSS colorHow to use: Omit for most categories. Use to add a subtle outline when the badge background is close in hue to the surrounding page background.
Table Map regions information
on sheet nl_appearance
Defines the human-readable name for each geographic region code used in mapregions data columns. Every region code that appears in your data must have a matching entry here - missing codes are logged as errors and displayed as raw codes in the UI.
Leave this table empty if you do not use mapregions data columns.
- Columns:
- Region code |
- Region name
Column Region code
member of table Map regions information on sheet nl_appearance
The short code identifying this geographic region, matching the codes used in mapregions data columns.
pattern (regex)^[a-z]+$ - only one or more lowercase letters a-zHow to use: Use the same codes as in your data sheet mapregions cells. Codes must be all-lowercase letters a-z only - no digits, no hyphens. The code must exactly match the class attribute of the SVG element corresponding to the map region if you use a choropleth map.
Region codes and names
Suppose you have a breedingRange column in your data sheet with mapregions data type and your SVG map has regions marked with the same codes.
| Region code | Region name |
|---|---|
mos | Moravinan-Silesian region |
olo | Olomouc region |
smo | South Moravian Region |
In your Custom data definition table, you would have the breedingRange column is a form similar to this (abbreviated example):
| Column name | Title | Data type | Template | comment |
|---|---|---|---|---|
breedingRange | Breeding range in Czech Republic | mapregions | maps/czechia.svg | Your |
... | ... | ... | ... | other config for unrelated data columns |
Column Region name
member of table Map regions information on sheet nl_appearance
The human-readable name for this region, shown in the UI and in the inline text list on taxon cards. Supports multilingual variants (Region name:en, Region name:fr).
How to use: Add multilingual variants (Region name:en, Region name:fr) for translated place names.
Multilingual region names
If your project is multilingual, add one Region name:langcode column per language to provide translated region names. The app displays the appropriate translation based on the user's language preference.
| Region code | Region name:en | Region name:cs |
|---|---|---|
mos | Moravinan-Silesian region | Moravskoslezský kraj |
olo | Olomouc region | Olomoucký kraj |
smo | South Moravian Region | Jihomoravský kraj |
Table Map regions legend
on sheet nl_appearance
Controls how mapregions status values are translated into colors on the SVG map and what text appears in the map legend and inline region lists.
Three modes are available:
- Category (default, Legend type column empty or
category): the Status code is matched as an exact string. One row per distinct status value, plus an optional fallback row with an empty Status code that colors any region not matched by another row. - Gradient (Legend type
gradient): the Status code is a numeric anchor position. At least two rows required defining the gradient start and end anchors. Colors are smoothly interpolated between anchors. Use for continuous numeric data. - Stepped (Legend type
stepped): anchor positions as above, but color assignment is discrete - each value snaps to the bin whose anchor it exceeds. Use to visually divide the numeric data into discrete categorzed groups.
You can combine Category with either Gradient or Stepped mode to cover cases when distinct categories live together with numeric data (e.g. a vegetation survey with coverage percentual values per region, but some regions classified as 'no data' or 'monitoring in progress'). The engine always checks for an exact categorical match first; numeric interpolation is the fallback. This lets you mix numeric data with categorical exception codes (e.g. ND, E) in the same column.
Leave this table empty if you do not use mapregions data columns. See Distribution maps with mapregions for the full color engine explanation and worked examples.
TIP
For the full anchor notation reference, the per-taxon color scale behaviour, and worked examples covering every mode and combination, see Distribution maps with mapregions → Anchor value notation.
- Columns:
- Column name |
- Status code |
- Fill color |
- Legend |
- Appended legend |
- Legend type
Column Column name
member of table Map regions legend on sheet nl_appearance
(empty)Restricts this legend row to a specific mapregions data column. Enter the exact data path as declared in the Custom data definition table (e.g. map, maps.europe, distribution). Leave empty to apply the row globally to every mapregions column. The compound pair of Column name and Status code must be unique across the table - the same Status code may appear on multiple rows provided each row names a different column.
data pathTwo independent gradients scoped to different columns
| Column name | Status code | Fill color | Legend | Legend type |
|---|---|---|---|---|
map.world | 0% | #f7fbff | Very rare | gradient |
map.world | 100% | #08306b | Well documented | gradient |
map.country | -2s | #d73027 | Low effort | gradient |
map.country | 2s | #1a9641 | High effort | gradient |
Column Status code
member of table Map regions legend on sheet nl_appearance
(empty)The status value or anchor position for this row. Interpretation depends on the Legend type of this row.
For category rows (Legend type category): a plain text string matched exactly against the data cell content (e.g. native, introduced, ND)..
For gradient and stepped rows: a numeric anchor position in one of five notations. All data values for the column must be parseable numbers (or matched by a categorical row).
- Raw value: a plain number (e.g.
7.6,0,-5). Anchor at that absolute value. Use for fixed biological thresholds. - Percentage of range: a number followed by
%(e.g.0%,50%,100%). Resolves between dataset min and max. Use when relative position matters more than absolute value. - Percentile: a number followed by
p(e.g.25p,75p). Resolves to that percentile of the data distribution. Use to highlight distributional extremes regardless of absolute scale. - Standard deviation: a number followed by
s(e.g.-2s,0s,1.5s). Resolves to that many σ from the dataset mean. Use to visualise statistical outliers. - Centered / diverging: syntax
[±magnitude][modifier]c[centerValue](e.g.-100%c0,0c28,-2sc28). Diverges from a declared center point. Use for change maps or deviation from a target baseline.
The five numeric anchor types may be mixed freely for advanced cases, but most of the time using a single anchor type is sufficient. See Anchor value notation for full explanations and the per-taxon dataset semantics.
Accepted content: The compound pair (Column name, Status code) must be unique across the table.
How to use: For simple categorical maps, enter the status strings used in your data. For numeric data, choose the anchor notation that best matches the data's nature and the intended visual communication.
Categorical statuses
| Status code | Fill color | Legend | Legend type |
|---|---|---|---|
native | #1a9641 | Native | category |
introduced | #d73027 | Introduced | category |
#aaaaaa | Not assessed | category |
Gradient (adaptive scale)
| Status code | Fill color | Legend | Legend type |
|---|---|---|---|
0% | #f7fbff | Rare | gradient |
50% | #6baed6 | Moderate | gradient |
100% | #08306b | Abundant | gradient |
Column Fill color
member of table Map regions legend on sheet nl_appearance
The color applied to matching regions on the SVG map and to the legend swatch. For category rows this is a fixed color. For gradient rows it is the color at this anchor point, with colors between anchors smoothly interpolated. For stepped rows it is the color of the bin whose threshold begins at this anchor.
CSS colorHow to use: Choose perceptually distinct and accessible colors. For gradients, use a sequential or diverging ramp that communicates the data direction clearly.
Column Legend
member of table Map regions legend on sheet nl_appearance
Label shown for this row in the map legend. For category rows this label is always displayed. For gradient and stepped rows, only rows with a non-empty Legend value appear in the legend - you can define intermediate anchor rows without cluttering the legend by leaving their Legend cells empty.
How to use: Label the outermost anchors and any semantically important midpoints (e.g. Low, Median, High). Leave intermediate gradient anchors unlabelled to keep the legend clean.
Column Appended legend
member of table Map regions legend on sheet nl_appearance
Text appended directly after the region name in the inline text list on the taxon card (visible when placement is not details). For example, a status introduced with Appended legend introduced produces Germany *(introduced)*. Supports Markdown.
Only meaningful for category and stepped rows - for gradient rows this field is ignored, as the raw data value is shown instead of a dynamically computed label.
How to use: Use for categorical status values where the status name adds meaningful context to the region name in the inline list. Leave empty when the region name alone is sufficient.
Breeding atlas with appended status
| Status code | Fill color | Legend | Appended legend | Legend type |
|---|---|---|---|---|
c | #1a9641 | Confirmed breeding | confirmed breeding | |
p | #a6d96a | Probable breeding | probable breeding | |
v | #636363 | Vagrant | vagrant |
Depending on your data and other settings, this could render as something like:
Germany (confirmed breeding), Spain (vagrant), France (probable breeding) Column Legend type
member of table Map regions legend on sheet nl_appearance
Controls how this row is interpreted by the rendering engine.
category: the Status code is a plain text string matched exactly against data cell content. The Fill color is applied directly to any matching region. This covers simple presence/absence, named statuses, and categorical override rows mixed into a gradient/stepped column.gradient: the Status code is an anchor position (numeric anchors notation). Colors are smoothly interpolated between adjacent anchors. Requires at least twogradientrows for the same column. Use for continuous data (population density, temperature, index values).stepped: the Status code is an anchor position (numeric anchors notation). A value falls into the bin whose anchor is the highest anchor not exceeding the value - equivalent to histogram binning. No color blending. Use for crisp color bands at defined thresholds (abundance classes, IUCN criterion scores).
For a mixed column (e.g. a gradient with a categorical exception for 'No Data'), define the gradient anchors with gradient and the exception row with empty/category. The engine always checks for an exact categorical string match first; numeric anchor interpolation is the fallback.
category, gradient, steppedHow to use: Use category for named status values. Use gradient for continuous numeric data. Use stepped for numeric data best communicated as discrete bins.
Mixed column: gradient with categorical overrides
| Status code | Fill color | Legend | Appended legend | Legend type |
|---|---|---|---|---|
0% | #d7191c | Bare / sparse | gradient | |
100% | #1a9641 | Dense vegetation | gradient | |
ND | #aaaaaa | No satellite data | no data | |
FL | #000000 | Fire loss | destroyed by fire |
Table Search category custom order
on sheet nl_appearance
Overrides the default alphabetical ordering of filter values in the sidebar filter dropdowns. Items appear in the filter in the order they appear in this table. Any data value not listed here is appended alphabetically after the explicitly ordered values.
A typical use case is the Red List category, where severity order (Critically Endangered → Endangered → Vulnerable…) is more meaningful than alphabetical. Another is a topmost taxonomic group where you want prominent categories to appear first.
If you use mapregions columns, you can also control the order of region names in the filter and group them if needed. The Values ordered containing the region name from Map regions information, not the region code.
This table can be left completely empty if alphabetical ordering is acceptable for all your filters.
- Columns:
- Column name |
- Group title |
- Values ordered
Column Column name
member of table Search category custom order on sheet nl_appearance
The data path of the filtered column whose values should be reordered. Must match a column that has a Search category title set in the Custom data definition table.
The same two shorthand notations supported in Column name also work here:
- Numbered-array shorthand (
habit#): covers all numbered instances at render time. - One-level child wildcard (
status.*): expanded at compile time into one copy of each row for every direct child ofstatusdeclared in Custom data definition. Explicit rows for a given child always take precedence over wildcard-generated ones.
dataPathWithWildcardHow to use: Enter the column name exactly as it appears in the Custom data definition table. Use .* when several sibling columns share the same filter value order — write the ordering rows once with e.g. status.* and the compiler generates copies for each child automatically.
TIP
The .* wildcard is particularly useful when the same controlled vocabulary (e.g. Endemic / Native / Introduced) is used across multiple per-region status columns such as status.nc, status.vu, and status.fj. One set of ordering rows with status.* keeps the filter order consistent across all of them without repetition.
Red List in severity order
| Column name | Group title | Values ordered |
|---|---|---|
redlist | Critically Endangered | |
redlist | Endangered | |
redlist | Vulnerable | |
redlist | Near Threatened | |
redlist | Least Concern | |
redlist | Data Deficient | |
redlist | Not Evaluated |
Column Group title
member of table Search category custom order on sheet nl_appearance
Assigns multiple filter values under a shared group heading with a collective tick/untick button. All rows sharing the same Group title value (for the same Column name) are displayed together under that heading. Individual values within the group can still be ticked and unticked independently.
How to use: Use to group related filter values that users would often select together - e.g. Endemic, Near-endemic, Endemic? under a group titled Endemites.
Grouping endemic statuses
Two columns are used in this example: redlist with IUCN categories, and asianDistribution with country names. We group Endemic-like statuses under one group, leaving the Native and Introduced statuses ungrouped. For the asianDistribution column (expectedly a mapregions data type with per-country distribution data), we group countries under broader geographic subregions to suit users interested in selecting all countries of a given geographic subregion at once in the filter. Individual countries can still be selected too.
| Column name | Group title | Values ordered |
|---|---|---|
status | Endemites | Endemic |
status | Endemites | Near-endemic |
status | Endemites | Endemic? |
status | Native | |
status | Introduced | |
asianDistribution | South-east Asia | Myanmar |
asianDistribution | South-east Asia | Laos |
asianDistribution | East Asia | South Korea |
asianDistribution | East Asia | China |
asianDistribution | East Asia | Taiwan |
Column Values ordered
member of table Search category custom order on sheet nl_appearance
One filter value per row, in the desired display order. The value must match a value that actually appears in the filter (after any possible Category display label replacement, so that order is preserved per-language).
Accepted content: Duplicate values within the same Column name group are not allowed.
How to use: List all values you want to control the position of. Values not listed will be appended alphabetically after the explicitly ordered ones.
Table Supported languages
on sheet nl_appearance
Declares all languages the project is available in. The first row is the default language. Any column with no language suffix (:code) is treated as belonging to this default language. If no specific language is defined for a column, then this column is used verbatim in all language variants.
If your project is monolingual, you can omit this table entirely. When more than one language is defined, users see a language switcher in the Side Menu.
TIP
The active language is reflected in the URL via the ?l= query parameter, so a specific language version can be linked or bookmarked directly.
- Columns:
- Code |
- Name of language |
- Fallback language
Column Code
member of table Supported languages on sheet nl_appearance
The language code in lowercase (e.g. en, fr, de) you will append to multilingual columns. The first row's code is the default language.
pattern (regex)^[a-z]+$ - only one or more lowercase letters a-zAccepted content: Any letters combination is fine, for existing languages codes, see ISO 639-1 language code list.
How to use: Prefer the standard two-letter ISO 639-1 codes. Place the default language in the first row. For languages without a NaturaList UI translation, set the Fallback language column to a language that does have one.
Bilingual English/Czech project
| Code | Name of language | Fallback language |
|---|---|---|
en | English | |
cs | Česky | en |
In your data sheet and the nl_content and nl_appearance configuration sheets any colum that accepts multilingual content can be then suffixed with :en or :cs to indicate the language of that column's content. Any column without a language suffix is used in all language variants.
| species | description:en | description:cs | redlistCode | comment |
|---|---|---|---|---|
Turdus merula | Plumage entirely black with a bright yellow eye-ring and bill. | Černé opeření, jasně žlutý oční kroužek a zobák. | LC | Users who selected the English version will see the English description and users who selected the Czech version will see the Czech description. Both will see the same Red List code and species name, as those columns have no language suffix. |
Column Name of language
member of table Supported languages on sheet nl_appearance
The language's name as displayed in the app's language switcher. Use the name as written in that language (e.g. Français not French, Česky not Czech).
Column Fallback language
member of table Supported languages on sheet nl_appearance
If your language code has no matching NaturaList UI translation (e.g. iu for Inuktitut), specify here the code of a language to use for the UI instead (e.g. fr). If left empty, English is used as the UI fallback.
How to use: Set only when using a language code for which NaturaList has no UI translation and you prefer a specific fallback other than English.
UI translations welcome
NaturaList UI currently supports English (en) and French (fr). If you would like to see your language supported, get in touch via NaturaList GitHub page.