Re: Update translations in branch 4.2 (was Re: Not yet translated functions UNICODE and UNICHAR)

[Matthias Seidel]

Hi Pedro,

The first step would be to update the strings on Pootle with the current 
en-US.SDF.


The strings on Pootle are outdated. New ones were added, some were 
removed, some changed.


Regards,

   Matthias

Am 29.07.24 um 12:26 schrieb Pedro Lino:

Hi Damjan


On 07/28/2024 4:42 PM WEST Damjan Jovanovic  wrote:

  
On Sun, Jul 28, 2024 at 3:39 PM Matthias Seidel 

We need to find volunteers who want to work on it.
And we need to have the will to release AOO 4.2.0.



If it's such a problem, I'll volunteer.
What exactly needs to be done?

Thank you for stepping in!

A short version of the problem (someone please correct me if there are 
inaccuracies) and two possible paths:

1) Translators use the Pootle platform (which has been discontinued but still 
works) to translate the text strings both for the UI and Help of the 4.2 branch
https://translate.apache.org/projects/

2) Translations (in PO format) are converted through some manual process in SDF 
files (I volunteered to learn from Mechtilde but I needed additional karma for 
some of the steps and we could never find who would give it to me)

3) Translations for the several languages are included in our code tree as SDF 
files

What is needed:

Minimum: as a first step that the current Pootle translations are converted to 
SDF and manually merged to the source tree. If this works, we can ask 
volunteers to finish the translations and then hopefully automate the PO to SDF 
to source process so that we can have a complete 4.2 release.

Ideal: a new platform (user friendly and stable/supported) that works with 
"modern" PO files and an automated process to periodically merge those updated 
translations into the source (eliminating the conversion to SDF format). This obviously 
would require the PO strings to be mapped to the interface and included in the Help files.
This solution is more work intensive but would solve the problem into the 
future.

I would suggest that you (Damjan) would help with Minimum and leave the Ideal 
to  some other volunteer who wants to jump in.

Best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Update translations in branch 4.2 (was Re: Not yet translated functions UNICODE and UNICHAR)

[Pedro Lino]

Hi Damjan

> On 07/28/2024 4:42 PM WEST Damjan Jovanovic  wrote:
> 
>  
> On Sun, Jul 28, 2024 at 3:39 PM Matthias Seidel 

> > We need to find volunteers who want to work on it.
> > And we need to have the will to release AOO 4.2.0.
> >
> >
> If it's such a problem, I'll volunteer.
> What exactly needs to be done?

Thank you for stepping in!

A short version of the problem (someone please correct me if there are 
inaccuracies) and two possible paths:

1) Translators use the Pootle platform (which has been discontinued but still 
works) to translate the text strings both for the UI and Help of the 4.2 branch
https://translate.apache.org/projects/

2) Translations (in PO format) are converted through some manual process in SDF 
files (I volunteered to learn from Mechtilde but I needed additional karma for 
some of the steps and we could never find who would give it to me)

3) Translations for the several languages are included in our code tree as SDF 
files

What is needed:

Minimum: as a first step that the current Pootle translations are converted to 
SDF and manually merged to the source tree. If this works, we can ask 
volunteers to finish the translations and then hopefully automate the PO to SDF 
to source process so that we can have a complete 4.2 release.

Ideal: a new platform (user friendly and stable/supported) that works with 
"modern" PO files and an automated process to periodically merge those updated 
translations into the source (eliminating the conversion to SDF format). This 
obviously would require the PO strings to be mapped to the interface and 
included in the Help files. 
This solution is more work intensive but would solve the problem into the 
future.

I would suggest that you (Damjan) would help with Minimum and leave the Ideal 
to  some other volunteer who wants to jump in.

Best,
Pedro

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

Re: Not yet translated functions UNICODE and UNICHAR

[Matthias Seidel]

BTW:

Of course I am available for testing (since 2019 to be exact).

I cannot merge my PRs [1][2] until we have solved this problem...

Regards,

   Matthias

[1] https://github.com/apache/openoffice/pull/168
[2] https://github.com/apache/openoffice/pull/180

Am 28.07.24 um 17:54 schrieb Matthias Seidel:

Hi Damjan,

Am 28.07.24 um 17:42 schrieb Damjan Jovanovic:
On Sun, Jul 28, 2024 at 3:39 PM Matthias Seidel 


wrote:


Hi Aivaras,

Am 28.07.24 um 17:32 schrieb Aivaras Stepukonis:

2024-07-28 11:17, Matthias Seidel rašė:

The last step would be to export the new translations to SDF files
and to merge them with our code.

While I’m not in a position to appreciate the technical reasons for
using SDF files, the working format for localizers is PO files.

 From the standpoint of logic, if POs can be mapped to SDFs and the
latter to the UI of AOO, then, in principle, POs can be mapped
directly to the UI of AOO.

Perhaps getting rid of SDFs altogether would be the strategic path to
take in the future development of this area of code?

The format is not the problem... ;-)

We need to find volunteers who want to work on it.

And we need to have the will to release AOO 4.2.0.



If it's such a problem, I'll volunteer.


Great!



What exactly needs to be done?


Honestly, I am not the one to ask. ;-)

Basically, Pootle is out of date and not maintained anymore. We should 
find an alternative.


But in principle it would be enough for the 4.2.0 release if we could 
get the current process running again, even if it is done manually:


 - Export en-US from AOO42X. That is done by our buildbot every week
 - Import the en-US template into Pootle for all languages
 - Give translators some time to update the new/changed strings
 - Export the translations to SDF files
 - Commit the SDF files to our AOO42X branch (or trunk and then 
cherry-pick them)


Mechtilde and Peter, who did work on that can maybe tell you more.

But I haven't "seen" them for a while.

Regards,

   Matthias





Regards,

 Matthias



Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Not yet translated functions UNICODE and UNICHAR

[Matthias Seidel]

Hi Damjan,

Am 28.07.24 um 17:42 schrieb Damjan Jovanovic:

On Sun, Jul 28, 2024 at 3:39 PM Matthias Seidel 
wrote:


Hi Aivaras,

Am 28.07.24 um 17:32 schrieb Aivaras Stepukonis:

2024-07-28 11:17, Matthias Seidel rašė:

The last step would be to export the new translations to SDF files
and to merge them with our code.

While I’m not in a position to appreciate the technical reasons for
using SDF files, the working format for localizers is PO files.

 From the standpoint of logic, if POs can be mapped to SDFs and the
latter to the UI of AOO, then, in principle, POs can be mapped
directly to the UI of AOO.

Perhaps getting rid of SDFs altogether would be the strategic path to
take in the future development of this area of code?

The format is not the problem... ;-)

We need to find volunteers who want to work on it.

And we need to have the will to release AOO 4.2.0.



If it's such a problem, I'll volunteer.


Great!



What exactly needs to be done?


Honestly, I am not the one to ask. ;-)

Basically, Pootle is out of date and not maintained anymore. We should 
find an alternative.


But in principle it would be enough for the 4.2.0 release if we could 
get the current process running again, even if it is done manually:


 - Export en-US from AOO42X. That is done by our buildbot every week
 - Import the en-US template into Pootle for all languages
 - Give translators some time to update the new/changed strings
 - Export the translations to SDF files
 - Commit the SDF files to our AOO42X branch (or trunk and then 
cherry-pick them)


