Re: AOo 4.5.0 builds

[Delio Orozco Gonzalez]

Hello Matias: 

I donwloaded from  https://ci.apache.org/projects/openoffice/install/linux64/, 
the vertion for spanish with the link: 
Apache_OpenOffice_4.5.0_Linux_x86-64_install-deb_es_2021-05-11_04:13:41_b82be50fa0f1a4e9f27bc8d6c5da1904c31a998f.tar.gz
  

And I can't install because when I unpack the file I get a error messages with 
the compacted archive. I work with Debian 9.

Regards, Delio.

- Mensaje original -
De: "Matthias Seidel" 
Para: "dev" 
Enviados: Domingo, 30 de Mayo 2021 16:42:13
Asunto: Re: AOo 4.5.0 builds

Hi Rory,

Am 30.05.21 um 22:34 schrieb Rory O'Farrell:
> On Sun, 30 May 2021 22:14:13 +0200
> Matthias Seidel  wrote:
>
>> Hi Rory,
>>
>> This is for Linux only (450 and 42X), Windows builds are fine.
> Having moved away from Windows some 12/13 years ago, I now live a very happy 
> life!

I am on Linux for 8 years now, but 80% of our users are on Windows.

So Windows is my main concern.

>
> Thanks for the help.

You're welcome!

Matthias

>
>> I have informed Infra
>>
>> Regards,
>>
>>    Matthias
>>
>> Am 30.05.21 um 22:11 schrieb Rory O'Farrell:
>>> The automatic builds of 4.5.0, which used be updated every day or two, seem 
>>> to have ceased.  The builds at
>>>
>>> https://ci.apache.org/projects/openoffice/install/linux64/
>>>
>>> have not been updated since 11th May.
>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

[GitHub] [openoffice] cbmarcum opened a new pull request #131: Refs #i128455# - updated junit to 4.13.2.

[GitBox]

cbmarcum opened a new pull request #131:
URL: https://github.com/apache/openoffice/pull/131


   updated NamedRequest inner class Suite constructor to match the signature of 
the super class ParentRunner that was the only constructor until JUnit 4.13.  
Now ParentRunner has a second constructor that made passing a null arg 
ambiguous.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: OOo:eo Localization page

[Marcus]

Am 12.05.21 um 20:38 schrieb Marcus:
I would say, let's going on in the mail thread in @L10n. Otherwise it's 
just double postings. ;-)


in the meantime the webpages have been updated and are available:
https://www.openoffice.org/eo/

Please have a look what you want to translate. Then I can help you. :-)

Thanks

Marcus




Am 12.05.21 um 11:33 schrieb Dean.Webber:
I have updated the "main" page for the Esperanto (EO) language. The 
html code is available at https://justpaste.it/8yuud for upload.


The pages have mostly been translated using translate.yandex.com with 
help from en.bab.la/dictionary/english-esperanto/ for the remaining few.


This will still point to the english version of the downloads page, as 
the Esperanto version has been relocated for housekeeping purposes.


If someone could upload this, I can make sure that it looks as it 
should when sitting in the correct location.


As a final check I can translate it back to English, to ensure that 
the meaning has not changed significantly.



I was not sure how the language detection in the page operates, but I 
set the variable for language to "eo" on line 271, is that sufficient?



The original was based from the English (en-GB) version found from 
www.openoffice.org/?redirect=soft 
and clicking on "This site is also available in English (en-GB). Just 
click this text to get redirected.". The soft redirect message appears 
when changing from another language back to English.


From: Aivaras Stepukonis 
Sent: Wednesday, 12 May 2021 1:23 AM
To: dev@openoffice.apache.org 
Subject: Re: OOo:eo Localization page

Thank for the link, Marcus!

Yes, as long as the visitors are informed they can help with
localization, keeping the website up to date by removing from sight the
bits that are unmaintained is an appropriate QA step.

Aivaras

2021-05-11 14:01, Marcus rašė:

Am 11.05.21 um 11:35 schrieb Aivaras Stepukonis:

On the subject of unmaintained, untranslated local webpages.

One should start with a simple set of criteria that allows to
determine what is/is not unmaintained. Something like:

1. incomplete page translation;
2. outdated page layout/design.


the criteria are summarized here:
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.openoffice.org%2Fprojects%2Fnative-lang.htmldata=04%7C01%7C2018001901%40student.sit.ac.nz%7C6379c6930f444b8bf8c008d9148007f2%7Cc46ab213d1794a719ff7b9d9fe3f3b48%7C0%7C1%7C637563362414144036%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=DEnEpvYDuzBAw0qhtWplPWqHwMSd8p56Btwk6S0bDXI%3Dreserved=0 




Then one would archive the pages that fall under the above criteria.
The visitors coming from the locales of the unlocalized pages would
instead be directed to the main page with a message "If you can help
translating this page into your native language, let us know!"


This is already done in a slightly different way:
- Pages have English text
- A big, red box with text similar to yours but just a bit more.
- No redirection to the main page

Marcus




2021-05-11 02:07, Marcus rašė:

Am 11.05.21 um 00:18 schrieb Dean.Webber:

How many localization pages need to be translated? How many pages
are 'not maintained'?


the default set has ~40 pages. But I haven't counted the total
amount of words or sentences.


Depending on the extend of the pages, we can adopt a translate
service (which will have some cost attached). For example to
translate 100 pages of similar character length using the yandex
translate api will cost $5.00/month (assuming USD).


Hm, costs are always not a good argument. OpenOffice is made by
volunteers. The same should apply to the creation and maintenance of
webpages or documentation in general.

I don't know the quality of translated languages of Yandex or
others. But I know Google Translate and its quality is ...
improvable. ;-)


Otherwise perhaps a list of these pages can be left for those that
are new recruits, or looking for something to do. So, if they chose
too, they can spend some time working on localizations or
translations. They can then use a translate service (for free) to
convert from the sources to the localization language.

This may result in poor quality translation, but enough for people
to get the general idea, and a good starting point for native
language speakers to modify pages.


As written previously the pages are unmaintained for years. There
are no volunteers that would take care of it. So, translating a part
of it and then others can do the remaining stuff will not come true.

Very seldom we get a mail that someone has seen a message like you
can see here in the red box [1]. We give them a few hints and how
and where to start with translation and then ... noting more. Thats
all.


But honestly, I have no idea of the scale of the localization pages.


The problem is that there is nobody who can take care of these
pages. 

[GitHub] [openoffice] cbmarcum merged pull request #130: Refs #128452 - JUnit and Hamcrest update for test automation

[GitBox]

cbmarcum merged pull request #130:
URL: https://github.com/apache/openoffice/pull/130


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org