Hi,

On 20.09.2013 14:26, Ricardo Berlasso wrote:
2013/9/20 Oliver-Rainer Wittmann <[email protected]
<mailto:[email protected]>>

    Hi,

    forgive me for writing in English, but this post goes to several
    native language mailing lists and to [email protected] and [email protected].

    I am currently preparing the update of the XML feeds for our product
    update notification service for former OpenOffice versions (3.2.0,
    3.2.1, 3.3.0, 3.4.0, 3.4.1, 4.0.0) in order to enable the
    notification about new version 4.0.1

    For most of the languages the user is directed by the update
    notification to our main download side [1].
    For the following languages the user is directed to the
    corresponding native languages page:
    - Chinese (simplified)
    - Chinese (traditional)
    - Dutch
    - French
    - German
    - Italian
    - Japanese
    - Slovak
    - Spanish

    IMPORTANT:
    Please drop me a short note, when the corresponding native langauge
    pages has been updated after version 4.0.1 has been released
    OR
    drop me a short note, when no update to the native language page is
    needed.

    When I have collected the replies for all the above mentioned
    languages I will enable the product update notification for version
    4.0.1

    BTW, if for your languages the user shall also be directed to a
    corresponding native languages pages, then let me know this page. I
    will include it in the update XML feeds.

    [1] www.openoffice.org/download <http://www.openoffice.org/download>


Hi, Oliver,

For the ES site, the download page is at

http://www.openoffice.org/es/descargar/

The site only need to update the header when the release is made
available, so no problem with that: it will be done as soon as the 4.0.1
announcement enters the announcement mailing list ;)


WOW that was a fast reply - Thx.

Best regards, Oliver.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Responder a