Mechtilde and Peter, who did work on that can maybe tell you more.

But I haven't "seen" them for a while.

Regards,

   Matthias





Regards,

 Matthias



Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Not yet translated functions UNICODE and UNICHAR

[Matthias Seidel]

Am 28.07.24 um 17:51 schrieb Aivaras Stepukonis:

2024-07-28 18:38, Matthias Seidel rašė:

The format is not the problem... 😉

We need to find volunteers who want to work on it.

And we need to have the will to release AOO 4.2.0. 


The lack of volunteering is certainly /another/ problem; however, I 
don’t see how that explains that SDFs are not a problem. If PO is the 
actual format for translation and Pootle, why not consider using them 
for AOO as well, thus removing one stage from code preparation. Plenty 
of applications do just that. (That may open a prospect for 
translators to see their translations in real time if POs are shipped 
together with the application.)


OK, then go for it!

I simply want to get 4.2.0 out. ;-)


--
Pagarbiai / Sincerely,
📧 Aivaras Stepukonis 

2024-07-28 18:38, Matthias Seidel rašė:

Hi Aivaras,

Am 28.07.24 um 17:32 schrieb Aivaras Stepukonis:

2024-07-28 11:17, Matthias Seidel rašė:
The last step would be to export the new translations to SDF files 
and to merge them with our code.


While I’m not in a position to appreciate the technical reasons for 
using SDF files, the working format for localizers is PO files.


From the standpoint of logic, if POs can be mapped to SDFs and the 
latter to the UI of AOO, then, in principle, POs can be mapped 
directly to the UI of AOO.


Perhaps getting rid of SDFs altogether would be the strategic path 
to take in the future development of this area of code?


The format is not the problem... ;-)

We need to find volunteers who want to work on it.

And we need to have the will to release AOO 4.2.0.

Regards,

   Matthias



--
Pagarbiai / Sincerely,
📧 Aivaras Stepukonis 
 


2024-07-28 13:05, Matthias Seidel rašė:

Dick,

Am 28.07.24 um 11:55 schrieb Dick Groskamp:

Matthias

On 2024/07/28 08:17:48 Matthias Seidel wrote:

Hi Dick,

Am 27.07.24 um 15:37 schrieb Dick Groskamp:

OK, looked into it a bit.

>From the en-us.sdf new templates have to be created, which are 
then uploaded to Pootle.

(This will add new strings and mark deprecated ones)
After that, all existing translations have to be downloaded to disk

The translation does not need to be downloaded.

Maybe, but I didn't have the karma :-)
Then the downloaded translations can be updated with the new 
templates.

That should happen on the Pootle server.

Well, as I understand it, that is the part that is broken :-(
Seems that automated version could leave Pootle in a bad state
https://stackoverflow.com/questions/33630137/what-is-update-against-templates-in-pootle-2-7 


Also Pootle is still Python 2
One catch though:  each language has to be individually been 
updated.

Of course.
After that has been done, syncing the updated files with Pootle 
is the last step.
The last step would be to export the new translations to SDF 
files and

to merge them with our code.

True

Cumbersome :-(
Until we find someone who is willing to work on the process we 
are not

able to release 4.2.0 (after all these years).

The PMC should stop ignoring this fact.

Regards,

     Matthias
I did manage to download nl and update the template with pot2po 
(all on my disk obviously)


I just had a quick look at the difference between earlier SDF 
(2020) and the current one (2024)

There seems to be a difference of sixty lines (60)
Now the challenge is to find them :-)


Well, that is a good challenge, but everything will get overridden 
later (when we have a working process again). ;-)


Regards,

   Matthias


On 2024/07/26 15:26:49 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 16:55 schrieb Dick Groskamp:

On 2024/07/26 11:42:26 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 09:22 schrieb Dick Groskamp:

Matthias,

I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. 
It is dated 20200411.

I think it is the most recent one.

Yes, the "most recent one" (for NL) is 4 years old...

Problems I see is that they are also out of sync.
nl Help-files are not in sync with SDF and also not with 
Pootle.

Everything is out of sync.
For now I fixed the discrepancies by updating the Help-files 
and put them into the *.jars of the nl Help on my machine. 
That seems to work for now.
I also plan to update Pootle with the corrections. That will 
be a manual task I'm afraid :-)

Translation in Pootle has always been a manual process?
Yes, but I wonder how the strings from Pootle for nl ever got 
in Helpfiles :-)

The last export was done by an IBM employee in 2014.

Then I spoke to Mechtilde in 2019 and she got the process 
running again,

but everything was manually.

At one point the process broke (Pootle update?) and here we are.

I have no clue at all. After that then the Helpfiles are 
packaged somehow and delivered to the download package I assume
Then, when translation process would work again, P

Re: Not yet translated functions UNICODE and UNICHAR

[Aivaras Stepukonis]

2024-07-28 18:38, Matthias Seidel rašė:

The format is not the problem... 😉

We need to find volunteers who want to work on it.

And we need to have the will to release AOO 4.2.0. 


The lack of volunteering is certainly /another/ problem; however, I 
don’t see how that explains that SDFs are not a problem. If PO is the 
actual format for translation and Pootle, why not consider using them 
for AOO as well, thus removing one stage from code preparation. Plenty 
of applications do just that. (That may open a prospect for translators 
to see their translations in real time if POs are shipped together with 
the application.)

--
Pagarbiai / Sincerely,
📧 Aivaras Stepukonis 

2024-07-28 18:38, Matthias Seidel rašė:

Hi Aivaras,

Am 28.07.24 um 17:32 schrieb Aivaras Stepukonis:

2024-07-28 11:17, Matthias Seidel rašė:
The last step would be to export the new translations to SDF files 
and to merge them with our code.


While I’m not in a position to appreciate the technical reasons for 
using SDF files, the working format for localizers is PO files.


From the standpoint of logic, if POs can be mapped to SDFs and the 
latter to the UI of AOO, then, in principle, POs can be mapped 
directly to the UI of AOO.


Perhaps getting rid of SDFs altogether would be the strategic path to 
take in the future development of this area of code?


The format is not the problem... ;-)

We need to find volunteers who want to work on it.

And we need to have the will to release AOO 4.2.0.

Regards,

   Matthias



--
Pagarbiai / Sincerely,
📧 Aivaras Stepukonis 

2024-07-28 13:05, Matthias Seidel rašė:

Dick,

Am 28.07.24 um 11:55 schrieb Dick Groskamp:

Matthias

On 2024/07/28 08:17:48 Matthias Seidel wrote:

Hi Dick,

Am 27.07.24 um 15:37 schrieb Dick Groskamp:

OK, looked into it a bit.

>From the en-us.sdf new templates have to be created, which are 
then uploaded to Pootle.

(This will add new strings and mark deprecated ones)
After that, all existing translations have to be downloaded to disk

The translation does not need to be downloaded.

Maybe, but I didn't have the karma :-)
Then the downloaded translations can be updated with the new 
templates.

That should happen on the Pootle server.

