You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some clarification about the format of strings used by localization files stored in vdhlocales repository would be very appreciated.
When checking the current versions of en_US.toml and co.toml files, we can see the presence of two different string delimiters: three simple quotes (''') or double quote (").
Whereas Corsican localization, in co.toml file, contains:
GB = "$1 Go"
action_bulkdownloadconvert_title = "Scaricà è cunvertisce da gruppu"
v9_coapp_required = "Appiecazione cumpagnu richiesta"
We can note that the same variable may have different delimiters, depending on the .toml file.
When updating co.toml file, do I need to respect the existing string delimiters or may I use always the same, for example double quote (") on ALL the strings?
Please can you clarify?
I also opened issue #896 but I don't know if it was the right place to raise this question. If not, I will close it.
Best regards,
Patriccollu.
The text was updated successfully, but these errors were encountered:
Hello,
Some clarification about the format of strings used by localization files stored in vdhlocales repository would be very appreciated.
When checking the current versions of
en_US.toml
andco.toml
files, we can see the presence of two different string delimiters: three simple quotes (''') or double quote (").For example
en_US.toml
contains strings such as:Whereas Corsican localization, in
co.toml
file, contains:We can note that the same variable may have different delimiters, depending on the
.toml
file.When updating
co.toml
file, do I need to respect the existing string delimiters or may I use always the same, for example double quote (") on ALL the strings?Please can you clarify?
I also opened issue #896 but I don't know if it was the right place to raise this question. If not, I will close it.
Best regards,
Patriccollu.
The text was updated successfully, but these errors were encountered: