Latest Comments

112 Total
a comment on the token [alt] just doing research, I swear in the domain DontTrack.us for the language Portuguese of Brazil 3 years and 7 months ago
A frase deve começar com maiúscula, mas não deve ter uma segunda letra maiúscula no meio, como a outra sugestão.
a comment on the General Rambling "Next unvoted" should not show tokens in which we propose translations 3 years and 8 months ago
Right now, there are no untranslated tokens for "donttrack.us", in PT-BR.

In the page https://duck.co/translate/duckduckgo-don... I have the button "Vote on translated tokens". But it does not work in a useful way.

In the first time I click it, the page https://duck.co/translate/tokenlanguage/... is shown; but I did a suggestion in the translation of this item a long time ago, which implies that I cannot vote myself, but also I don't want to vote the other suggestions that are given there. This page should not be showed with these steps, right?

Then I continue. Click the arrow pointed ( :) I like the wizard and its funny hints) "go to next token". The page https://duck.co/translate/tokenlanguage/... is shown, but I also have made a suggestion for this token. Only the third page will have something new to me, right now - but it has a problem I probably will ask here in another thread, one of these days.

Am I doing some "unusual" step here? Or is there a little issue with these pages?
a comment on the token [size] All Sizes in the domain DuckDuckGo.com for the language English in United Kingdom 3 years and 8 months ago
Note that "All sizes" and "All Sizes" has a different S. The proper one should maintain the capital S.
a reply to a comment on the General Rambling Wrong translation in use 3 years and 8 months ago
"Makes sense"... no, not really. It probably was written with a misunderstanding caused by similar English words or sentences (same verb but different conjugations, opposing ideas).

The translation I want to remove means "to show results for [...]", with words that have the idea of a future action/consequence/fact very strong, and are commonly understood like that. And I think this is not what it should mean.

The translation I propose there means "Showing [or viewing] results for [...]", with the idea of things that are already done, that we can see now, that are present. And this is more appropriate, I think. You can even confirm for us this token is used with these context ideas.

I agree with you that someone should vote for it, eventually. But until then it allows, sometimes, that wrong translation may be used. So a down vote (similar to what we see in StackOverflow websites) could be considered to exist.
a comment on the token Viewing results for %s. in the domain DuckDuckGo.com for the language Portuguese of Brazil 3 years and 8 months ago
"Ver resultados para" está muito errado! Cuidado pra não confundir o tempo verbal da ideia, que às vezes não é tão óbvio. No caso, o melhor deve ser mesmo como o que vemos em vários lugares similares: "Mostrando resultados para". Os resultados já estão lá, sendo mostrados.
a comment on the General Rambling Wrong translation in use 3 years and 8 months ago
The token https://duck.co/translate/tokenlanguage/... has a wrong translation currently in use. It has not vote yet; won't have mine because I think it is wrong; but my (assume) correct translation put there cannot be used until people vote for it more than the (assume) wrong one.

I ask two things:

1. remove this wrong translation suggestion from there; or at least hide it.

There may be arguments to leave all suggestions there: they should get less votes; better translation should be made. But why filling our screen with options that sometimes are too silly? And this goes to my second wish, that is not new.

2. to have a way to down vote translation suggestions, instead of just "liking" it. Having two translation, one with "-1" and other with "0" could fix the situation, until more people go there. For website users this is an improvement since they won't see weird things, although temporary - which is important, in the long term.

I explained why the other suggestion should be wrong in the token page. Translators that go there may read it (hopefully they always read comments before voting/translating, but some comments should have the same value as token notes).
a reply to a comment on the General Rambling Translation token information and context are needed 3 years and 8 months ago
Thank you both, very much. The note there now is crystal clear. :)

I'll make posts about contexts that I find useful to have. But, just a humble suggestion, I think they should exist for all tokens: context, examples, link to help about order¹ of placeholders, when present.

¹ It is the same syntax that C printf (and sister functions in any language) uses, but I guess most translators are not familiar with them, may not remember it so easily, so a "one click that's it" page can be valuable. The page linked about placeholders is there. But a I'm talking about a simpler page or section just about the order; two examples and the syntax, direct link to this. I have read that page but missed the order part (because most of it were things I already knew, probably skimmed through a few ones, like this).
a comment on the token Viewing results from the %s. in the domain DuckDuckGo.com for the language Portuguese of Brazil 3 years and 8 months ago
É necessário confirmar que o %s *não pode* ser substitutído por palavras femininas e/ou no plural. Isso tornará a tradução proposta errada.

Porém, caso isso não seja necessário, *não se deve* usar algo mais geral como "o(a)(os)(as)" na posição do artigo. Ficará feio, com cara de coisa mal feita.
a comment on the General Rambling Translation token information and context are needed 3 years and 8 months ago
In this token to translate:

Viewing results from the %s for %s

There are two placeholder that I cannot imagine what should or could be their contents. Is it possible to include information, possibly an clear and direct example of where this string is used? I imagine the information being added to all language translation interfaces, but if this is not possible, I ask for PT_BR and Brit. Eng. (the two languages I contribute to).

This is not the first time I see this kind of case. There are languages that will need a very different order of words/ideas in the sentence to have the same meaning of the full English sentence. The consequence of this is that the placeholder content must have a way to be exchanged. Is there? And, so translator are aware of such cases, a broader token/sentence context and data must be added to the interface.

I think that depend on translators to discuss/ask this about the tokens they feel it is needed is error prone, and will not detect errors, sometimes in important tokens.
a comment on the token [frontpage] The search engine that doesn't track you. %sLearn More%s in the domain DuckDuckGo.com for the language Portuguese of Brazil 3 years and 8 months ago
O termo técnico usado para "search engine" em português é BUSCADOR. E mais nada. "Ferramenta de busca" é apenas uma tradução literal das palavras em inglês, e portanto deve ser menos usada do que o termo técnico em uso frequente, onde não permanece o jargão original, em inglês (mesmo em documentos/textos em português).
« 1 ... 3 4 5 6 7 8 9 10 11 12 »