Well, as I understand it, that is the part that is broken :-(
Seems that automated version could leave Pootle in a bad state
https://stackoverflow.com/questions/33630137/what-is-update-against-templates-in-pootle-2-7 


Also Pootle is still Python 2
One catch though:  each language has to be individually been 
updated.

Of course.
After that has been done, syncing the updated files with Pootle 
is the last step.
The last step would be to export the new translations to SDF files 
and

to merge them with our code.

True

Cumbersome :-(
Until we find someone who is willing to work on the process we are 
not

able to release 4.2.0 (after all these years).

The PMC should stop ignoring this fact.

Regards,

     Matthias
I did manage to download nl and update the template with pot2po 
(all on my disk obviously)


I just had a quick look at the difference between earlier SDF 
(2020) and the current one (2024)

There seems to be a difference of sixty lines (60)
Now the challenge is to find them :-)


Well, that is a good challenge, but everything will get overridden 
later (when we have a working process again). ;-)


Regards,

   Matthias


On 2024/07/26 15:26:49 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 16:55 schrieb Dick Groskamp:

On 2024/07/26 11:42:26 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 09:22 schrieb Dick Groskamp:

Matthias,

I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. 
It is dated 20200411.

I think it is the most recent one.

Yes, the "most recent one" (for NL) is 4 years old...

Problems I see is that they are also out of sync.
nl Help-files are not in sync with SDF and also not with Pootle.

Everything is out of sync.
For now I fixed the discrepancies by updating the Help-files 
and put them into the *.jars of the nl Help on my machine. 
That seems to work for now.
I also plan to update Pootle with the corrections. That will 
be a manual task I'm afraid :-)

Translation in Pootle has always been a manual process?
Yes, but I wonder how the strings from Pootle for nl ever got 
in Helpfiles :-)

The last export was done by an IBM employee in 2014.

Then I spoke to Mechtilde in 2019 and she got the process 
running again,

but everything was manually.

At one point the process broke (Pootle update?) and here we are.

I have no clue at all. After that then the Helpfiles are 
packaged somehow and delivered to the download package I assume
Then, when translation process would work again, Pootle is in 
sync and updated,

which should deliver correct sdf.

Whenever that will be... ;-)
I haven't seen any

Re: Not yet translated functions UNICODE and UNICHAR

[Damjan Jovanovic]

On Sun, Jul 28, 2024 at 3:39 PM Matthias Seidel 
wrote:

> Hi Aivaras,
>
> Am 28.07.24 um 17:32 schrieb Aivaras Stepukonis:
> > 2024-07-28 11:17, Matthias Seidel rašė:
> >> The last step would be to export the new translations to SDF files
> >> and to merge them with our code.
> >
> > While I’m not in a position to appreciate the technical reasons for
> > using SDF files, the working format for localizers is PO files.
> >
> > From the standpoint of logic, if POs can be mapped to SDFs and the
> > latter to the UI of AOO, then, in principle, POs can be mapped
> > directly to the UI of AOO.
> >
> > Perhaps getting rid of SDFs altogether would be the strategic path to
> > take in the future development of this area of code?
>
> The format is not the problem... ;-)
>
> We need to find volunteers who want to work on it.
>
> And we need to have the will to release AOO 4.2.0.
>
>
If it's such a problem, I'll volunteer.

What exactly needs to be done?


> Regards,
>
> Matthias
>
>
Regards
Damjan

Re: Not yet translated functions UNICODE and UNICHAR

[Matthias Seidel]

Hi Aivaras,

Am 28.07.24 um 17:32 schrieb Aivaras Stepukonis:

2024-07-28 11:17, Matthias Seidel rašė:
The last step would be to export the new translations to SDF files 
and to merge them with our code.


While I’m not in a position to appreciate the technical reasons for 
using SDF files, the working format for localizers is PO files.


From the standpoint of logic, if POs can be mapped to SDFs and the 
latter to the UI of AOO, then, in principle, POs can be mapped 
directly to the UI of AOO.


Perhaps getting rid of SDFs altogether would be the strategic path to 
take in the future development of this area of code?


The format is not the problem... ;-)

We need to find volunteers who want to work on it.

And we need to have the will to release AOO 4.2.0.

Regards,

   Matthias



--
Pagarbiai / Sincerely,
📧 Aivaras Stepukonis 

2024-07-28 13:05, Matthias Seidel rašė:

Dick,

Am 28.07.24 um 11:55 schrieb Dick Groskamp:

Matthias

On 2024/07/28 08:17:48 Matthias Seidel wrote:

Hi Dick,

Am 27.07.24 um 15:37 schrieb Dick Groskamp:

OK, looked into it a bit.

>From the en-us.sdf new templates have to be created, which are 
then uploaded to Pootle.

(This will add new strings and mark deprecated ones)
After that, all existing translations have to be downloaded to disk

The translation does not need to be downloaded.

Maybe, but I didn't have the karma :-)
Then the downloaded translations can be updated with the new 
templates.

That should happen on the Pootle server.

Well, as I understand it, that is the part that is broken :-(
Seems that automated version could leave Pootle in a bad state
https://stackoverflow.com/questions/33630137/what-is-update-against-templates-in-pootle-2-7 


Also Pootle is still Python 2

One catch though:  each language has to be individually been updated.

Of course.
After that has been done, syncing the updated files with Pootle is 
the last step.

The last step would be to export the new translations to SDF files and
to merge them with our code.

True

Cumbersome :-(

Until we find someone who is willing to work on the process we are not
able to release 4.2.0 (after all these years).

The PMC should stop ignoring this fact.

Regards,

     Matthias
I did manage to download nl and update the template with pot2po (all 
on my disk obviously)


I just had a quick look at the difference between earlier SDF (2020) 
and the current one (2024)

There seems to be a difference of sixty lines (60)
Now the challenge is to find them :-)


Well, that is a good challenge, but everything will get overridden 
later (when we have a working process again). ;-)


Regards,

   Matthias


On 2024/07/26 15:26:49 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 16:55 schrieb Dick Groskamp:

On 2024/07/26 11:42:26 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 09:22 schrieb Dick Groskamp:

Matthias,

I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. 
It is dated 20200411.

I think it is the most recent one.

Yes, the "most recent one" (for NL) is 4 years old...

Problems I see is that they are also out of sync.
nl Help-files are not in sync with SDF and also not with Pootle.

Everything is out of sync.
For now I fixed the discrepancies by updating the Help-files 
and put them into the *.jars of the nl Help on my machine. 
That seems to work for now.
I also plan to update Pootle with the corrections. That will 
be a manual task I'm afraid :-)

Translation in Pootle has always been a manual process?
Yes, but I wonder how the strings from Pootle for nl ever got in 
Helpfiles :-)

The last export was done by an IBM employee in 2014.

Then I spoke to Mechtilde in 2019 and she got the process running 
again,

but everything was manually.

At one point the process broke (Pootle update?) and here we are.

I have no clue at all. After that then the Helpfiles are 
packaged somehow and delivered to the download package I assume
Then, when translation process would work again, Pootle is in 
sync and updated,

which should deliver correct sdf.

Whenever that will be... ;-)
I haven't seen any new strings come in the last four/five years 
so I can slowly move forwards.
There were a lot of new strings in that time, but Pootle simply 
wasn't

updated.


