But where is “hidden fields”? In fact, I found none of the text below to translate.
Dentro de Widget, VISIBLE CAMPOS should be “Campos Visíveis” and “HIDDEN CAMPOS” should be “Campos Ocultos”.
The types of columns (in the Field/Campo) options are not translated.
Any = Qualquer
Text = Texto
Numeric = Numérico
Integer = Inteiro
Toggle = Seleção
Date = Data
DateTime = DataTempo
Choice = Escolha
ChoiceList = Multipla Escolha
Reference = Referência
Reference List = Lista de Referências
Attachment = Anexo
Formato da Célula:
Textbox should be “Caixa de texto”
As I have no clue what “Field in 2 views” does, I won´t translate it lol
It’s weird because SOME parts of the right panel are translated
For example… Column has been translated to COLUNA. However, TABLE should be TABELA, but it was not translated.
And inside Weblate I cannot find where to translate TABLE.
However, I also do not find where to translate COLUMN. So how was it translated, if it’s not available at Weblate?
There are SEVERAL already translated stuff that I just can´t find at Weblate.
edit: I downloaded the translation JSON and opened it. There are much more words and texts than I can find in Weblate. Maybe I am clueless on how to search words in Weblate to translate
There’s a lot going on in Weblate. For searches, have you noticed the |< < 1/NN > >| part at the very top, could that be where the results you expect are hiding?
I’m not a Weblate expert, I’m not sure if there’s a good way to get a list of all matches on a single page. I did see search one level up that might be helpful for some cases:
I wanted to let you know that there is a new special source string that looks like this:
Translators: please translate this only when your language is ready to be offered to users
In the future, languages for which this string has not been translated will be ignored, and not offered to users. This is to make it easier to start translations but not have the pressure of them showing up immediately to everyone before the translator is comfortable with them.
There will be an environment variable to override this behavior for self-hosters and desktop app users.
Hi, it took me long time but I help translate to polish. It was very easy with Weblate. Some words needs to be fixed because I don’t know what mean for examplefiddle in Grist case. But most was OK.
It means VIOLIN or to PLAY VIOLIN in the strict sense.
But there are other meanings. Thus, it should be seen WHERE the word FIDDLE is used in Grist. My guess is that it’s related to “manipulate or tamper with data”.
To manipulate or tamper with something: If someone fiddles with something, they are making small adjustments or changes to it, often in a way that is unnecessary or unhelpful. For example, “He kept fiddling with the TV remote, trying to get it to work.”
To waste time or avoid work: If someone is fiddling around, they are not doing anything productive and are wasting time.
To cheat or deceive: If someone is fiddling something, they are cheating or deceiving someone in order to gain an advantage. For example, “He was caught fiddling the company’s accounts.”
It actually refers to sites like those listed at https://fiddles.io/, where “X fiddle” means a page where you can fiddle with / play around with something just to try it out. Agreed it is not a very user-friendly term.
(see the little bit of gray text in the breadcrumb row?)
There are some notes about it here:
You can enter the same mode on any document by doing [Share icon] → “Work on a Copy”, except then it is called unsaved instead of fiddle (which is probably clearer).
Hi all - we’ve changed settings on weblate, now anyone can start a translation, no need for an adminstrator. Just please delay translating the special string that looks like this: "Translators: please translate this only when your language is ready to be offered to users". Please translate this later rather than sooner, so users don’t get disappointed with a very incomplete translation. Thanks!
@George_Mouawad or @Siavash, we haven’t started on RTL support, but a partial translation of at least one RTL language could be handy for testing when someone does start working on it, so if either of you have time for it that would be super helpful
I am nb_NO (Norwegian Bokmål) Allan Nordhøy @ Hosted Weblate
Seems a great deal of time was spent creating this.
I wouldn’t mind spending some time getting the stringbase in shape to better match that effort.
Would be nice if a WL admin (@paul-grist or @anais-grist) could turn on suggestions in Sign in @ Hosted Weblate , and preferably also direct editing of source strings. Could also edit the respective files in a PR.
The source strings for grist-core are extracted from code using this script:
The process could use some improvement. In particular, deleting strings that are no longer used needs someone to notice and intervene (help in a PR would definitely be appreciated here). I’d be worried that direct editing of source strings could lead to conflicts, but I’d be glad to be reassured about that.
I believe suggestions are already enabled, but maybe there’s some related setting we’re missing?
I think it might be the “read-only” flag that prevents suggestions,
which in and of itself doesn’t make a lot of sense.
Possibly having those by default is just how the platform handles “direct editing” being turned off.
As long as source strings are only changed in WL,
and any pending changes dropped at the PR stage I think there should be no conflicts.
Meant to link to the actual editing, and looked up a project I have access to since normal users can’t see the config of every project.
I’ve translated the project in Bulgarian, but now I want to improve the overall translation by using the project.
How can I can I locally, and preferably easy, add the translation keys to the labels so I can easily fix the tense, mood, aspect and use the correct translation in the correct context?
Edit: This seems to work.
diff --git a/app/client/lib/localization.ts b/app/client/lib/localization.ts
index 4780b73c..c0cef1e7 100644
--- a/app/client/lib/localization.ts
+++ b/app/client/lib/localization.ts
@@ -109,7 +109,7 @@ function domT(key: string, args: any, tImpl: typeof i18next.t) {
// If there are any DomElements in args, handle it with missingInterpolationHandler.
const domElements = !args ? [] : Object.entries(args).filter(([_, value]) => isLikeDomContents(value));
if (!args || !domElements.length) {
- return tImpl(key, args || undefined);
+ return tImpl(key, args || undefined) + ` (${key})`;
} else {
Grist translations are mostly done by users who need them. If you log in to the site for managing Grist translations, you can add a new language yourself:
Basque is ready but there are three keys that I’m not sure how to localise:
Ready Column,
Future values and
Map
I believe map/mapping/unmap could be translated as analyse, assign, show and hide, depending on context. That’s the way they will show for now at least.
