Pootle upgrade

l10n
#1

Hi,

This week we upgrade our Pootle server, translations.documentfoundation.org.
With help of Pootle developers, the newest version of Pootle will be
deployed. During upgrade we may shut down the service, so please do not be
surprised.

LibreOffice 3.5 files were backed up and removed from the interface,
because there will be no more releases of LibreOffice 3.5.x. Outdated
extension translations were backed up and removed, too. Migration takes a
lot of time, it will take less, when we don't migrate obsoleted projects.

After successful upgrade, I will import LibreOffice 4.0 files, so you can
start to prepare for the next major release. Before that I would like to
minimize the amount of changed strings and migrate translations in a smart
way. For example many cosmetic fixes have been made to en-US help files,
and UI is moving from .src format to new XML based .ui format, while the
strings remained the same.

Best regards,
Andras

#2

4.0? What about 3.x versions?

Regards

#3

It seems you missed the announcement, instead of 3.7 the next release will
be 4.0.
See e.g.:
http://nabble.documentfoundation.org/ANNOUNCE-Policy-change-regarding-API-and-ABI-stability-td4016550.html

Andras

#4

Hi Andras,

Hi,

This week we upgrade our Pootle server, translations.documentfoundation.org.
With help of Pootle developers, the newest version of Pootle will be
deployed. During upgrade we may shut down the service, so please do not be
surprised.

LibreOffice 3.5 files were backed up and removed from the interface,
because there will be no more releases of LibreOffice 3.5.x. Outdated
extension translations were backed up and removed, too. Migration takes a
lot of time, it will take less, when we don't migrate obsoleted projects.

After successful upgrade, I will import LibreOffice 4.0 files, so you can
start to prepare for the next major release. Before that I would like to
minimize the amount of changed strings and migrate translations in a smart
way. For example many cosmetic fixes have been made to en-US help files,
and UI is moving from .src format to new XML based .ui format, while the
strings remained the same.

Thanks a lot to you and Pootle devs for the work you're doing on this.

Could you give us a link where we can find more information about the
transformation from src to xml file format?
Also I've seen messages on the dev list that the wiki help will become
the primary help in the future, could you give us more information on
this or where we can find it, I would like to understand the process :slight_smile:
Thanks in advance
Kind regards
Sophie

#5

Hi Sophie,

Could you give us a link where we can find more information about the
transformation from src to xml file format?

If you are interested in details, it is documented in the wiki:
http://wiki.documentfoundation.org/Development/WidgetLayout
However, this change will be transparent to translators. I remember when
module cui was cut out of module svx back in OOo times, and suddenly all
translators had a lot of untranslated dialogs, which were translated
before. It would be better to avoid this situation, and migrate
translations centrally. I have not tried to do that, but I will find out
something.

Also I've seen messages on the dev list that the wiki help will become
the primary help in the future, could you give us more information on
this or where we can find it, I would like to understand the process :slight_smile:
Thanks in advance

... in the future, yes, that may never come, so I cannot tell anything else
about this. It is still in planning phase. I will oppose any change that
does not provide a smooth migration path to save our years of work that we
have put into help translations. Ideally this process will be transparent
to translators as well. I like the general concept of web based help, and I
will help to make it happen. I'll inform this mailing list, when I know
more.

Best regards,
Andras

#6

Hi Andras,

Hi Sophie,

Could you give us a link where we can find more information about the
transformation from src to xml file format?

If you are interested in details, it is documented in the wiki:
http://wiki.documentfoundation.org/Development/WidgetLayout
However, this change will be transparent to translators. I remember when
module cui was cut out of module svx back in OOo times, and suddenly all
translators had a lot of untranslated dialogs, which were translated
before. It would be better to avoid this situation, and migrate
translations centrally. I have not tried to do that, but I will find out
something.

Thanks a lot for your work on this. I'm confident that you'll find the
best for us. I'm also a curious girl who like to understand what's going
behind :wink:

Also I've seen messages on the dev list that the wiki help will become
the primary help in the future, could you give us more information on
this or where we can find it, I would like to understand the process :slight_smile:
Thanks in advance

... in the future, yes, that may never come, so I cannot tell anything else
about this. It is still in planning phase. I will oppose any change that
does not provide a smooth migration path to save our years of work that we
have put into help translations. Ideally this process will be transparent
to translators as well. I like the general concept of web based help, and I
will help to make it happen. I'll inform this mailing list, when I know
more.

Thanks. I'm not against a web based help too as long as we make the help
files available with the product. Most users (even in France) are not
allowed to access internet at their working place or have no access at
all. So again, I'm not against it, I just want both possibilities :slight_smile:

Kind regards
Sophie

#7

Unlike the current format, the glade UI files can be be translated
using gettext, so do you plan to finally switch LibreOffice to
gettext, so that we can have the possibility to test translations
without having to recompile the whole univers (ie something most
translator are not capable to do)?

#8

Yes I did. I´m not subscribed on that list. Will do it right now.

Regards