One example:
Image for STOP for BASIC macro  (sc_basicstop.png)
was sc_stop.png in nl Help file, showing nothing  :-(
I *think* that was solved at one point, but the changes didn't 
make it

into Pootle.

But you can always try the en-US build to see the actual 
development...


BTW, SDF for en-US is not in our source, it gets exported weekly 
by our

buildbot:

https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D

Regards,

      Matthias


Regards,

       Matthias


Greetings

On 2024/07/25 14:58:18 Matthias Seidel wrote:

Hi Dick,

Am 23.07.24 um 15:12 schrieb Dick Groskamp:

I'm currently working my way through the Helpfiles, trying t

Re: Not yet translated functions UNICODE and UNICHAR

[Aivaras Stepukonis]

2024-07-28 11:17, Matthias Seidel rašė:
The last step would be to export the new translations to SDF files and 
to merge them with our code.


While I’m not in a position to appreciate the technical reasons for 
using SDF files, the working format for localizers is PO files.


From the standpoint of logic, if POs can be mapped to SDFs and the 
latter to the UI of AOO, then, in principle, POs can be mapped directly 
to the UI of AOO.


Perhaps getting rid of SDFs altogether would be the strategic path to 
take in the future development of this area of code?


--
Pagarbiai / Sincerely,
📧 Aivaras Stepukonis 

2024-07-28 13:05, Matthias Seidel rašė:

Dick,

Am 28.07.24 um 11:55 schrieb Dick Groskamp:

Matthias

On 2024/07/28 08:17:48 Matthias Seidel wrote:

Hi Dick,

Am 27.07.24 um 15:37 schrieb Dick Groskamp:

OK, looked into it a bit.

>From the en-us.sdf new templates have to be created, which are 
then uploaded to Pootle.

(This will add new strings and mark deprecated ones)
After that, all existing translations have to be downloaded to disk

The translation does not need to be downloaded.

Maybe, but I didn't have the karma :-)
Then the downloaded translations can be updated with the new 
templates.

That should happen on the Pootle server.

Well, as I understand it, that is the part that is broken :-(
Seems that automated version could leave Pootle in a bad state
https://stackoverflow.com/questions/33630137/what-is-update-against-templates-in-pootle-2-7 


Also Pootle is still Python 2

One catch though:  each language has to be individually been updated.

Of course.
After that has been done, syncing the updated files with Pootle is 
the last step.

The last step would be to export the new translations to SDF files and
to merge them with our code.

True

Cumbersome :-(

Until we find someone who is willing to work on the process we are not
able to release 4.2.0 (after all these years).

The PMC should stop ignoring this fact.

Regards,

     Matthias
I did manage to download nl and update the template with pot2po (all 
on my disk obviously)


I just had a quick look at the difference between earlier SDF (2020) 
and the current one (2024)

There seems to be a difference of sixty lines (60)
Now the challenge is to find them :-)


Well, that is a good challenge, but everything will get overridden 
later (when we have a working process again). ;-)


Regards,

   Matthias


On 2024/07/26 15:26:49 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 16:55 schrieb Dick Groskamp:

On 2024/07/26 11:42:26 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 09:22 schrieb Dick Groskamp:

Matthias,

I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It 
is dated 20200411.

I think it is the most recent one.

Yes, the "most recent one" (for NL) is 4 years old...

Problems I see is that they are also out of sync.
nl Help-files are not in sync with SDF and also not with Pootle.

Everything is out of sync.
For now I fixed the discrepancies by updating the Help-files 
and put them into the *.jars of the nl Help on my machine. That 
seems to work for now.
I also plan to update Pootle with the corrections. That will be 
a manual task I'm afraid :-)

Translation in Pootle has always been a manual process?
Yes, but I wonder how the strings from Pootle for nl ever got in 
Helpfiles :-)

The last export was done by an IBM employee in 2014.

Then I spoke to Mechtilde in 2019 and she got the process running 
again,

but everything was manually.

At one point the process broke (Pootle update?) and here we are.

I have no clue at all. After that then the Helpfiles are packaged 
somehow and delivered to the download package I assume
Then, when translation process would work again, Pootle is in 
sync and updated,

which should deliver correct sdf.

Whenever that will be... ;-)
I haven't seen any new strings come in the last four/five years 
so I can slowly move forwards.
There were a lot of new strings in that time, but Pootle simply 
wasn't

updated.


One example:
Image for STOP for BASIC macro  (sc_basicstop.png)
was sc_stop.png in nl Help file, showing nothing  :-(
I *think* that was solved at one point, but the changes didn't 
make it

into Pootle.

But you can always try the en-US build to see the actual 
development...


BTW, SDF for en-US is not in our source, it gets exported weekly 
by our

buildbot:

https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D

Regards,

      Matthias


Regards,

       Matthias


Greetings

On 2024/07/25 14:58:18 Matthias Seidel wrote:

Hi Dick,

Am 23.07.24 um 15:12 schrieb Dick Groskamp:

I'm currently working my way through the Helpfiles, trying to
synchronize between Pootle and the available SDF and the 
existing

Help-pages for Dutch.

I noticed several discrepancies between those instances.

The available SDF (which ones exactly?) are out of date.
One of the most signif

Re: Not yet translated functions UNICODE and UNICHAR

[Matthias Seidel]

Dick,

Am 28.07.24 um 11:55 schrieb Dick Groskamp:

Matthias

On 2024/07/28 08:17:48 Matthias Seidel wrote:

Hi Dick,

Am 27.07.24 um 15:37 schrieb Dick Groskamp:

OK, looked into it a bit.

>From the en-us.sdf new templates have to be created, which are then uploaded 
to Pootle.
(This will add new strings and mark deprecated ones)
After that, all existing translations have to be downloaded to disk

The translation does not need to be downloaded.

Maybe, but I didn't have the karma :-)

Then the downloaded translations can be updated with the new templates.

That should happen on the Pootle server.

Well, as I understand it, that is the part that is broken :-(
Seems that automated version could leave Pootle in a bad state
https://stackoverflow.com/questions/33630137/what-is-update-against-templates-in-pootle-2-7
Also Pootle is still Python 2

One catch though:  each language has to be individually been updated.

Of course.

After that has been done, syncing the updated files with Pootle is the last 
step.

The last step would be to export the new translations to SDF files and
to merge them with our code.

True

Cumbersome :-(

Until we find someone who is willing to work on the process we are not
able to release 4.2.0 (after all these years).

The PMC should stop ignoring this fact.

Regards,

     Matthias

I did manage to download nl and update the template with pot2po (all on my disk 
obviously)

I just had a quick look at the difference between earlier SDF (2020) and the 
current one (2024)
There seems to be a difference of sixty lines (60)
Now the challenge is to find them :-)


Well, that is a good challenge, but everything will get overridden later 
(when we have a working process again). ;-)


Regards,

   Matthias


On 2024/07/26 15:26:49 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 16:55 schrieb Dick Groskamp:

On 2024/07/26 11:42:26 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 09:22 schrieb Dick Groskamp:

Matthias,

I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated 
20200411.
I think it is the most recent one.

Yes, the "most recent one" (for NL) is 4 years old...

Problems I see is that they are also out of sync.
nl Help-files are not in sync with SDF and also not with Pootle.

Everything is out of sync.

For now I fixed the discrepancies by updating the Help-files and put them into 
the *.jars of the nl Help on my machine.  That seems to work for now.
I also plan to update Pootle with the corrections. That will be a manual task 
I'm afraid :-)

Translation in Pootle has always been a manual process?

Yes, but I wonder how the strings from Pootle for nl ever got in Helpfiles :-)

