Weblate: new hardware

l10n
#1

Hi,

We have now switched to a dedicated machine to run our Weblate instance.
Thanks a lot to Guilhem and Christian for their work on that!

If you see "TDF Weblate STAGING - LibreOffice" then, you are on the old
instance where translations are blocked. If you see "TDF Weblate -
LibreOffice" then you are on the new instance, DNS has been updated

As soon as everything is checked on the new machine, we will be able to
upgrade to a newer version. Don't hesitate to send your feedback to the
list.

Cheers
Sophie

#2

sophi <sophi@libreoffice.org> 於 2019年12月9日 週一 下午7:05寫道：

Hi,

We have now switched to a dedicated machine to run our Weblate instance.
Thanks a lot to Guilhem and Christian for their work on that!

If you see "TDF Weblate STAGING - LibreOffice" then, you are on the old
instance where translations are blocked. If you see "TDF Weblate -
LibreOffice" then you are on the new instance, DNS has been updated

As soon as everything is checked on the new machine, we will be able to
upgrade to a newer version. Don't hesitate to send your feedback to the
list.

Are the migration from Pootle to Weblate finished?
Should we work on Weblate instance or Pootle now? Or both are fine?

Thanks.

#3

Hi Cheng-Chia,

sophi <sophi@libreoffice.org> 於 2019年12月9日 週一 下午7:05寫道：

Hi,

We have now switched to a dedicated machine to run our Weblate instance.
Thanks a lot to Guilhem and Christian for their work on that!

If you see "TDF Weblate STAGING - LibreOffice" then, you are on the old
instance where translations are blocked. If you see "TDF Weblate -
LibreOffice" then you are on the new instance, DNS has been updated

As soon as everything is checked on the new machine, we will be able to
upgrade to a newer version. Don't hesitate to send your feedback to the
list.

Are the migration from Pootle to Weblate finished?
Should we work on Weblate instance or Pootle now? Or both are fine?

For now, only master is on Weblate, 6.3 and other projects are in Pootle.
Cheers
Sophie

#4

Hi

I see that searching is changed.
I can no more choose for "Exact match"
And I can no more choose my language, so the result are in all languages.
Maybe I do something wrong?

Kind tegards,
Kees

sophi schreef op 09.12.2019 12:04:

#5

Hi Kees,

Hi

I see that searching is changed.
I can no more choose for "Exact match"
And I can no more choose my language, so the result are in all languages.
Maybe I do something wrong?

So Christian has upgraded to version 3.9.1 and the search has changed.
To search the keyID UJ5WP for example, I did:
- Choose UI project,
- Select Dutch
- Click on the Search button
- Enter comment:UJ5WP in the Query field
- Click on Search button
--> I get the result in your language.

If you go to the Advanced query builder, you have examples of the
syntax. For example in the drop down list, instead of Source string
select Comment Strings and in Search for, enter UJ5WP and then click on
ADD. You'll see that in the Query field you have now comment:UJ5WP

Cheers
Sophie

#6

Thanks Sophi

I will try to follow your ionstructions, but I must say that it doesn't make it easier for me.

Greetings, Kees

sophi schreef op 11.12.2019 10:39:

#7

Hi Sophi

One more question.
Why do I have to choose my lanquage after choosing search.
Can't it use my lanquage as a default?

Regards, Kees

sophi schreef op 11.12.2019 10:39: