Re: [Discussion] Pootle Migration - Git Connection
Hello Peter, > For example. 4.1.x and 4.2.x Translation sets do not match. Maybe > we could use Git to have a 4.2.x branch,another branch will contain > 4.1.x Translation files. Git is not a dedicated tool for translation strings If I understood, we will have .po files and should use a specific software to make this. After work done, pushing PRs to contribute. IMO, this is not easy for end-users who help to contribute. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[Discussion] Pootle Migration - Git Connection
Forgot the Discussion flag. :( Am 29.05.22 um 23:41 schrieb Peter Kovacs: Hello all, I am still working myself into Pootle. Pootle stores the translation at default on the filesystem. There is a backend which can utilize git. Pootle commit changes on the translation towards the git repository. It would give us maybe the opportunity to maintain different Iteration of OpenOffice Translation texts. For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation files. We could then think of a Version Mapping and a back push translation system. This is just a crazy Idea at this moment, to manage the string changes between Versions. What do you think? Is this an Idea to look into? Please write me your opinion. Thanks. All the best Peter - 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
[GitHub] [openoffice] cbmarcum opened a new pull request, #150: Refs #i112383# and #i117960#. - backporting to AOO41X
cbmarcum opened a new pull request, #150:
URL: https://github.com/apache/openoffice/pull/150
Can't cherry-pick due to file changes and both commits changed the same test
file.
Original commit messages and links follow:
#i112383# CLng('&H') fails on 64-bits rather than returning -1
Found-by: andrew
Patch-by: Damjan Jovanovic
https://github.com/apache/openoffice/commit/323c350123d05cd9f450aebd421b7bfa74c331d2
#i117960# Basic: Line Input doesn't work in single-line If
i92642 added the ability to use certain keywords as variable names (eg. name
= 1, line = 'hi'),
but also caused a regression where "Line Input" is broken in single-line If
statements.
This patch fixes that by allowing Then and Else to also be the start-of-line
tokens expected to
immediately preceed the 'Line' token in order for that 'Line' token to be
recognized a keyword instead
of a variable name. Also added FVT spreadsheet tests for 'Line' as both a
variable name and as 'Line Input'.
Patch by: Damjan Jovanovic
https://github.com/apache/openoffice/commit/725d867363770a4c47c4b3c6dbe1f359c296604a
--
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.
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
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
[Pootle Migration] Git Connection
Hello all, I am still working myself into Pootle. Pootle stores the translation at default on the filesystem. There is a backend which can utilize git. Pootle commit changes on the translation towards the git repository. It would give us maybe the opportunity to maintain different Iteration of OpenOffice Translation texts. For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation files. We could then think of a Version Mapping and a back push translation system. This is just a crazy Idea at this moment, to manage the string changes between Versions. What do you think? Is this an Idea to look into? Please write me your opinion. Thanks. All the best Peter - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] cbmarcum merged pull request #149: Fix TestFormulaDocs to run against AOO41X, make parameterized, and fix late screenshots
cbmarcum merged PR #149: URL: https://github.com/apache/openoffice/pull/149 -- 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. To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 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
[GitHub] [openoffice] cbmarcum opened a new pull request, #149: Fix test formula docs
cbmarcum opened a new pull request, #149: URL: https://github.com/apache/openoffice/pull/149 updated TestFormulaDocs test to be a parameterized test to better see which document failed. Fixed late screenshots on failures. Added timeout for dialog hangs when running tests against AOO41X branch due to some BASIC bug fixes for i112383 [1] and it's commit [2] and i117960 [3] and it's commit [4] not being back-ported to AOO41X. [1] https://bz.apache.org/ooo/show_bug.cgi?id=112383 [2] https://github.com/cbmarcum/openoffice/commit/323c350123d05cd9f450aebd421b7bfa74c331d2 [3] https://bz.apache.org/ooo/show_bug.cgi?id=117960 [4] https://github.com/apache/openoffice/commit/725d867363770a4c47c4b3c6dbe1f359c296604a -- 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. To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 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