The last export was done by an IBM employee in 2014.

Then I spoke to Mechtilde in 2019 and she got the process running again,
but everything was manually.

At one point the process broke (Pootle update?) and here we are.


I have no clue at all. After that then the Helpfiles are packaged somehow and 
delivered to the download package I assume

Then, when translation process would work again, Pootle is in sync and updated,
which should deliver correct sdf.

Whenever that will be... ;-)

I haven't seen any new strings come in the last four/five years so I can slowly 
move forwards.

There were a lot of new strings in that time, but Pootle simply wasn't
updated.


One example:
Image for STOP for BASIC macro  (sc_basicstop.png)
was sc_stop.png in nl Help file, showing nothing  :-(

I *think* that was solved at one point, but the changes didn't make it
into Pootle.

But you can always try the en-US build to see the actual development...

BTW, SDF for en-US is not in our source, it gets exported weekly by our
buildbot:

https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D

Regards,

      Matthias


Regards,

   Matthias


Greetings

On 2024/07/25 14:58:18 Matthias Seidel wrote:

Hi Dick,

Am 23.07.24 um 15:12 schrieb Dick Groskamp:

I'm currently working my way through the Helpfiles, trying to
synchronize between Pootle and the available SDF and the existing
Help-pages for Dutch.

I noticed several discrepancies between those instances.

The available SDF (which ones exactly?) are out of date.

One of the most significant is the missing translation in the SDF for
the functions UNICODE and UNICHAR,

that is, they are mentioned for the Help-files, but not for the UI
(there they still are UNICODE and UNICHAR)

Would it be possible to already add the translations for these
functions, or do I have to go to all the Help-files first to get
POOTLE fully up to date?

It concerns just two small strings for the UI:

formula    source\core\resource\core_resource.src    0 string
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICODE ->    nl UNI.CODE
formula    source\core\resource\core_resource.src    0 string
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICHAR --> nl    UNI.TEKEN


I've already added them to Pootle, but don't know how to get them in
the upcoming builds.

*When* the tr

Re: Not yet translated functions UNICODE and UNICHAR

[Dick Groskamp]

Matthias

On 2024/07/28 08:17:48 Matthias Seidel wrote:
> Hi Dick,
> 
> Am 27.07.24 um 15:37 schrieb Dick Groskamp:
> > OK, looked into it a bit.
> >
> > >From the en-us.sdf new templates have to be created, which are then 
> > >uploaded to Pootle.
> > (This will add new strings and mark deprecated ones)
> > After that, all existing translations have to be downloaded to disk
> The translation does not need to be downloaded.
Maybe, but I didn't have the karma :-)
> > Then the downloaded translations can be updated with the new templates.
> That should happen on the Pootle server.
Well, as I understand it, that is the part that is broken :-( 
Seems that automated version could leave Pootle in a bad state
https://stackoverflow.com/questions/33630137/what-is-update-against-templates-in-pootle-2-7
Also Pootle is still Python 2
> > One catch though:  each language has to be individually been updated.
> Of course.
> > After that has been done, syncing the updated files with Pootle is the last 
> > step.
> The last step would be to export the new translations to SDF files and 
> to merge them with our code.
True
> >
> > Cumbersome :-(
> 
> Until we find someone who is willing to work on the process we are not 
> able to release 4.2.0 (after all these years).
> 
> The PMC should stop ignoring this fact.
> 
> Regards,
> 
>     Matthias

I did manage to download nl and update the template with pot2po (all on my disk 
obviously)

I just had a quick look at the difference between earlier SDF (2020) and the 
current one (2024)
There seems to be a difference of sixty lines (60)
Now the challenge is to find them :-)
> >
> > On 2024/07/26 15:26:49 Matthias Seidel wrote:
> >> Hi Dick,
> >>
> >> Am 26.07.24 um 16:55 schrieb Dick Groskamp:
> >>> On 2024/07/26 11:42:26 Matthias Seidel wrote:
>  Hi Dick,
> 
>  Am 26.07.24 um 09:22 schrieb Dick Groskamp:
> > Matthias,
> >
> > I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is 
> > dated 20200411.
> > I think it is the most recent one.
>  Yes, the "most recent one" (for NL) is 4 years old...
> > Problems I see is that they are also out of sync.
> > nl Help-files are not in sync with SDF and also not with Pootle.
>  Everything is out of sync.
> > For now I fixed the discrepancies by updating the Help-files and put 
> > them into the *.jars of the nl Help on my machine.  That seems to work 
> > for now.
> > I also plan to update Pootle with the corrections. That will be a 
> > manual task I'm afraid :-)
>  Translation in Pootle has always been a manual process?
> >>> Yes, but I wonder how the strings from Pootle for nl ever got in 
> >>> Helpfiles :-)
> >> The last export was done by an IBM employee in 2014.
> >>
> >> Then I spoke to Mechtilde in 2019 and she got the process running again,
> >> but everything was manually.
> >>
> >> At one point the process broke (Pootle update?) and here we are.
> >>
> >>> I have no clue at all. After that then the Helpfiles are packaged somehow 
> >>> and delivered to the download package I assume
> > Then, when translation process would work again, Pootle is in sync and 
> > updated,
> > which should deliver correct sdf.
>  Whenever that will be... ;-)
> >>> I haven't seen any new strings come in the last four/five years so I can 
> >>> slowly move forwards.
> >> There were a lot of new strings in that time, but Pootle simply wasn't
> >> updated.
> >>
> >>> One example:
> >>> Image for STOP for BASIC macro  (sc_basicstop.png)
> >>> was sc_stop.png in nl Help file, showing nothing  :-(
> >> I *think* that was solved at one point, but the changes didn't make it
> >> into Pootle.
> >>
> >> But you can always try the en-US build to see the actual development...
> >>
> >> BTW, SDF for en-US is not in our source, it gets exported weekly by our
> >> buildbot:
> >>
> >> https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D
> >>
> >> Regards,
> >>
> >>      Matthias
> >>
>  Regards,
> 
>    Matthias
> 
> > Greetings
> >
> > On 2024/07/25 14:58:18 Matthias Seidel wrote:
> >> Hi Dick,
> >>
> >> Am 23.07.24 um 15:12 schrieb Dick Groskamp:
> >>> I'm currently working my way through the Helpfiles, trying to
> >>> synchronize between Pootle and the available SDF and the existing
> >>> Help-pages for Dutch.
> >>>
> >>> I noticed several discrepancies between those instances.
> >> The available SDF (which ones exactly?) are out of date.
> >>> One of the most significant is the missing translation in the SDF for
> >>> the functions UNICODE and UNICHAR,
> >>>
> >>> that is, they are mentioned for the Help-files, but not for the UI
> >>> (there they still are UNICODE and UNICHAR)
> >>>
> >>> Would it be possible to already add the translations for these
> >>> functions, or do I have to go to all the Help-files first to get
> >>> POOTLE fully up t

Re: Not yet translated functions UNICODE and UNICHAR

[Matthias Seidel]

Hi Dick,

Am 27.07.24 um 15:37 schrieb Dick Groskamp:

OK, looked into it a bit.

>From the en-us.sdf new templates have to be created, which are then uploaded 
to Pootle.
(This will add new strings and mark deprecated ones)
After that, all existing translations have to be downloaded to disk

The translation does not need to be downloaded.

Then the downloaded translations can be updated with the new templates.

That should happen on the Pootle server.

One catch though:  each language has to be individually been updated.

Of course.

After that has been done, syncing the updated files with Pootle is the last 
step.
The last step would be to export the new translations to SDF files and 
to merge them with our code.


Cumbersome :-(


Until we find someone who is willing to work on the process we are not 
able to release 4.2.0 (after all these years).


The PMC should stop ignoring this fact.

Regards,

   Matthias



On 2024/07/26 15:26:49 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 16:55 schrieb Dick Groskamp:

On 2024/07/26 11:42:26 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 09:22 schrieb Dick Groskamp:

Matthias,

I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated 
20200411.
I think it is the most recent one.

Yes, the "most recent one" (for NL) is 4 years old...

Problems I see is that they are also out of sync.
nl Help-files are not in sync with SDF and also not with Pootle.

Everything is out of sync.

For now I fixed the discrepancies by updating the Help-files and put them into 
the *.jars of the nl Help on my machine.  That seems to work for now.
I also plan to update Pootle with the corrections. That will be a manual task 
I'm afraid :-)

Translation in Pootle has always been a manual process?

Yes, but I wonder how the strings from Pootle for nl ever got in Helpfiles :-)

The last export was done by an IBM employee in 2014.

Then I spoke to Mechtilde in 2019 and she got the process running again,
but everything was manually.

At one point the process broke (Pootle update?) and here we are.


I have no clue at all. After that then the Helpfiles are packaged somehow and 
delivered to the download package I assume

Then, when translation process would work again, Pootle is in sync and updated,
which should deliver correct sdf.

Whenever that will be... ;-)

