Weblate, where we stand currently

l10n
#21

Username: thangamani-arun
Email: thangam.arunx@gmail.com

வெள்., 22 நவ., 2019, PM 4:49க்கு, sophi <sophi@libreoffice.org> எழுதியது:

#22

Yes, I'm getting the same messages:

" Please fix errors in the form.
Error in parameter method: This field is required. "

I downloaded cu/messages and translated it in Poedit. Poedit is complaining about:

format specification in 'msgid' and 'msgstr' for argument 1 are not the same

#. pA7RB
#: cui/inc/tipoftheday.hrc:208
#, c-format
msgctxt "RID_CUI_TIPOFTHEDAY"
msgid "When you're creating a Style based on another, you can enter a percentage value or a point value (e.g. 110% or -2pt or +5pt)."
msgstr "Wrth greu Arddull yn seiliedig ar un arall, gallwch nodi gwerth canrannol neu werth pwynt (e.e. 110% neu -2pt neu +5pt)."

I'm not clear what error is here. Any ideas? I'm not sure it's creating the above error, though.

Ar 21/11/2019 07:33, ysgrifennodd Sveinn í Felli:

#23

I tried uploading sfx2/messages I'd downloaded from Weblate, no Pootle error message, but got the same response from Weblate:

" Please fix errors in the form.
Error in parameter method: This field is required. "

Ar 22/11/2019 11:22, ysgrifennodd Rhoslyn Prys:

#24

What was good about Pootle was that Dwayne and his team were very focused on ease of use for translators. That was his priority, to encourage translators to get involved in providing translations, especially in minority languages for major software programs. He gave me a lot of encouragement and helped me to transfer to Pootle from the awful setup Mozilla had at the time.

It's a big loss not to have Pootle being developed and a bigger loss that the ideas have been lost - anyone seen an easy translatiors guide to Weblate - https://docs.weblate.org/en/latest/ ?  It's all admin stuff.

Ar 21/11/2019 19:56, ysgrifennodd Valter Mura:

#25

I believe that investing in Pootle today is a waste of money, Weblate
already has a great amount of features and advantages, if you believe it's
a cosmetic change it would be better to develop a customized UI rather than
investing in a project which falls behind most of the recent innovation and
standards available to translators.

#26

Hi Sveinn, *,

I have been trying to upload files through the Weblate instance, but
every time the same error message appears:

" Please fix errors in the form.
Error in parameter method: This field is required. "

As I didn't have any problem updloading a file with the change you described:
https://vm137.documentfoundation.org/translate/libo_ui-master/cuimessages/is/?checksum=54e51525910b6a67
I assume you just didn't pick one of the file-upload modes. You need
to tell weblate how to treat the uploaded strings.
Whether they should be made as suggestions or flagged as fuzzy or
flagged as need review or just committed as-is.

You can then further limit to what strings in the uploaded file that
setting should apply to. You can tell weblate to ignore strings that
are flagged as fuzzy in the po file, and you can also tell weblate to
not overwerite strings that have been translated in weblate already.

Has anyone been able to upload a file to our Weblate?

Yes - and just tried with the component/file you had problems with. So
please double-check whether you did pick a file upload mode.

I guess the bug in weblate is that it doesn't tell what field is
required, just that "This" field is required and hoping that you know
which field is meant :wink:

ciao
Christian

#27

Þann 25.11.2019 10:53, skrifaði Christian Lohmaier:

Hi Sveinn, *,

I have been trying to upload files through the Weblate instance, but
every time the same error message appears:

" Please fix errors in the form.
Error in parameter method: This field is required. "

As I didn't have any problem updloading a file with the change you described:
https://vm137.documentfoundation.org/translate/libo_ui-master/cuimessages/is/?checksum=54e51525910b6a67
I assume you just didn't pick one of the file-upload modes. You need
to tell weblate how to treat the uploaded strings.
Whether they should be made as suggestions or flagged as fuzzy or
flagged as need review or just committed as-is.

You can then further limit to what strings in the uploaded file that
setting should apply to. You can tell weblate to ignore strings that
are flagged as fuzzy in the po file, and you can also tell weblate to
not overwerite strings that have been translated in weblate already.

Has anyone been able to upload a file to our Weblate?

Yes - and just tried with the component/file you had problems with. So
please double-check whether you did pick a file upload mode.

I guess the bug in weblate is that it doesn't tell what field is
required, just that "This" field is required and hoping that you know
which field is meant :wink:

Oh, my bad ;-(

You're right, one *must* check one of the options:

  (x) Add as translation needing review
  () Add as suggestion
  () Add as translation needing edit

I guess that in older versions of Weblate, the first option would have been preselected - perhaps it's even related to which browser one uses?

Anyway, problem solved - thanks a lot!

Sveinn

#28

Hi Rhoslyn, *,

Yes, I'm getting the same messages:

" Please fix errors in the form.
Error in parameter method: This field is required. "

So I guess same cause here - not picking one of the upload modes.

I downloaded cu/messages and translated it in Poedit. Poedit is
complaining about:

format specification in 'msgid' and 'msgstr' for argument 1 are not the same

#. pA7RB
#: cui/inc/tipoftheday.hrc:208
#, c-format
msgctxt "RID_CUI_TIPOFTHEDAY"
msgid "When you're creating a Style based on another, you can enter a
percentage value or a point value (e.g. 110% or -2pt or +5pt)."
msgstr "Wrth greu Arddull yn seiliedig ar un arall, gallwch nodi gwerth
canrannol neu werth pwynt (e.e. 110% neu -2pt neu +5pt)."

it thinks the string is some placeholder string, so false positive.
it has c-format label, and there placeholders have the form
%[parameter][flags][width][.precision][length]type

A space would be a valid flag (add space for positive number, but a
"-" for negative values) - so "% o" from source string and "% n" are
different, hence it complains/warns.
But that's not the cause of the error

I'm not clear what error is here.

the c-format label on the string is misleading/wrong technically. If
it were used as a c-format/placeholder string, the percent signs would
have to be escaped:
… 110%% or -2pt…
but the string is not used as a placeholder string, so the c-format is
added errornously by xgettext - the strings from hrc files are
extracted using this command:
xgettext -C --add-comments --keyword=NC_:1c,2 --keyword=NNC_:1c,2,3
--from-code=UTF-8 --no-wrap cui/inc/tipoftheday.hrc -o
/tmp/messages.po

But seems the strings in the file don't use c-string style placeholder
definitions for all strings, but a mix of $1 ... $2 style and also %1
or $(ARG1) $(ARG2)...
only 16 strings seems to be using c-style format like this:
NC_("SV_STDTEXT_SERVICENOTAVAILABLE", "The component (%s) could not be
loaded.\nPlease start setup with the repair option.")
But even then it is not real c-format string, but later replaced by a
find and replace (so the placeholder can be anything)

All others use a freestyle-way of placholder %SOMELABEL, the $1 style,
the %1 style or $(ARG1) style...
So "fix" for the bogus warning is to change the xgettext invocation to
not assume C++ format strings/strip the c-format label from the
result.

Any ideas? I'm not sure it's creating
the above error, though.

The warning is unrelated.
Make sure to pick a file-upload-mode and uploading should work.

ciao

Christian

#29

Hi,

Þann 25.11.2019 10:53, skrifaði Christian Lohmaier:

Hi Sveinn, *,

I have been trying to upload files through the Weblate instance, but
every time the same error message appears:

" Please fix errors in the form.
Error in parameter method: This field is required. "

As I didn't have any problem updloading a file with the change you
described:
https://vm137.documentfoundation.org/translate/libo_ui-master/cuimessages/is/?checksum=54e51525910b6a67

I assume you just didn't pick one of the file-upload modes. You need
to tell weblate how to treat the uploaded strings.
Whether they should be made as suggestions or flagged as fuzzy or
flagged as need review or just committed as-is.

You can then further limit to what strings in the uploaded file that
setting should apply to. You can tell weblate to ignore strings that
are flagged as fuzzy in the po file, and you can also tell weblate to
not overwerite strings that have been translated in weblate already.

Has anyone been able to upload a file to our Weblate?

Yes - and just tried with the component/file you had problems with. So
please double-check whether you did pick a file upload mode.

I guess the bug in weblate is that it doesn't tell what field is
required, just that "This" field is required and hoping that you know
which field is meant :wink:

Oh, my bad ;-(

You're right, one *must* check one of the options:

(x) Add as translation needing review
    () Add as suggestion
    () Add as translation needing edit

I guess that in older versions of Weblate, the first option would have
been preselected - perhaps it's even related to which browser one uses?

great, I didn't thought about that, I was scanning the file.

Anyway, problem solved - thanks a lot!

yes, thanks Cloph for looking at it. I'll collect those things and will
do a FAQ on our wiki, so newcomers will have some hints.

Cheers
Sophie

#30

Thanks Christian,

None of those choices made much sense to me. I was looking for a Import translation (I'm happy with it, and don't want to do anything else with it...) choice.

After a lot of trial and error I found that it's best to choose 'Add as translation needing review', although it didn't need a review.

Using 'Overwrite existing translations...' took a long time, up to 6 minutes.

All looks OK now. Thanks.

Rhos

Ar 25/11/2019 10:53, ysgrifennodd Christian Lohmaier:

#31

Hi Rhoslyn;

The option 'Add as translation needing review' may not be of obvious use unless you are aware of that Weblate is used by a respectable bunch of different projects - and that some of them (very few actually, but I know about a couple of projects) do insist on reviewing each and every string - and worse: the whole language is not available unless all strings are translated and reviewed before deadline...

This is of course absurd for many one-man-show language teams, and IMHO should be up to each language team to decide whether to use it or not.

So, that feature may not concern us, but in some cases it does.

Best regards,
Sveinn í Felli

Þann 25.11.2019 14:06, skrifaði Rhoslyn Prys:

#32

Yes, I guessed that, you would have thought that that could have been dealt with via individual profiles, as other on-line translation machines do.

Thanks, Sveinn :slight_smile:

Ar 25/11/2019 15:00, ysgrifennodd Sveinn í Felli:

#33

Thanks Christian for the explanation. Weblate accepted the translation file back without the 'fix' being made.

Ar 25/11/2019 12:09, ysgrifennodd Christian Lohmaier:

#34

FYI: created https://gerrit.libreoffice.org/#/c/83784/ to remove the
wrong c-format label for one of the future template updates.

ciao
Christian

#35

I found some differences in the search options of Pootle and Weblate.
- When searching in Pootle you can select "Phrase match" and Case-sensetive match. In Weblate I don't see that.
- The results in Pootle are in a list and the amount of found items is mentioned. In Weblate only one instance is shown and you have to search again for the next.

Kind regards, Kees

sophi schreef op 19.11.2019 17:14:

#36

Hi Kees,

I found some differences in the search options of Pootle and Weblate.
- When searching in Pootle you can select "Phrase match" and
Case-sensetive match. In Weblate I don't see that.

The naming is not the same, but in the Search type drop down list, you
find Fulltext, Substring, Exact match and regular expression.

- The results in Pootle are in a list and the amount of found items is
mentioned. In Weblate only one instance is shown and you have to search
again for the next.

I get a list, for example searching for Open, I get 7 occurrences, which
indeed it not complete, but it's a list. Could you send me a sample of
your search so I can reproduce it and see what's going on?

After several tests, I finally was able to retrieve your request for
UJ5WP in the example you sent me. You need to add Exact match in the
Search type and check Comment strings, and you get the result quite
quickly. I'll add it to the FAQ too.

Looking at the documentation, it seems the search query has changed in
the next version, see:
https://docs.weblate.org/en/latest/user/search.html
hope that will help us to fine tune string search

Cheers
Sophie

#37

sophi schreef op 28.11.2019 11:34:

Hi Kees,

I found some differences in the search options of Pootle and Weblate.
- When searching in Pootle you can select "Phrase match" and
Case-sensetive match. In Weblate I don't see that.

The naming is not the same, but in the Search type drop down list, you
find Fulltext, Substring, Exact match and regular expression.

Ah yes, I found it. Thanks for the tip.

- The results in Pootle are in a list and the amount of found items is
mentioned. In Weblate only one instance is shown and you have to search
again for the next.

I get a list, for example searching for Open, I get 7 occurrences, which
indeed it not complete, but it's a list. Could you send me a sample of
your search so I can reproduce it and see what's going on?

As I search for "Openen" (Open in Dutch) I get a list indeed. Again thanks for the help.
I think it depends on what you are searching for.

After several tests, I finally was able to retrieve your request for
UJ5WP in the example you sent me. You need to add Exact match in the
Search type and check Comment strings, and you get the result quite
quickly. I'll add it to the FAQ too.

That is it. Great now it works. Thanks a lot for your help.

Looking at the documentation, it seems the search query has changed in
the next version, see:
https://docs.weblate.org/en/latest/user/search.html
hope that will help us to fine tune string search

I hope so too.

Again. Thanks a lot Sophie.
Kees

#38

Sorry for jumping in so late but it's the same subject:

Are we planning any fundemental changes to this wiki page before I'm going
on with translating it?
https://wiki.documentfoundation.org/Translating_LibreOffice

Thanks!
Yaron Shahrabani

<DevOps - Hebrew translator>

#39

Yes, Sophie will update it. I would not touch the translations yet.

Ilmari