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:
Hi everyone;
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. "
Has anyone been able to upload a file to our Weblate?
Best,
Sveinn í Felli
To Christian et al.:
I even made a test; downloaded one file
<https://weblate.documentfoundation.org/projects/libo_ui-master/cuimessages/is/>
from which I had beforehand corrected all errors and therefore had
already been handled by Weblate.
This file I opened in a text editor and filled in one missing
translation:
#. NG4jW
#: cui/inc/tipoftheday.hrc:258
msgctxt "STR_MORE_LINK"
msgid "More info"
msgstr "Nánari upplýsingar"
Saved the file and tried to upload, but the same error appeared again.
Verified the file with:
$ msgfmt -vc 3libo_ui-master-cuimessages-is.po -o
3libo_ui-master-cuimessages-is.mo
3libo_ui-master-cuimessages-is.po:2: warning: header field
'PO-Revision-Date' still has the initial default value
3libo_ui-master-cuimessages-is.po:2: warning: header field
'Last-Translator' still has the initial default value
2270 translated messages, 326 untranslated messages.
Took a look at the header; nothing unusual although both
"PO-Revision-Date" and "Last-Translator" fields are untouched
(original default values). The field "Language-Team" had some
Weblate-gibberish extending over a couple of lines, so I tried to put
in some reasonable values:
"PO-Revision-Date: 2019-11-21 06:41+0000\n"
"Last-Translator: Sveinn í Felli <sv1@fellsnet.is>\n"
"Language-Team: Icelandic <translation-team-is@lists.sourceforge.net>\n"
Verified the file with:
$ msgfmt -vc libo_ui-master-cuimessages-is.po -o
libo_ui-master-cuimessages-is.mo
2270 translated messages, 326 untranslated messages.
Uploaded this file but all the same; Weblate refuses to cooperate.
I think I have already mentioned this problem on this ML because it's
not just this Weblate-instance which has these symptoms; uploading
worked w/o hickups until (if I remember correctly) Weblate 3.7 came
into production. I'm also working on several other projects on various
different Weblate-instances; some are affected by this and others are
not. I'm not able to see any pattern or common attributes for the
projects that fail.
--
Rhoslyn Prys
Meddal.com
07815067805 / 01248 351289
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
- Re: [libreoffice-l10n] Weblate, where we stand currently (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.