I haven't seen any new strings come in the last four/five years so I can slowly 
move forwards.

There were a lot of new strings in that time, but Pootle simply wasn't
updated.


One example:
Image for STOP for BASIC macro  (sc_basicstop.png)
was sc_stop.png in nl Help file, showing nothing  :-(

I *think* that was solved at one point, but the changes didn't make it
into Pootle.

But you can always try the en-US build to see the actual development...

BTW, SDF for en-US is not in our source, it gets exported weekly by our
buildbot:

https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D

Regards,

     Matthias


Regards,

      Matthias


Greetings

On 2024/07/25 14:58:18 Matthias Seidel wrote:

Hi Dick,

Am 23.07.24 um 15:12 schrieb Dick Groskamp:

I'm currently working my way through the Helpfiles, trying to
synchronize between Pootle and the available SDF and the existing
Help-pages for Dutch.

I noticed several discrepancies between those instances.

The available SDF (which ones exactly?) are out of date.

One of the most significant is the missing translation in the SDF for
the functions UNICODE and UNICHAR,

that is, they are mentioned for the Help-files, but not for the UI
(there they still are UNICODE and UNICHAR)

Would it be possible to already add the translations for these
functions, or do I have to go to all the Help-files first to get
POOTLE fully up to date?

It concerns just two small strings for the UI:

formula    source\core\resource\core_resource.src    0 string
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICODE ->    nl UNI.CODE
formula    source\core\resource\core_resource.src    0 string
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICHAR --> nl    UNI.TEKEN


I've already added them to Pootle, but don't know how to get them in
the upcoming builds.

*When* the translation process is working again, you will find them in
AOO42X.

Regards,

   Matthias


If they are not there, only way to use them is to use English names,
but, as you understand, that's not synchronized with Help


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


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


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



smime.p

Re: Not yet translated functions UNICODE and UNICHAR

[Dick Groskamp]

OK, looked into it a bit.

>From the en-us.sdf new templates have to be created, which are then uploaded 
>to Pootle.
(This will add new strings and mark deprecated ones)
After that, all existing translations have to be downloaded to disk
Then the downloaded translations can be updated with the new templates.
One catch though:  each language has to be individually been updated.
After that has been done, syncing the updated files with Pootle is the last 
step.

Cumbersome :-( 

On 2024/07/26 15:26:49 Matthias Seidel wrote:
> Hi Dick,
> 
> Am 26.07.24 um 16:55 schrieb Dick Groskamp:
> > On 2024/07/26 11:42:26 Matthias Seidel wrote:
> >> Hi Dick,
> >>
> >> Am 26.07.24 um 09:22 schrieb Dick Groskamp:
> >>> Matthias,
> >>>
> >>> I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated 
> >>> 20200411.
> >>> I think it is the most recent one.
> >> Yes, the "most recent one" (for NL) is 4 years old...
> >>> Problems I see is that they are also out of sync.
> >>> nl Help-files are not in sync with SDF and also not with Pootle.
> >> Everything is out of sync.
> >>> For now I fixed the discrepancies by updating the Help-files and put them 
> >>> into the *.jars of the nl Help on my machine.  That seems to work for now.
> >>> I also plan to update Pootle with the corrections. That will be a manual 
> >>> task I'm afraid :-)
> >> Translation in Pootle has always been a manual process?
> > Yes, but I wonder how the strings from Pootle for nl ever got in Helpfiles 
> > :-)
> 
> The last export was done by an IBM employee in 2014.
> 
> Then I spoke to Mechtilde in 2019 and she got the process running again, 
> but everything was manually.
> 
> At one point the process broke (Pootle update?) and here we are.
> 
> > I have no clue at all. After that then the Helpfiles are packaged somehow 
> > and delivered to the download package I assume
> >>> Then, when translation process would work again, Pootle is in sync and 
> >>> updated,
> >>> which should deliver correct sdf.
> >> Whenever that will be... ;-)
> > I haven't seen any new strings come in the last four/five years so I can 
> > slowly move forwards.
> 
> There were a lot of new strings in that time, but Pootle simply wasn't 
> updated.
> 
> >
> > One example:
> > Image for STOP for BASIC macro  (sc_basicstop.png)
> > was sc_stop.png in nl Help file, showing nothing  :-(
> 
> I *think* that was solved at one point, but the changes didn't make it 
> into Pootle.
> 
> But you can always try the en-US build to see the actual development...
> 
> BTW, SDF for en-US is not in our source, it gets exported weekly by our 
> buildbot:
> 
> https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D
> 
> Regards,
> 
>     Matthias
> 
> >> Regards,
> >>
> >>      Matthias
> >>
> >>> Greetings
> >>>
> >>> On 2024/07/25 14:58:18 Matthias Seidel wrote:
>  Hi Dick,
> 
>  Am 23.07.24 um 15:12 schrieb Dick Groskamp:
> > I'm currently working my way through the Helpfiles, trying to
> > synchronize between Pootle and the available SDF and the existing
> > Help-pages for Dutch.
> >
> > I noticed several discrepancies between those instances.
>  The available SDF (which ones exactly?) are out of date.
> > One of the most significant is the missing translation in the SDF for
> > the functions UNICODE and UNICHAR,
> >
> > that is, they are mentioned for the Help-files, but not for the UI
> > (there they still are UNICODE and UNICHAR)
> >
> > Would it be possible to already add the translations for these
> > functions, or do I have to go to all the Help-files first to get
> > POOTLE fully up to date?
> >
> > It concerns just two small strings for the UI:
> >
> > formula    source\core\resource\core_resource.src    0 string
> > RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICODE ->    nl UNI.CODE
> > formula    source\core\resource\core_resource.src    0 string
> > RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICHAR --> nl    UNI.TEKEN
> >
> >
> > I've already added them to Pootle, but don't know how to get them in
> > the upcoming builds.
>  *When* the translation process is working again, you will find them in
>  AOO42X.
> 
>  Regards,
> 
>    Matthias
> 
> > If they are not there, only way to use them is to use English names,
> > but, as you understand, that's not synchronized with Help
> >
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>>
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
> 

-
To unsubscribe, e-mail

Re: Not yet translated functions UNICODE and UNICHAR

[Matthias Seidel]

Hi Dick,

Am 26.07.24 um 16:55 schrieb Dick Groskamp:

On 2024/07/26 11:42:26 Matthias Seidel wrote:

Hi Dick,

Am 26.07.24 um 09:22 schrieb Dick Groskamp:

Matthias,

I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated 
20200411.
I think it is the most recent one.

Yes, the "most recent one" (for NL) is 4 years old...

Problems I see is that they are also out of sync.
nl Help-files are not in sync with SDF and also not with Pootle.

Everything is out of sync.

For now I fixed the discrepancies by updating the Help-files and put them into 
the *.jars of the nl Help on my machine.  That seems to work for now.
I also plan to update Pootle with the corrections. That will be a manual task 
I'm afraid :-)

Translation in Pootle has always been a manual process?

Yes, but I wonder how the strings from Pootle for nl ever got in Helpfiles :-)


