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
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.a
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
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 th
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 reposito
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 s