The last export was done by an IBM employee in 2014.

Then I spoke to Mechtilde in 2019 and she got the process running again, 
but everything was manually.


At one point the process broke (Pootle update?) and here we are.


I have no clue at all. After that then the Helpfiles are packaged somehow and 
delivered to the download package I assume

Then, when translation process would work again, Pootle is in sync and updated,
which should deliver correct sdf.

Whenever that will be... ;-)

I haven't seen any new strings come in the last four/five years so I can slowly 
move forwards.


There were a lot of new strings in that time, but Pootle simply wasn't 
updated.




One example:
Image for STOP for BASIC macro  (sc_basicstop.png)
was sc_stop.png in nl Help file, showing nothing  :-(


I *think* that was solved at one point, but the changes didn't make it 
into Pootle.


But you can always try the en-US build to see the actual development...

BTW, SDF for en-US is not in our source, it gets exported weekly by our 
buildbot:


https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D

Regards,

   Matthias


Regards,

     Matthias


Greetings

On 2024/07/25 14:58:18 Matthias Seidel wrote:

Hi Dick,

Am 23.07.24 um 15:12 schrieb Dick Groskamp:

I'm currently working my way through the Helpfiles, trying to
synchronize between Pootle and the available SDF and the existing
Help-pages for Dutch.

I noticed several discrepancies between those instances.

The available SDF (which ones exactly?) are out of date.

One of the most significant is the missing translation in the SDF for
the functions UNICODE and UNICHAR,

that is, they are mentioned for the Help-files, but not for the UI
(there they still are UNICODE and UNICHAR)

Would it be possible to already add the translations for these
functions, or do I have to go to all the Help-files first to get
POOTLE fully up to date?

It concerns just two small strings for the UI:

formula    source\core\resource\core_resource.src    0 string
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICODE ->    nl UNI.CODE
formula    source\core\resource\core_resource.src    0 string
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICHAR --> nl    UNI.TEKEN


I've already added them to Pootle, but don't know how to get them in
the upcoming builds.

*When* the translation process is working again, you will find them in
AOO42X.

Regards,

      Matthias


If they are not there, only way to use them is to use English names,
but, as you understand, that's not synchronized with Help


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


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Not yet translated functions UNICODE and UNICHAR

[Dick Groskamp]

On 2024/07/26 11:42:26 Matthias Seidel wrote:
> Hi Dick,
> 
> Am 26.07.24 um 09:22 schrieb Dick Groskamp:
> > Matthias,
> >
> > I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated 
> > 20200411.
> > I think it is the most recent one.
> Yes, the "most recent one" (for NL) is 4 years old...
> >
> > Problems I see is that they are also out of sync.
> > nl Help-files are not in sync with SDF and also not with Pootle.
> Everything is out of sync.
> >
> > For now I fixed the discrepancies by updating the Help-files and put them 
> > into the *.jars of the nl Help on my machine.  That seems to work for now.
> > I also plan to update Pootle with the corrections. That will be a manual 
> > task I'm afraid :-)
> 
> Translation in Pootle has always been a manual process?

Yes, but I wonder how the strings from Pootle for nl ever got in Helpfiles :-)
I have no clue at all. After that then the Helpfiles are packaged somehow and 
delivered to the download package I assume
> 
> > Then, when translation process would work again, Pootle is in sync and 
> > updated,
> > which should deliver correct sdf.
> 
> Whenever that will be... ;-)

I haven't seen any new strings come in the last four/five years so I can slowly 
move forwards.

One example:
Image for STOP for BASIC macro  (sc_basicstop.png)
was sc_stop.png in nl Help file, showing nothing  :-(
> 
> Regards,
> 
>     Matthias
> 
> >
> > Greetings
> >
> > On 2024/07/25 14:58:18 Matthias Seidel wrote:
> >> Hi Dick,
> >>
> >> Am 23.07.24 um 15:12 schrieb Dick Groskamp:
> >>> I'm currently working my way through the Helpfiles, trying to
> >>> synchronize between Pootle and the available SDF and the existing
> >>> Help-pages for Dutch.
> >>>
> >>> I noticed several discrepancies between those instances.
> >> The available SDF (which ones exactly?) are out of date.
> >>> One of the most significant is the missing translation in the SDF for
> >>> the functions UNICODE and UNICHAR,
> >>>
> >>> that is, they are mentioned for the Help-files, but not for the UI
> >>> (there they still are UNICODE and UNICHAR)
> >>>
> >>> Would it be possible to already add the translations for these
> >>> functions, or do I have to go to all the Help-files first to get
> >>> POOTLE fully up to date?
> >>>
> >>> It concerns just two small strings for the UI:
> >>>
> >>> formula    source\core\resource\core_resource.src    0 string
> >>> RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICODE ->    nl UNI.CODE
> >>> formula    source\core\resource\core_resource.src    0 string
> >>> RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICHAR --> nl    UNI.TEKEN
> >>>
> >>>
> >>> I've already added them to Pootle, but don't know how to get them in
> >>> the upcoming builds.
> >> *When* the translation process is working again, you will find them in
> >> AOO42X.
> >>
> >> Regards,
> >>
> >>      Matthias
> >>
> >>> If they are not there, only way to use them is to use English names,
> >>> but, as you understand, that's not synchronized with Help
> >>>
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
> 

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

Re: Not yet translated functions UNICODE and UNICHAR

[Matthias Seidel]

Hi Dick,

Am 26.07.24 um 09:22 schrieb Dick Groskamp:

Matthias,

I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated 
20200411.
I think it is the most recent one.

Yes, the "most recent one" (for NL) is 4 years old...


Problems I see is that they are also out of sync.
nl Help-files are not in sync with SDF and also not with Pootle.

Everything is out of sync.


For now I fixed the discrepancies by updating the Help-files and put them into 
the *.jars of the nl Help on my machine.  That seems to work for now.
I also plan to update Pootle with the corrections. That will be a manual task 
I'm afraid :-)


Translation in Pootle has always been a manual process?


Then, when translation process would work again, Pootle is in sync and updated,
which should deliver correct sdf.


Whenever that will be... ;-)

Regards,

   Matthias



Greetings

On 2024/07/25 14:58:18 Matthias Seidel wrote:

Hi Dick,

Am 23.07.24 um 15:12 schrieb Dick Groskamp:

I'm currently working my way through the Helpfiles, trying to
synchronize between Pootle and the available SDF and the existing
Help-pages for Dutch.

I noticed several discrepancies between those instances.

The available SDF (which ones exactly?) are out of date.

One of the most significant is the missing translation in the SDF for
the functions UNICODE and UNICHAR,

that is, they are mentioned for the Help-files, but not for the UI
(there they still are UNICODE and UNICHAR)

Would it be possible to already add the translations for these
functions, or do I have to go to all the Help-files first to get
POOTLE fully up to date?

It concerns just two small strings for the UI:

formula    source\core\resource\core_resource.src    0 string
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICODE ->    nl UNI.CODE
formula    source\core\resource\core_resource.src    0 string
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICHAR --> nl    UNI.TEKEN


I've already added them to Pootle, but don't know how to get them in
the upcoming builds.

*When* the translation process is working again, you will find them in
AOO42X.

Regards,

     Matthias


If they are not there, only way to use them is to use English names,
but, as you understand, that's not synchronized with Help


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Not yet translated functions UNICODE and UNICHAR

[Dick Groskamp]

BTW, does someone know what is wrong/defect with the translation process ??



On 2024/07/25 14:58:18 Matthias Seidel wrote:
> Hi Dick,
> 
> Am 23.07.24 um 15:12 schrieb Dick Groskamp:
> > I'm currently working my way through the Helpfiles, trying to 
> > synchronize between Pootle and the available SDF and the existing 
> > Help-pages for Dutch.
> >
> > I noticed several discrepancies between those instances.
> The available SDF (which ones exactly?) are out of date.
> >
> > One of the most significant is the missing translation in the SDF for 
> > the functions UNICODE and UNICHAR,
> >
> > that is, they are mentioned for the Help-files, but not for the UI 
> > (there they still are UNICODE and UNICHAR)
> >
> > Would it be possible to already add the translations for these 
> > functions, or do I have to go to all the Help-files first to get 
> > POOTLE fully up to date?
> >
> > It concerns just two small strings for the UI:
> >
> > formula    source\core\resource\core_resource.src    0 string 
> > RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICODE ->    nl UNI.CODE
> > formula    source\core\resource\core_resource.src    0 string 
> > RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICHAR --> nl    UNI.TEKEN
> >
> >
> > I've already added them to Pootle, but don't know how to get them in 
> > the upcoming builds.
> 
> *When* the translation process is working again, you will find them in 
> AOO42X.
> 
> Regards,
> 
>     Matthias
> 
> >
> > If they are not there, only way to use them is to use English names, 
> > but, as you understand, that's not synchronized with Help
> >
> 

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

Re: Not yet translated functions UNICODE and UNICHAR

[Dick Groskamp]

Matthias,

I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated 
20200411.
I think it is the most recent one.

Problems I see is that they are also out of sync.
nl Help-files are not in sync with SDF and also not with Pootle.

For now I fixed the discrepancies by updating the Help-files and put them into 
the *.jars of the nl Help on my machine.  That seems to work for now.
I also plan to update Pootle with the corrections. That will be a manual task 
I'm afraid :-)
Then, when translation process would work again, Pootle is in sync and updated,
which should deliver correct sdf.

Greetings

On 2024/07/25 14:58:18 Matthias Seidel wrote:
> Hi Dick,
> 
> Am 23.07.24 um 15:12 schrieb Dick Groskamp:
> > I'm currently working my way through the Helpfiles, trying to 
> > synchronize between Pootle and the available SDF and the existing 
> > Help-pages for Dutch.
> >
> > I noticed several discrepancies between those instances.
> The available SDF (which ones exactly?) are out of date.
> >
> > One of the most significant is the missing translation in the SDF for 
> > the functions UNICODE and UNICHAR,
> >
> > that is, they are mentioned for the Help-files, but not for the UI 
> > (there they still are UNICODE and UNICHAR)
> >
> > Would it be possible to already add the translations for these 
> > functions, or do I have to go to all the Help-files first to get 
> > POOTLE fully up to date?
> >
> > It concerns just two small strings for the UI:
> >
> > formula    source\core\resource\core_resource.src    0 string 
> > RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICODE ->    nl UNI.CODE
> > formula    source\core\resource\core_resource.src    0 string 
> > RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICHAR --> nl    UNI.TEKEN
> >
> >
> > I've already added them to Pootle, but don't know how to get them in 
> > the upcoming builds.
> 
> *When* the translation process is working again, you will find them in 
> AOO42X.
> 
> Regards,
> 
>     Matthias
> 
> >
> > If they are not there, only way to use them is to use English names, 
> > but, as you understand, that's not synchronized with Help
> >
> 

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

Re: Not yet translated functions UNICODE and UNICHAR

[Matthias Seidel]

Hi Dick,

Am 23.07.24 um 15:12 schrieb Dick Groskamp:
I'm currently working my way through the Helpfiles, trying to 
synchronize between Pootle and the available SDF and the existing 
Help-pages for Dutch.


I noticed several discrepancies between those instances.

The available SDF (which ones exactly?) are out of date.


One of the most significant is the missing translation in the SDF for 
the functions UNICODE and UNICHAR,


that is, they are mentioned for the Help-files, but not for the UI 
(there they still are UNICODE and UNICHAR)


Would it be possible to already add the translations for these 
functions, or do I have to go to all the Help-files first to get 
POOTLE fully up to date?


It concerns just two small strings for the UI:

formula    source\core\resource\core_resource.src    0 string 
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICODE ->    nl UNI.CODE
formula    source\core\resource\core_resource.src    0 string 
RID_STRLIST_FUNCTION_NAMES    SC_OPCODE_UNICHAR --> nl    UNI.TEKEN



I've already added them to Pootle, but don't know how to get them in 
the upcoming builds.


*When* the translation process is working again, you will find them in 
AOO42X.


Regards,

   Matthias



If they are not there, only way to use them is to use English names, 
but, as you understand, that's not synchronized with Help




smime.p7s
Description: Kryptografische S/MIME-Signatur