Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx merged PR #213: URL: https://github.com/apache/openoffice/pull/213 -- 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
[PR] misc: fix spelling [openoffice]
jbampton opened a new pull request, #213: URL: https://github.com/apache/openoffice/pull/213 (no comment) -- 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
Re: [PR] Fix spelling in code comments [openoffice]
Pilot-Pirx merged PR #212: URL: https://github.com/apache/openoffice/pull/212 -- 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
[PR] Fix spelling in code comments [openoffice]
jbampton opened a new pull request, #212: URL: https://github.com/apache/openoffice/pull/212 (no comment) -- 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
Re: [PR] Fix spelling in code comments [openoffice]
Pilot-Pirx merged PR #211: URL: https://github.com/apache/openoffice/pull/211 -- 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
[PR] Fix spelling in code comments [openoffice]
jbampton opened a new pull request, #211: URL: https://github.com/apache/openoffice/pull/211 (no comment) -- 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
Re: [PR] Fix spelling in code comments [openoffice]
Pilot-Pirx merged PR #210: URL: https://github.com/apache/openoffice/pull/210 -- 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
[PR] Fix spelling in code comments [openoffice]
jbampton opened a new pull request, #210: URL: https://github.com/apache/openoffice/pull/210 (no comment) -- 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
Re: [PR] Fix spelling in comments [openoffice]
Pilot-Pirx merged PR #209: URL: https://github.com/apache/openoffice/pull/209 -- 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
[PR] Fix spelling in comments [openoffice]
jbampton opened a new pull request, #209: URL: https://github.com/apache/openoffice/pull/209 (no comment) -- 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
Re: [PR] Fix spelling in code comments [openoffice]
Pilot-Pirx commented on PR #208: URL: https://github.com/apache/openoffice/pull/208#issuecomment-2029737332 Thanks again! -- 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
Re: [PR] Fix spelling in code comments [openoffice]
Pilot-Pirx merged PR #208: URL: https://github.com/apache/openoffice/pull/208 -- 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
[PR] Fix spelling in code comments [openoffice]
jbampton opened a new pull request, #208: URL: https://github.com/apache/openoffice/pull/208 (no comment) -- 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
Re: [PR] Fix spelling in code comments and descriptions only [openoffice]
Pilot-Pirx merged PR #207: URL: https://github.com/apache/openoffice/pull/207 -- 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
[PR] Fix spelling in code comments and descriptions only [openoffice]
jbampton opened a new pull request, #207: URL: https://github.com/apache/openoffice/pull/207 (no comment) -- 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
Re: [PR] docs: fix spelling in code comments [openoffice]
Pilot-Pirx merged PR #205: URL: https://github.com/apache/openoffice/pull/205 -- 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
[PR] docs: fix spelling in code comments [openoffice]
jbampton opened a new pull request, #205: URL: https://github.com/apache/openoffice/pull/205 (no comment) -- 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
Re: [PR] docs: fix spelling in code comments [openoffice]
Pilot-Pirx merged PR #204: URL: https://github.com/apache/openoffice/pull/204 -- 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
[PR] docs: fix spelling in code comments [openoffice]
jbampton opened a new pull request, #204: URL: https://github.com/apache/openoffice/pull/204 (no comment) -- 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
Re: [PR] docs: fix spelling in code comments [openoffice]
Pilot-Pirx merged PR #203: URL: https://github.com/apache/openoffice/pull/203 -- 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
Re: [PR] docs: fix spelling in code comments [openoffice]
Pilot-Pirx commented on PR #203: URL: https://github.com/apache/openoffice/pull/203#issuecomment-1957180180 Looks good to me! -- 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
[PR] docs: fix spelling in code comments [openoffice]
jbampton opened a new pull request, #203: URL: https://github.com/apache/openoffice/pull/203 (no comment) -- 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
[PR] misc: fix spelling [openoffice]
jbampton opened a new pull request, #190: URL: https://github.com/apache/openoffice/pull/190 (no comment) -- 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
Re: [PR] misc: fix spelling, fix test [openoffice]
Pilot-Pirx commented on code in PR #189: URL: https://github.com/apache/openoffice/pull/189#discussion_r1412429050 ## main/qadevOOo/tests/basic/ifc/awt/XListBox/awt_XListBox.xba: ## Review Comment: Good find! -- 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
Re: [PR] misc: fix spelling, fix test [openoffice]
Pilot-Pirx merged PR #189: URL: https://github.com/apache/openoffice/pull/189 -- 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
[PR] misc: fix spelling, fix test [openoffice]
jbampton opened a new pull request, #189: URL: https://github.com/apache/openoffice/pull/189 (no comment) -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx merged PR #188: URL: https://github.com/apache/openoffice/pull/188 -- 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
[PR] misc: fix spelling [openoffice]
jbampton opened a new pull request, #188: URL: https://github.com/apache/openoffice/pull/188 (no comment) -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx merged PR #187: URL: https://github.com/apache/openoffice/pull/187 -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx commented on PR #187: URL: https://github.com/apache/openoffice/pull/187#issuecomment-1834012356 Typos and grammar are an endless story in our code. But situation improves with every Pull Request! ;-) -- 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
[PR] misc: fix spelling [openoffice]
jbampton opened a new pull request, #187: URL: https://github.com/apache/openoffice/pull/187 (no comment) -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx commented on PR #186: URL: https://github.com/apache/openoffice/pull/186#issuecomment-1829502837 Thanks again! I added some small changes regarding German Umlaute and Unicode. -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx merged PR #186: URL: https://github.com/apache/openoffice/pull/186 -- 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
[PR] misc: fix spelling [openoffice]
jbampton opened a new pull request, #186: URL: https://github.com/apache/openoffice/pull/186 (no comment) -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx merged PR #185: URL: https://github.com/apache/openoffice/pull/185 -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx commented on code in PR #185: URL: https://github.com/apache/openoffice/pull/185#discussion_r1404883590 ## test/testcommon/source/org/openoffice/test/vcl/client/CommandCaller.java: ## Review Comment: This is a typo in one of our Java classes, see: http://opengrok.openoffice.org/search?project=trunk=%22protocal%22= I would not dare to change it... -- 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
[PR] misc: fix spelling [openoffice]
jbampton opened a new pull request, #185: URL: https://github.com/apache/openoffice/pull/185 (no comment) -- 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
Re: [PR] misc: fix spelling [openoffice-org]
dave2wave merged PR #89: URL: https://github.com/apache/openoffice-org/pull/89 -- 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
[PR] misc: fix spelling [openoffice-org]
jbampton opened a new pull request, #89: URL: https://github.com/apache/openoffice-org/pull/89 (no comment) -- 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
Re: [PR] tools/kenai2website.sh: fix spelling [openoffice-org]
dave2wave merged PR #88: URL: https://github.com/apache/openoffice-org/pull/88 -- 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
Re: [PR] tools/kenai2website.sh: fix spelling [openoffice-org]
dave2wave commented on PR #88: URL: https://github.com/apache/openoffice-org/pull/88#issuecomment-1817937929 This script is completely obsolete and was only used to move OpenOffice.org website from Oracle's Kenai CMS to the Apache CMS. We are now using a different website build. I will accept this PR and then submit a PR to delete these unused tools. -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx merged PR #184: URL: https://github.com/apache/openoffice/pull/184 -- 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
Re: [PR] misc: fix spelling [openoffice]
ardovm commented on code in PR #184: URL: https://github.com/apache/openoffice/pull/184#discussion_r1398373585 ## main/winaccessibility/source/UAccCOM/MAccessible.h: ## Review Comment: I would normally be very reluctant to rename methods as we are doing here. However, these methods do not seem to be called anywhere, so renaming them should not break anything. We should rather understand why this code is here, given that it is not used. But let's make one step at a time. -- 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
[PR] tools/kenai2website.sh: fix spelling [openoffice-org]
jbampton opened a new pull request, #88: URL: https://github.com/apache/openoffice-org/pull/88 (no comment) -- 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
Re: [PR] misc: fix spelling [openoffice]
ardovm commented on code in PR #184: URL: https://github.com/apache/openoffice/pull/184#discussion_r1395766868 ## main/offapi/com/sun/star/awt/XListBox.idl: ## Review Comment: Being it a long standing API, IMHO we should be very very motivated in order to change it. I agree that duplicating it is a feasible way to go, for the moment. -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx commented on code in PR #184: URL: https://github.com/apache/openoffice/pull/184#discussion_r1395752148 ## main/offapi/com/sun/star/awt/XListBox.idl: ## Review Comment: https://www.openoffice.org/api/docs/common/ref/com/sun/star/awt/XListBox.html#isMutipleMode -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx commented on code in PR #184: URL: https://github.com/apache/openoffice/pull/184#discussion_r1395640262 ## main/offapi/com/sun/star/awt/XListBox.idl: ## Review Comment: This is a historical typo in our API. I think we would need to address both versions and set the wrong one to "deprecated". @ardovm What do you think? -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx commented on code in PR #184: URL: https://github.com/apache/openoffice/pull/184#discussion_r1395640262 ## main/offapi/com/sun/star/awt/XListBox.idl: ## Review Comment: This is a historical typo in our API. I think we would need to address both versions and set the wrong one to "deprecated". -- 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
[PR] misc: fix spelling [openoffice]
jbampton opened a new pull request, #184: URL: https://github.com/apache/openoffice/pull/184 (no comment) -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx commented on PR #183: URL: https://github.com/apache/openoffice/pull/183#issuecomment-1812959537 Thanks again! -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx merged PR #183: URL: https://github.com/apache/openoffice/pull/183 -- 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
[PR] misc: fix spelling [openoffice]
jbampton opened a new pull request, #183: URL: https://github.com/apache/openoffice/pull/183 (no comment) -- 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
Re: [PR] misc: fix spelling [openoffice]
Pilot-Pirx merged PR #182: URL: https://github.com/apache/openoffice/pull/182 -- 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
[PR] misc: fix spelling [openoffice]
jbampton opened a new pull request, #182: URL: https://github.com/apache/openoffice/pull/182 (no comment) -- 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
Re: Check for English spelling extension updates broken?
On 10/03/22 Pedro Lino wrote: Thanks to Andrea's clear instructions we now have one more trained "staff" to do this update ;) Thank you for taking over! I'll try to get the instructions posted to some "official" shared space by this weekend. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Marcus, Am 10.03.22 um 21:12 schrieb Marcus: > Am 10.03.22 um 18:21 schrieb Matthias Seidel: >> Am 10.03.22 um 17:52 schrieb Pedro Lino: >>> >>> Yes, it was updated on March 1st >>> >>> Thanks to Andrea's clear instructions we now have one more trained >>> "staff" to do this update ;) >>> >>> I can confirm that it also works perfectly under Linux using the >>> 4.1.12 Nightly builds >> >> Good to hear! >> >>> Maybe this is a good enough motive to release 4.1.12 to all? >> >> This and some other goodies. >> >> I think we can plan the release at this point, so maybe we have >> something ready in April? > > the more important thing is what we want to have ready for 4.1.2. Just look at a nightly build and decide what is (still) missing for you... ;-) The development has been open since October last year. Matthias > But this is not a topic for this thread. ;-) > > Marcus > > > On 03/10/2022 4:10 PM Matthias Seidel wrote: Hi Pedro, all, Am 19.02.22 um 17:56 schrieb Pedro Lino: > Hi Andrea, all > >> On 02/13/2022 10:11 PM Andrea Pescetti wrote: >> I'm assuming lazy consensus on giving you permissions on the >> Extensions >> site (not the site itself, actually, but the shell access). You >> should >> post here your SourceForge username for you to be added. >> >> Once we are ready with permissions we can then get into details >> of how >> the feed works. > One week later, I assume no one opposes that I have permissions on > the Extensions shell access? > > Who can handle this so you can teach me further steps? At least on Windows I now get an update notification for the English dictionary. So it seems to work again? Many thanks for that! Looking at: https://sourceforge.net/projects/aoo-extensions/files/17102/75/dict-en-20220301_aoo.oxt/stats/timeline the download numbers increase now! Note: With the next AOO release the update notifications should also work for macOS/Linux again. Regards, Matthias > Regards, > Pedro > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Check for English spelling extension updates broken?
Am 10.03.22 um 18:21 schrieb Matthias Seidel: Am 10.03.22 um 17:52 schrieb Pedro Lino: Yes, it was updated on March 1st Thanks to Andrea's clear instructions we now have one more trained "staff" to do this update ;) I can confirm that it also works perfectly under Linux using the 4.1.12 Nightly builds Good to hear! Maybe this is a good enough motive to release 4.1.12 to all? This and some other goodies. I think we can plan the release at this point, so maybe we have something ready in April? the more important thing is what we want to have ready for 4.1.2. But this is not a topic for this thread. ;-) Marcus On 03/10/2022 4:10 PM Matthias Seidel wrote: Hi Pedro, all, Am 19.02.22 um 17:56 schrieb Pedro Lino: Hi Andrea, all On 02/13/2022 10:11 PM Andrea Pescetti wrote: I'm assuming lazy consensus on giving you permissions on the Extensions site (not the site itself, actually, but the shell access). You should post here your SourceForge username for you to be added. Once we are ready with permissions we can then get into details of how the feed works. One week later, I assume no one opposes that I have permissions on the Extensions shell access? Who can handle this so you can teach me further steps? At least on Windows I now get an update notification for the English dictionary. So it seems to work again? Many thanks for that! Looking at: https://sourceforge.net/projects/aoo-extensions/files/17102/75/dict-en-20220301_aoo.oxt/stats/timeline the download numbers increase now! Note: With the next AOO release the update notifications should also work for macOS/Linux again. Regards, Matthias Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Pedro, Am 10.03.22 um 17:52 schrieb Pedro Lino: > Hi Matthias > > Yes, it was updated on March 1st > > Thanks to Andrea's clear instructions we now have one more trained "staff" to > do this update ;) > > I can confirm that it also works perfectly under Linux using the 4.1.12 > Nightly builds Good to hear! > > Maybe this is a good enough motive to release 4.1.12 to all? This and some other goodies. I think we can plan the release at this point, so maybe we have something ready in April? Regards, Matthias > > Regards, > Pedro > >> On 03/10/2022 4:10 PM Matthias Seidel wrote: >> >> >> Hi Pedro, all, >> >> Am 19.02.22 um 17:56 schrieb Pedro Lino: >>> Hi Andrea, all >>> On 02/13/2022 10:11 PM Andrea Pescetti wrote: I'm assuming lazy consensus on giving you permissions on the Extensions site (not the site itself, actually, but the shell access). You should post here your SourceForge username for you to be added. Once we are ready with permissions we can then get into details of how the feed works. >>> One week later, I assume no one opposes that I have permissions on the >>> Extensions shell access? >>> >>> Who can handle this so you can teach me further steps? >> At least on Windows I now get an update notification for the English >> dictionary. >> >> So it seems to work again? Many thanks for that! >> >> Looking at: >> >> https://sourceforge.net/projects/aoo-extensions/files/17102/75/dict-en-20220301_aoo.oxt/stats/timeline >> >> the download numbers increase now! >> >> Note: With the next AOO release the update notifications should also >> work for macOS/Linux again. >> >> Regards, >> >> Matthias >> >>> Regards, >>> Pedro >>> >>> - >>> 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: S/MIME Cryptographic Signature
Re: Check for English spelling extension updates broken?
Hi Matthias Yes, it was updated on March 1st Thanks to Andrea's clear instructions we now have one more trained "staff" to do this update ;) I can confirm that it also works perfectly under Linux using the 4.1.12 Nightly builds Maybe this is a good enough motive to release 4.1.12 to all? Regards, Pedro > On 03/10/2022 4:10 PM Matthias Seidel wrote: > > > Hi Pedro, all, > > Am 19.02.22 um 17:56 schrieb Pedro Lino: > > Hi Andrea, all > > > >> On 02/13/2022 10:11 PM Andrea Pescetti wrote: > >> I'm assuming lazy consensus on giving you permissions on the Extensions > >> site (not the site itself, actually, but the shell access). You should > >> post here your SourceForge username for you to be added. > >> > >> Once we are ready with permissions we can then get into details of how > >> the feed works. > > One week later, I assume no one opposes that I have permissions on the > > Extensions shell access? > > > > Who can handle this so you can teach me further steps? > > At least on Windows I now get an update notification for the English > dictionary. > > So it seems to work again? Many thanks for that! > > Looking at: > > https://sourceforge.net/projects/aoo-extensions/files/17102/75/dict-en-20220301_aoo.oxt/stats/timeline > > the download numbers increase now! > > Note: With the next AOO release the update notifications should also > work for macOS/Linux again. > > Regards, > > Matthias > > > > > Regards, > > Pedro > > > > - > > 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: Check for English spelling extension updates broken?
Hi Pedro, all, Am 19.02.22 um 17:56 schrieb Pedro Lino: > Hi Andrea, all > >> On 02/13/2022 10:11 PM Andrea Pescetti wrote: >> I'm assuming lazy consensus on giving you permissions on the Extensions >> site (not the site itself, actually, but the shell access). You should >> post here your SourceForge username for you to be added. >> >> Once we are ready with permissions we can then get into details of how >> the feed works. > One week later, I assume no one opposes that I have permissions on the > Extensions shell access? > > Who can handle this so you can teach me further steps? At least on Windows I now get an update notification for the English dictionary. So it seems to work again? Many thanks for that! Looking at: https://sourceforge.net/projects/aoo-extensions/files/17102/75/dict-en-20220301_aoo.oxt/stats/timeline the download numbers increase now! Note: With the next AOO release the update notifications should also work for macOS/Linux again. Regards, Matthias > > Regards, > Pedro > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Check for English spelling extension updates broken?
On 20.02.22 00:41, Andrea Pescetti wrote: On 19/02/22 Pedro Lino wrote: no one opposes that I have permissions on the Extensions shell access? Done! You have it now. Who can handle this so you can teach me further steps? I've written extensive documentation with the aim of adding it to https://svn.apache.org/repos/infra/infrastructure/trunk/docs/services (committer-only access; it is where we store Infra documentation) but apparently it has recently been made read-only. So I can't add the filethere. Maybe infra moved to git? I'll send it to you in a personal mail now and then, if it works for you, we'll see how to upload it to a shared space. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- This is the Way! http://www.apache.org/theapacheway/index.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
On 19/02/22 Pedro Lino wrote: no one opposes that I have permissions on the Extensions shell access? Done! You have it now. Who can handle this so you can teach me further steps? I've written extensive documentation with the aim of adding it to https://svn.apache.org/repos/infra/infrastructure/trunk/docs/services (committer-only access; it is where we store Infra documentation) but apparently it has recently been made read-only. So I can't add the filethere. I'll send it to you in a personal mail now and then, if it works for you, we'll see how to upload it to a shared space. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Andrea, all > On 02/13/2022 10:11 PM Andrea Pescetti wrote: > I'm assuming lazy consensus on giving you permissions on the Extensions > site (not the site itself, actually, but the shell access). You should > post here your SourceForge username for you to be added. > > Once we are ready with permissions we can then get into details of how > the feed works. One week later, I assume no one opposes that I have permissions on the Extensions shell access? Who can handle this so you can teach me further steps? Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Andrea > On 02/13/2022 10:11 PM Andrea Pescetti wrote: > I had to try a lot of times since apparently the process changed since > the last time I checked this, but I was able to login at last and it's > still weekend! Thank you for taking some time to do this and for testing first! > So, the first steps on your side, since the site is hosted on > SourceForge, would be: > - Get a SourceForge account (and you probably already have one) > - Follow this guide > https://sourceforge.net/p/forge/documentation/SSH%20Keys/ to create and > upload your SSH key > - Test that the shell works by checking whether "ssh -t > your_user_n...@shell.sourceforge.net create" gives you a shell; then you > can simply type "exit" and logout as you won't have any projects > associated to you. Done. It is working! > I'm assuming lazy consensus on giving you permissions on the Extensions > site (not the site itself, actually, but the shell access). You should > post here your SourceForge username for you to be added. My username is plino > Once we are ready with permissions we can then get into details of how > the feed works. Thanks! Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
On 11/02/22 Pedro Lino wrote: Do you have time for this issue during this weekend? Hello Pedro, I had to try a lot of times since apparently the process changed since the last time I checked this, but I was able to login at last and it's still weekend! So, the first steps on your side, since the site is hosted on SourceForge, would be: - Get a SourceForge account (and you probably already have one) - Follow this guide https://sourceforge.net/p/forge/documentation/SSH%20Keys/ to create and upload your SSH key - Test that the shell works by checking whether "ssh -t your_user_n...@shell.sourceforge.net create" gives you a shell; then you can simply type "exit" and logout as you won't have any projects associated to you. I'm assuming lazy consensus on giving you permissions on the Extensions site (not the site itself, actually, but the shell access). You should post here your SourceForge username for you to be added. Once we are ready with permissions we can then get into details of how the feed works. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo spelling dictionaries site closed
Am 11.02.22 um 02:34 schrieb Jean-Christophe Helary: On Feb 11, 2022, at 9:36, Matthias Seidel wrote: Am 11.02.22 um 00:07 schrieb Marcus: Am 10.02.22 um 23:08 schrieb Matthias Seidel: Am 10.02.22 um 23:06 schrieb Marcus: Am 10.02.22 um 21:25 schrieb Matthias Seidel: Can we help here? I think don't understand the problem: All extensions can be accessed via the extension webpage. Is this not an option? If not, what is expected? Did you read the mail?! OK, I'm trying a thought. I don't know which content and how it was on the webpage that is now gone. So, maybe it's rubish. - Download all extensions - Extract the pure dictionary files - Put them on a new webpage - Exchange the old URL to this new one in OmegaT Can this work? BTW: When I look at the SSL certificate for "https://download.services.openoffice.org/; (yes, with HTTPS) I've the feeling that the page was not under our control. You are right! This site was probably never under our control! The invalid certificate refers to some domains (e.g. https://www.ammec.de). Does anyone know "Marco Skambraks"? @Jean-Christophe: It looks like OmegaT points to a download page that was not from the OpenOffice project. In what format does OmegaT expect the dictionaries? I installed the Windows version and it does not seem to accept OXT, which is the only format we offer. Regards, Matthias Thank you both so much for looking into this. I'm putting Aaron Madlon-Kay, who is the OmegaT project coordinator in Cc. The process was transparent to the user so it's hard to see what was hosted/expected from the site, but from reading the OmegaT code it looks like the site hosted a number of zipped .aff + .dic pairs for each language. https://sourceforge.net/p/omegat/code/ci/master/tree/src/org/omegat/core/spellchecker/DictionaryManager.java OmegaT displayed the language code, the user selected a language and OmegaT downloaded the zip, unzipped it in a dedicated folder and that was it. Marco Skambraks seems to have been working on accessibility in Linux. https://wiki.linuxfoundation.org/accessibility/charter_v1.0 https://www.knopper.net/knoppix-adriane/index-en.html https://www.suse.com/c/the-brains-behind-the-books-part-ix-meike-chabowski/ He seems to be heading this company http://www.ammec.de/ So I guess the belief that we were using an OOo repository was wrong and I'm sorry I bothered you. LibreOffice seems to have a github repository with the unzipped files at https://github.com/LibreOffice/dictionaries Either way, we'll have to implement a new solution. Thank you again for all the work you do on OOo. don't worry, it's nice to see that we could help to see the problem behind the problem. :-) Good luck that you don't have to change much for the solution. Marcus Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: Matthias, Dave, Thank you very much for looking into this. If you have an equivalent repository that’s open for external access, OmegaT will need to update its spelling dictionary installation process and inform current users that the URI currently used needs to be changed (not that people change of dictionaries that often, but just in case.) Regards, Jean-Christophe On Feb 6, 2022, at 1:05, Matthias Seidel wrote: Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us know what would be the equivalent URL? Thank you in advance. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Andrea Do you have time for this issue during this weekend? Regards, Pedro > On 02/03/2022 11:01 PM Andrea Pescetti wrote: > > > Pedro Lino wrote: > > I found some odd results. If the user has an older than 2017 version of the > > dictionary, the Extension Update dialog will report that version 2017.05.01 > > is available. If the user has the 2017.05.01 version or newer it will > > always report that "No new updates are available." > > This is not odd actually, it is quite easily explained. > > The update feed, much like the one we use for OpenOffice itself, has > information on the latest available version. If you don't update it (I > mean, "updating the update feed") for a while it will still advertise > the old version as "latest", and the logic is that if you have a newer > version than what the feed believes is the "latest" then you are > considered to not need the update. > > I'm surely available to show you all details, just please let FOSDEM > pass... but it is just round the corner, links coming in a separate mail. > > Regards, >Andrea. > > - > 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: OOo spelling dictionaries site closed
> On Feb 11, 2022, at 9:36, Matthias Seidel wrote: > > Hi Marcus, > > Am 11.02.22 um 00:07 schrieb Marcus: >> Am 10.02.22 um 23:08 schrieb Matthias Seidel: >>> Am 10.02.22 um 23:06 schrieb Marcus: >>>> Am 10.02.22 um 21:25 schrieb Matthias Seidel: >>>>> Can we help here? >>>> >>>> I think don't understand the problem: >>>> >>>> All extensions can be accessed via the extension webpage. Is this not >>>> an option? If not, what is expected? >>> >>> Did you read the mail?! >> >> OK, I'm trying a thought. I don't know which content and how it was on >> the webpage that is now gone. So, maybe it's rubish. >> >> - Download all extensions >> - Extract the pure dictionary files >> - Put them on a new webpage >> - Exchange the old URL to this new one in OmegaT >> >> Can this work? >> >> BTW: >> When I look at the SSL certificate for >> "https://download.services.openoffice.org/; (yes, with HTTPS) I've the >> feeling that the page was not under our control. > > You are right! This site was probably never under our control! > > The invalid certificate refers to some domains (e.g. > https://www.ammec.de). Does anyone know "Marco Skambraks"? > > @Jean-Christophe: > It looks like OmegaT points to a download page that was not from the > OpenOffice project. > In what format does OmegaT expect the dictionaries? I installed the > Windows version and it does not seem to accept OXT, which is the only > format we offer. > > Regards, > >Matthias Thank you both so much for looking into this. I'm putting Aaron Madlon-Kay, who is the OmegaT project coordinator in Cc. The process was transparent to the user so it's hard to see what was hosted/expected from the site, but from reading the OmegaT code it looks like the site hosted a number of zipped .aff + .dic pairs for each language. https://sourceforge.net/p/omegat/code/ci/master/tree/src/org/omegat/core/spellchecker/DictionaryManager.java OmegaT displayed the language code, the user selected a language and OmegaT downloaded the zip, unzipped it in a dedicated folder and that was it. Marco Skambraks seems to have been working on accessibility in Linux. https://wiki.linuxfoundation.org/accessibility/charter_v1.0 https://www.knopper.net/knoppix-adriane/index-en.html https://www.suse.com/c/the-brains-behind-the-books-part-ix-meike-chabowski/ He seems to be heading this company http://www.ammec.de/ So I guess the belief that we were using an OOo repository was wrong and I'm sorry I bothered you. LibreOffice seems to have a github repository with the unzipped files at https://github.com/LibreOffice/dictionaries Either way, we'll have to implement a new solution. Thank you again for all the work you do on OOo. Jean-Christophe > >> >> Marcus >> >> >> >>>>> Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: >>>>>> Matthias, Dave, >>>>>> >>>>>> Thank you very much for looking into this. >>>>>> >>>>>> If you have an equivalent repository that’s open for external >>>>>> access, OmegaT will need to update its spelling dictionary >>>>>> installation process and inform current users that the URI currently >>>>>> used needs to be changed (not that people change of dictionaries >>>>>> that often, but just in case.) >>>>>> >>>>>> Regards, >>>>>> >>>>>> Jean-Christophe >>>>>> >>>>>>> On Feb 6, 2022, at 1:05, Matthias Seidel >>>>>>> wrote: >>>>>>> >>>>>>> Hi Jean-Christophe, >>>>>>> >>>>>>> Thanks for asking here! It is a much better place than Twitter... >>>>>>> ;-) >>>>>>> >>>>>>> I am wondering if there was a redirection dumped when we switched >>>>>>> the >>>>>>> build system for the homepage? >>>>>>> >>>>>>> http://download.services.openoffice.org/files/contrib/dictionaries/ >>>>>>> seems to be long gone... >>>>>>> >>>>>>> @Dave: Do you have more insight? >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Matthias >>>>>>> >>>>>>> Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: >>>>>>>&
Re: OOo spelling dictionaries site closed
Hi Marcus, Am 11.02.22 um 00:07 schrieb Marcus: > Am 10.02.22 um 23:08 schrieb Matthias Seidel: >> Am 10.02.22 um 23:06 schrieb Marcus: >>> Am 10.02.22 um 21:25 schrieb Matthias Seidel: >>>> Can we help here? >>> >>> I think don't understand the problem: >>> >>> All extensions can be accessed via the extension webpage. Is this not >>> an option? If not, what is expected? >> >> Did you read the mail?! > > OK, I'm trying a thought. I don't know which content and how it was on > the webpage that is now gone. So, maybe it's rubish. > > - Download all extensions > - Extract the pure dictionary files > - Put them on a new webpage > - Exchange the old URL to this new one in OmegaT > > Can this work? > > BTW: > When I look at the SSL certificate for > "https://download.services.openoffice.org/; (yes, with HTTPS) I've the > feeling that the page was not under our control. You are right! This site was probably never under our control! The invalid certificate refers to some domains (e.g. https://www.ammec.de). Does anyone know "Marco Skambraks"? @Jean-Christophe: It looks like OmegaT points to a download page that was not from the OpenOffice project. In what format does OmegaT expect the dictionaries? I installed the Windows version and it does not seem to accept OXT, which is the only format we offer. Regards, Matthias > > Marcus > > > >>>> Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: >>>>> Matthias, Dave, >>>>> >>>>> Thank you very much for looking into this. >>>>> >>>>> If you have an equivalent repository that’s open for external >>>>> access, OmegaT will need to update its spelling dictionary >>>>> installation process and inform current users that the URI currently >>>>> used needs to be changed (not that people change of dictionaries >>>>> that often, but just in case.) >>>>> >>>>> Regards, >>>>> >>>>> Jean-Christophe >>>>> >>>>>> On Feb 6, 2022, at 1:05, Matthias Seidel >>>>>> wrote: >>>>>> >>>>>> Hi Jean-Christophe, >>>>>> >>>>>> Thanks for asking here! It is a much better place than Twitter... >>>>>> ;-) >>>>>> >>>>>> I am wondering if there was a redirection dumped when we switched >>>>>> the >>>>>> build system for the homepage? >>>>>> >>>>>> http://download.services.openoffice.org/files/contrib/dictionaries/ >>>>>> seems to be long gone... >>>>>> >>>>>> @Dave: Do you have more insight? >>>>>> >>>>>> Regards, >>>>>> >>>>>> Matthias >>>>>> >>>>>> Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: >>>>>>> Hello Devs, >>>>>>> >>>>>>> First, thank you for your hard work on OOo. I used to help with >>>>>>> localization when OOo was still managed by Sun. >>>>>>> >>>>>>> I am (still) currently helping with OmegaT, the free >>>>>>> ‘computer-aided-translation’ tool and we use OOo’s spelling >>>>>>> dictionaries for the spell-checking functionality. >>>>>>> >>>>>>> The site that’s hard linked in the code is: >>>>>>> http://download.services.openoffice.org/files/contrib/dictionaries/ >>>>>>> >>>>>>> But it seems to be definitely down, even though I seem to remember >>>>>>> that it was working a few weeks ago. >>>>>>> >>>>>>> OmegaT needs the dictionary files and won’t be able to work with >>>>>>> the OOo extensions. >>>>>>> >>>>>>> I understand that such direct access could cause undue load on >>>>>>> your servers, and that’s maybe the reason why you took it >>>>>>> off-line, but if that’s not the case we would love to be able to >>>>>>> keep using your repository, if you still have one. In which case, >>>>>>> would you mind letting us know what would be the equivalent URL? >>>>>>> >>>>>>> Thank you in advance. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: OOo spelling dictionaries site closed
Am 10.02.22 um 23:08 schrieb Matthias Seidel: Am 10.02.22 um 23:06 schrieb Marcus: Am 10.02.22 um 21:25 schrieb Matthias Seidel: Can we help here? I think don't understand the problem: All extensions can be accessed via the extension webpage. Is this not an option? If not, what is expected? Did you read the mail?! OK, I'm trying a thought. I don't know which content and how it was on the webpage that is now gone. So, maybe it's rubish. - Download all extensions - Extract the pure dictionary files - Put them on a new webpage - Exchange the old URL to this new one in OmegaT Can this work? BTW: When I look at the SSL certificate for "https://download.services.openoffice.org/; (yes, with HTTPS) I've the feeling that the page was not under our control. Marcus Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: Matthias, Dave, Thank you very much for looking into this. If you have an equivalent repository that’s open for external access, OmegaT will need to update its spelling dictionary installation process and inform current users that the URI currently used needs to be changed (not that people change of dictionaries that often, but just in case.) Regards, Jean-Christophe On Feb 6, 2022, at 1:05, Matthias Seidel wrote: Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us know what would be the equivalent URL? Thank you in advance. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo spelling dictionaries site closed
Hi Marcus, Am 10.02.22 um 23:06 schrieb Marcus: > Am 10.02.22 um 21:25 schrieb Matthias Seidel: >> Can we help here? > > I think don't understand the problem: > > All extensions can be accessed via the extension webpage. Is this not > an option? If not, what is expected? Did you read the mail?! Matthias > > Marcus > > > >> Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: >>> Matthias, Dave, >>> >>> Thank you very much for looking into this. >>> >>> If you have an equivalent repository that’s open for external >>> access, OmegaT will need to update its spelling dictionary >>> installation process and inform current users that the URI currently >>> used needs to be changed (not that people change of dictionaries >>> that often, but just in case.) >>> >>> Regards, >>> >>> Jean-Christophe >>> >>>> On Feb 6, 2022, at 1:05, Matthias Seidel >>>> wrote: >>>> >>>> Hi Jean-Christophe, >>>> >>>> Thanks for asking here! It is a much better place than Twitter... ;-) >>>> >>>> I am wondering if there was a redirection dumped when we switched the >>>> build system for the homepage? >>>> >>>> http://download.services.openoffice.org/files/contrib/dictionaries/ >>>> seems to be long gone... >>>> >>>> @Dave: Do you have more insight? >>>> >>>> Regards, >>>> >>>> Matthias >>>> >>>> Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: >>>>> Hello Devs, >>>>> >>>>> First, thank you for your hard work on OOo. I used to help with >>>>> localization when OOo was still managed by Sun. >>>>> >>>>> I am (still) currently helping with OmegaT, the free >>>>> ‘computer-aided-translation’ tool and we use OOo’s spelling >>>>> dictionaries for the spell-checking functionality. >>>>> >>>>> The site that’s hard linked in the code is: >>>>> http://download.services.openoffice.org/files/contrib/dictionaries/ >>>>> >>>>> But it seems to be definitely down, even though I seem to remember >>>>> that it was working a few weeks ago. >>>>> >>>>> OmegaT needs the dictionary files and won’t be able to work with >>>>> the OOo extensions. >>>>> >>>>> I understand that such direct access could cause undue load on >>>>> your servers, and that’s maybe the reason why you took it >>>>> off-line, but if that’s not the case we would love to be able to >>>>> keep using your repository, if you still have one. In which case, >>>>> would you mind letting us know what would be the equivalent URL? >>>>> >>>>> Thank you in advance. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: OOo spelling dictionaries site closed
Am 10.02.22 um 21:25 schrieb Matthias Seidel: Can we help here? I think don't understand the problem: All extensions can be accessed via the extension webpage. Is this not an option? If not, what is expected? Marcus Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: Matthias, Dave, Thank you very much for looking into this. If you have an equivalent repository that’s open for external access, OmegaT will need to update its spelling dictionary installation process and inform current users that the URI currently used needs to be changed (not that people change of dictionaries that often, but just in case.) Regards, Jean-Christophe On Feb 6, 2022, at 1:05, Matthias Seidel wrote: Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us know what would be the equivalent URL? Thank you in advance. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo spelling dictionaries site closed
Hi all, Can we help here? Regards, Matthias Am 06.02.22 um 08:41 schrieb Jean-Christophe Helary: > Matthias, Dave, > > Thank you very much for looking into this. > > If you have an equivalent repository that’s open for external access, OmegaT > will need to update its spelling dictionary installation process and inform > current users that the URI currently used needs to be changed (not that > people change of dictionaries that often, but just in case.) > > Regards, > > Jean-Christophe > >> On Feb 6, 2022, at 1:05, Matthias Seidel wrote: >> >> Hi Jean-Christophe, >> >> Thanks for asking here! It is a much better place than Twitter... ;-) >> >> I am wondering if there was a redirection dumped when we switched the >> build system for the homepage? >> >> http://download.services.openoffice.org/files/contrib/dictionaries/ >> seems to be long gone... >> >> @Dave: Do you have more insight? >> >> Regards, >> >>Matthias >> >> Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: >>> Hello Devs, >>> >>> First, thank you for your hard work on OOo. I used to help with >>> localization when OOo was still managed by Sun. >>> >>> I am (still) currently helping with OmegaT, the free >>> ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries >>> for the spell-checking functionality. >>> >>> The site that’s hard linked in the code is: >>> http://download.services.openoffice.org/files/contrib/dictionaries/ >>> >>> But it seems to be definitely down, even though I seem to remember that it >>> was working a few weeks ago. >>> >>> OmegaT needs the dictionary files and won’t be able to work with the OOo >>> extensions. >>> >>> I understand that such direct access could cause undue load on your >>> servers, and that’s maybe the reason why you took it off-line, but if >>> that’s not the case we would love to be able to keep using your repository, >>> if you still have one. In which case, would you mind letting us know what >>> would be the equivalent URL? >>> >>> Thank you in advance. >>> smime.p7s Description: S/MIME Cryptographic Signature
Re: OOo spelling dictionaries site closed
Matthias, Dave, Thank you very much for looking into this. If you have an equivalent repository that’s open for external access, OmegaT will need to update its spelling dictionary installation process and inform current users that the URI currently used needs to be changed (not that people change of dictionaries that often, but just in case.) Regards, Jean-Christophe > On Feb 6, 2022, at 1:05, Matthias Seidel wrote: > > Hi Jean-Christophe, > > Thanks for asking here! It is a much better place than Twitter... ;-) > > I am wondering if there was a redirection dumped when we switched the > build system for the homepage? > > http://download.services.openoffice.org/files/contrib/dictionaries/ > seems to be long gone... > > @Dave: Do you have more insight? > > Regards, > >Matthias > > Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: >> Hello Devs, >> >> First, thank you for your hard work on OOo. I used to help with localization >> when OOo was still managed by Sun. >> >> I am (still) currently helping with OmegaT, the free >> ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for >> the spell-checking functionality. >> >> The site that’s hard linked in the code is: >> http://download.services.openoffice.org/files/contrib/dictionaries/ >> >> But it seems to be definitely down, even though I seem to remember that it >> was working a few weeks ago. >> >> OmegaT needs the dictionary files and won’t be able to work with the OOo >> extensions. >> >> I understand that such direct access could cause undue load on your servers, >> and that’s maybe the reason why you took it off-line, but if that’s not the >> case we would love to be able to keep using your repository, if you still >> have one. In which case, would you mind letting us know what would be the >> equivalent URL? >> >> Thank you in advance. >> > -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OOo spelling dictionaries site closed
Hi Jean-Christophe, Thanks for asking here! It is a much better place than Twitter... ;-) I am wondering if there was a redirection dumped when we switched the build system for the homepage? http://download.services.openoffice.org/files/contrib/dictionaries/ seems to be long gone... @Dave: Do you have more insight? Regards, Matthias Am 05.02.22 um 05:03 schrieb Jean-Christophe Helary: > Hello Devs, > > First, thank you for your hard work on OOo. I used to help with localization > when OOo was still managed by Sun. > > I am (still) currently helping with OmegaT, the free > ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for > the spell-checking functionality. > > The site that’s hard linked in the code is: > http://download.services.openoffice.org/files/contrib/dictionaries/ > > But it seems to be definitely down, even though I seem to remember that it > was working a few weeks ago. > > OmegaT needs the dictionary files and won’t be able to work with the OOo > extensions. > > I understand that such direct access could cause undue load on your servers, > and that’s maybe the reason why you took it off-line, but if that’s not the > case we would love to be able to keep using your repository, if you still > have one. In which case, would you mind letting us know what would be the > equivalent URL? > > Thank you in advance. > smime.p7s Description: S/MIME Cryptographic Signature
OOo spelling dictionaries site closed
Hello Devs, First, thank you for your hard work on OOo. I used to help with localization when OOo was still managed by Sun. I am (still) currently helping with OmegaT, the free ‘computer-aided-translation’ tool and we use OOo’s spelling dictionaries for the spell-checking functionality. The site that’s hard linked in the code is: http://download.services.openoffice.org/files/contrib/dictionaries/ But it seems to be definitely down, even though I seem to remember that it was working a few weeks ago. OmegaT needs the dictionary files and won’t be able to work with the OOo extensions. I understand that such direct access could cause undue load on your servers, and that’s maybe the reason why you took it off-line, but if that’s not the case we would love to be able to keep using your repository, if you still have one. In which case, would you mind letting us know what would be the equivalent URL? Thank you in advance. -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Andrea Thank you for the fast reply! > On 02/03/2022 11:01 PM Andrea Pescetti wrote: > The update feed, much like the one we use for OpenOffice itself, has > information on the latest available version. If you don't update it (I > mean, "updating the update feed") for a while it will still advertise > the old version as "latest", and the logic is that if you have a newer > version than what the feed believes is the "latest" then you are > considered to not need the update. Which means it has not been updated since 2017 and nobody noticed because it is automagically updated with each new install :) > I'm surely available to show you all details, just please let FOSDEM > pass... but it is just round the corner, links coming in a separate mail. Of course! Unfortunately I will not be able to join you guys on Saturday since I will be traveling. Maybe on Sunday... All the best, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Pedro Lino wrote: I found some odd results. If the user has an older than 2017 version of the dictionary, the Extension Update dialog will report that version 2017.05.01 is available. If the user has the 2017.05.01 version or newer it will always report that "No new updates are available." This is not odd actually, it is quite easily explained. The update feed, much like the one we use for OpenOffice itself, has information on the latest available version. If you don't update it (I mean, "updating the update feed") for a while it will still advertise the old version as "latest", and the logic is that if you have a newer version than what the feed believes is the "latest" then you are considered to not need the update. I'm surely available to show you all details, just please let FOSDEM pass... but it is just round the corner, links coming in a separate mail. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Returning to this subject: I found some odd results. If the user has an older than 2017 version of the dictionary, the Extension Update dialog will report that version 2017.05.01 is available. If the user has the 2017.05.01 version or newer it will always report that "No new updates are available." I hope Andrea has some ideas on this. Regards, Pedro > On 02/03/2022 11:04 AM Matthias Seidel wrote: > > > Hi Pedro, all, > > Bumping this one up: > > Is it possible to re-activate the update feed for SourceForge? > > Regards, > > Matthias > > Am 15.03.21 um 21:12 schrieb Pedro Lino: > > Hi again Andrea > > > > Marco has released two versions since the one included in AOO 4.1.9 > > > > Can you update this or teach us how to do it? > > > > Thanks! > > > > Regards, > > Pedro > > > > > >> On 03/10/2021 4:42 PM Matthias Seidel wrote: > >> > >> > >> Hi Andrea, > >> > >> When would be the best time for an update? > >> > >> Regards, > >> > >> Matthias > >> > >> Am 22.01.21 um 00:39 schrieb Andrea Pescetti: > >>> On 21/01/2021 Pedro Lino wrote: > > Please let me know if it works; if it does, I will then revert it and > > republish only after 4.1.9 is out ... > It is fixed indeed (although I get 2 notifications for that > extension, but one problem at a time!). Thanks! > >>> OK, thank you for checking. I've now reverted the fix and we'll go > >>> live with a more complete version when people will have upgraded to > >>> 4.1.9. > >>> > if an extension author submits a new version does s/he have > permission to do that manual update or s/he has to request someone to > do it? > >>> Extensions authors cannot trigger the update. Site moderators can (and > >>> probably should) do it once in a while as a routine task. The worst > >>> period is for sure when you are close to a release and the few weeks > >>> after a release, since before the release you might be downloading a > >>> newer version than the one coming with the release (like: if a bundled > >>> extension was updated yesterday, 4.1.9 would contain an older > >>> extension version than the one people would download today). > >>> > >>> But when we are not in proximity of a release, we can trigger the > >>> update perhaps once a month; fact is, the process I could find is > >>> still cumbersome and requires shell commands to be run, so until we > >>> streamline it it won't be run very frequently. And I would be against > >>> fully automating it as some anti-spam checks might be needed, even > >>> though spam is a problem on the Templates site much more than the > >>> Extensions site. > >>> > >>> Regards, > >>> Andrea. > >>> > >>> - > >>> 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: Check for English spelling extension updates broken?
Hi Matthias > On 02/03/2022 11:04 AM Matthias Seidel wrote: > Is it possible to re-activate the update feed for SourceForge? I'm available to do this if someone helps me. Andrea? Regards, Pedro > Am 15.03.21 um 21:12 schrieb Pedro Lino: > > Hi again Andrea > > > > Marco has released two versions since the one included in AOO 4.1.9 > > > > Can you update this or teach us how to do it? > > > > Thanks! > > > > Regards, > > Pedro > > > > > >> On 03/10/2021 4:42 PM Matthias Seidel wrote: > >> > >> > >> Hi Andrea, > >> > >> When would be the best time for an update? > >> > >> Regards, > >> > >> Matthias > >> > >> Am 22.01.21 um 00:39 schrieb Andrea Pescetti: > >>> On 21/01/2021 Pedro Lino wrote: > > Please let me know if it works; if it does, I will then revert it and > > republish only after 4.1.9 is out ... > It is fixed indeed (although I get 2 notifications for that > extension, but one problem at a time!). Thanks! > >>> OK, thank you for checking. I've now reverted the fix and we'll go > >>> live with a more complete version when people will have upgraded to > >>> 4.1.9. > >>> > if an extension author submits a new version does s/he have > permission to do that manual update or s/he has to request someone to > do it? > >>> Extensions authors cannot trigger the update. Site moderators can (and > >>> probably should) do it once in a while as a routine task. The worst > >>> period is for sure when you are close to a release and the few weeks > >>> after a release, since before the release you might be downloading a > >>> newer version than the one coming with the release (like: if a bundled > >>> extension was updated yesterday, 4.1.9 would contain an older > >>> extension version than the one people would download today). > >>> > >>> But when we are not in proximity of a release, we can trigger the > >>> update perhaps once a month; fact is, the process I could find is > >>> still cumbersome and requires shell commands to be run, so until we > >>> streamline it it won't be run very frequently. And I would be against > >>> fully automating it as some anti-spam checks might be needed, even > >>> though spam is a problem on the Templates site much more than the > >>> Extensions site. > >>> > >>> Regards, > >>> Andrea. > >>> > >>> - > >>> 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: Check for English spelling extension updates broken?
Hi Pedro, all, Bumping this one up: Is it possible to re-activate the update feed for SourceForge? Regards, Matthias Am 15.03.21 um 21:12 schrieb Pedro Lino: > Hi again Andrea > > Marco has released two versions since the one included in AOO 4.1.9 > > Can you update this or teach us how to do it? > > Thanks! > > Regards, > Pedro > > >> On 03/10/2021 4:42 PM Matthias Seidel wrote: >> >> >> Hi Andrea, >> >> When would be the best time for an update? >> >> Regards, >> >> Matthias >> >> Am 22.01.21 um 00:39 schrieb Andrea Pescetti: >>> On 21/01/2021 Pedro Lino wrote: > Please let me know if it works; if it does, I will then revert it and > republish only after 4.1.9 is out ... It is fixed indeed (although I get 2 notifications for that extension, but one problem at a time!). Thanks! >>> OK, thank you for checking. I've now reverted the fix and we'll go >>> live with a more complete version when people will have upgraded to >>> 4.1.9. >>> if an extension author submits a new version does s/he have permission to do that manual update or s/he has to request someone to do it? >>> Extensions authors cannot trigger the update. Site moderators can (and >>> probably should) do it once in a while as a routine task. The worst >>> period is for sure when you are close to a release and the few weeks >>> after a release, since before the release you might be downloading a >>> newer version than the one coming with the release (like: if a bundled >>> extension was updated yesterday, 4.1.9 would contain an older >>> extension version than the one people would download today). >>> >>> But when we are not in proximity of a release, we can trigger the >>> update perhaps once a month; fact is, the process I could find is >>> still cumbersome and requires shell commands to be run, so until we >>> streamline it it won't be run very frequently. And I would be against >>> fully automating it as some anti-spam checks might be needed, even >>> though spam is a problem on the Templates site much more than the >>> Extensions site. >>> >>> Regards, >>> Andrea. >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>> smime.p7s Description: S/MIME Cryptographic Signature
Re: Check for English spelling extension updates broken?
Hi again Andrea Marco has released two versions since the one included in AOO 4.1.9 Can you update this or teach us how to do it? Thanks! Regards, Pedro > On 03/10/2021 4:42 PM Matthias Seidel wrote: > > > Hi Andrea, > > When would be the best time for an update? > > Regards, > > Matthias > > Am 22.01.21 um 00:39 schrieb Andrea Pescetti: > > On 21/01/2021 Pedro Lino wrote: > >>> Please let me know if it works; if it does, I will then revert it and > >>> republish only after 4.1.9 is out ... > >> It is fixed indeed (although I get 2 notifications for that > >> extension, but one problem at a time!). Thanks! > > > > OK, thank you for checking. I've now reverted the fix and we'll go > > live with a more complete version when people will have upgraded to > > 4.1.9. > > > >> if an extension author submits a new version does s/he have > >> permission to do that manual update or s/he has to request someone to > >> do it? > > > > Extensions authors cannot trigger the update. Site moderators can (and > > probably should) do it once in a while as a routine task. The worst > > period is for sure when you are close to a release and the few weeks > > after a release, since before the release you might be downloading a > > newer version than the one coming with the release (like: if a bundled > > extension was updated yesterday, 4.1.9 would contain an older > > extension version than the one people would download today). > > > > But when we are not in proximity of a release, we can trigger the > > update perhaps once a month; fact is, the process I could find is > > still cumbersome and requires shell commands to be run, so until we > > streamline it it won't be run very frequently. And I would be against > > fully automating it as some anti-spam checks might be needed, even > > though spam is a problem on the Templates site much more than the > > Extensions site. > > > > Regards, > > Andrea. > > > > - > > 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: Check for English spelling extension updates broken?
Hi Andrea, When would be the best time for an update? Regards, Matthias Am 22.01.21 um 00:39 schrieb Andrea Pescetti: > On 21/01/2021 Pedro Lino wrote: >>> Please let me know if it works; if it does, I will then revert it and >>> republish only after 4.1.9 is out ... >> It is fixed indeed (although I get 2 notifications for that >> extension, but one problem at a time!). Thanks! > > OK, thank you for checking. I've now reverted the fix and we'll go > live with a more complete version when people will have upgraded to > 4.1.9. > >> if an extension author submits a new version does s/he have >> permission to do that manual update or s/he has to request someone to >> do it? > > Extensions authors cannot trigger the update. Site moderators can (and > probably should) do it once in a while as a routine task. The worst > period is for sure when you are close to a release and the few weeks > after a release, since before the release you might be downloading a > newer version than the one coming with the release (like: if a bundled > extension was updated yesterday, 4.1.9 would contain an older > extension version than the one people would download today). > > But when we are not in proximity of a release, we can trigger the > update perhaps once a month; fact is, the process I could find is > still cumbersome and requires shell commands to be run, so until we > streamline it it won't be run very frequently. And I would be against > fully automating it as some anti-spam checks might be needed, even > though spam is a problem on the Templates site much more than the > Extensions site. > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > smime.p7s Description: S/MIME Cryptographic Signature
Re: Check for English spelling extension updates broken?
Hi Andrea > On 01/21/2021 11:39 PM Andrea Pescetti wrote: > OK, thank you for checking. I've now reverted the fix and we'll go live > with a more complete version when people will have upgraded to 4.1.9. Agreed. Thank you! > But when we are not in proximity of a release, we can trigger the update > perhaps once a month; fact is, the process I could find is still > cumbersome and requires shell commands to be run, so until we streamline > it it won't be run very frequently. And I would be against fully > automating it as some anti-spam checks might be needed, even though spam > is a problem on the Templates site much more than the Extensions site. If/when the process is streamlined I can volunteer to run it on a monthly/2 months basis (except before and after a new AOO release). It should be an improvement compared to 3 years :) Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
On 21/01/2021 Pedro Lino wrote: Please let me know if it works; if it does, I will then revert it and republish only after 4.1.9 is out ... It is fixed indeed (although I get 2 notifications for that extension, but one problem at a time!). Thanks! OK, thank you for checking. I've now reverted the fix and we'll go live with a more complete version when people will have upgraded to 4.1.9. if an extension author submits a new version does s/he have permission to do that manual update or s/he has to request someone to do it? Extensions authors cannot trigger the update. Site moderators can (and probably should) do it once in a while as a routine task. The worst period is for sure when you are close to a release and the few weeks after a release, since before the release you might be downloading a newer version than the one coming with the release (like: if a bundled extension was updated yesterday, 4.1.9 would contain an older extension version than the one people would download today). But when we are not in proximity of a release, we can trigger the update perhaps once a month; fact is, the process I could find is still cumbersome and requires shell commands to be run, so until we streamline it it won't be run very frequently. And I would be against fully automating it as some anti-spam checks might be needed, even though spam is a problem on the Templates site much more than the Extensions site. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Andrea > On 01/21/2021 8:04 PM Andrea Pescetti wrote: > I believe it's fixed now (limited to the specific case of the English > dictionary; I had to find some workarounds so I enabled only that > extension for testing). > Please let me know if it works; if it does, I will then revert it and > republish only after 4.1.9 is out (or users will be confused by the > double update; this is exactly the reason for the update to be manual by > the way). It is fixed indeed (although I get 2 notifications for that extension, but one problem at a time!). Thanks! It makes sense that it is manually to prevent double notifications but if an extension author submits a new version does s/he have permission to do that manual update or s/he has to request someone to do it? Is that the part that needs to be documented? Thank you for solving this issue! Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Am 21.01.21 um 21:04 schrieb Andrea Pescetti: On 20/01/2021 Andrea Pescetti wrote: I think we can fix it. Let me give it a try tomorrow. I believe it's fixed now (limited to the specific case of the English dictionary; I had to find some workarounds so I enabled only that extension for testing). Please let me know if it works; if it does, I will then revert it and republish only after 4.1.9 is out (or users will be confused by the double update; this is exactly the reason for the update to be manual by the way). [...] To check: in OpenOffice, check for Extensions Updates (not OpenOffice updates) and see whether this prompts you with an updated English dictionary to be downloaded (with a web browser, not within OpenOffice) and installed. wow \o/ , it's working again. :-) My English and German dictionaries want to be updated. A click on the [Install] button opens 2 tabs in my browser to the extension website for both dictionaries. Thanks for analysing this old problem. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
On 20/01/2021 Andrea Pescetti wrote: I think we can fix it. Let me give it a try tomorrow. I believe it's fixed now (limited to the specific case of the English dictionary; I had to find some workarounds so I enabled only that extension for testing). Please let me know if it works; if it does, I will then revert it and republish only after 4.1.9 is out (or users will be confused by the double update; this is exactly the reason for the update to be manual by the way). Before: $ curl -s https://extensions.openoffice.org/ExtensionUpdateService/check.Update | grep -A1 org.openoffice.en.hunspell.dictionaries After: $ curl -s https://extensions.openoffice.org/ExtensionUpdateService/check.Update | grep -A1 org.openoffice.en.hunspell.dictionaries To check: in OpenOffice, check for Extensions Updates (not OpenOffice updates) and see whether this prompts you with an updated English dictionary to be downloaded (with a web browser, not within OpenOffice) and installed. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Andrea > On 01/20/2021 10:23 PM Andrea Pescetti wrote: > I think we can fix it. Let me give it a try tomorrow. Excellent! Thanks! > What I can do tomorrow is: I can check whether our (site moderator) > access is enough to push the updated feed live; and I'll document it > internally in case. Thank you again! Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
On 20/01/2021 Matthias Seidel wrote: Am 20.01.21 um 00:47 schrieb Pedro Lino: On 01/19/2021 5:38 PM Matthias Seidel wrote: In this case it looks for the feed on the SourceForge server. My guess is, that these feeds are not generated anymore. I don't know if this was an automatic or a manual process. Generation is automated, but go-live is manual. And this seems to have been forgotten... you will be notified to update to 2017.05.01 ... That's the real issue. The feed (at least for the English dictionary) is outdated. I think we can fix it. Let me give it a try tomorrow. The relevant feed is described here: https://wiki.openoffice.org/wiki/Extensions/website/update_feed but the URL in our case is slightly different; you find it in your local versionrc (version.ini on Windows?) file and it should point (after redirection) to https://extensions.openoffice.org/ExtensionUpdateService/check.Update As you can verify by downloading it, the feed is there but it was last updated in June 2017 indeed. What I can do tomorrow is: I can check whether our (site moderator) access is enough to push the updated feed live; and I'll document it internally in case. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Pedro, Am 20.01.21 um 00:47 schrieb Pedro Lino: > Hi Matthias, Marco, all > > >> On 01/19/2021 5:38 PM Matthias Seidel wrote: >> >> AOO is looking for an "update feed", quite similar to the release >> updates. >> (Release update feeds are generated by hand after every release) >> >> In this case it looks for the feed on the SourceForge server. My guess >> is, that these feeds are not generated anymore. >> I don't know if this was an automatic or a manual process. >> > Sourceforge seems to work. If you install the 2017.03.01 version or any older > from > https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice > you will be notified to update to 2017.05.01 (I noticed this because on my > old XP laptop I still had version 2015.10.01 and was notified about updates > after installing 4.1.9RC1) Yes, requesting the feed itself should work again since AOO 4.1.8. > So the last notification is from version 2017.05.01 and nobody noticed > because 2017 was probably when the Update function was broken. That's the real issue. The feed (at least for the English dictionary) is outdated. I think there was a Drupal update maybe in 2017? This would be discussed with SourceForge. Personally I have no time to do so... Regards, Matthias > > I hope this helps fixing the issue ;) > > Regards, > Pedro > smime.p7s Description: S/MIME Cryptographic Signature
Re: Check for English spelling extension updates broken?
Hi Matthias, Marco, all > On 01/19/2021 5:38 PM Matthias Seidel wrote: > > AOO is looking for an "update feed", quite similar to the release updates. > (Release update feeds are generated by hand after every release) > > In this case it looks for the feed on the SourceForge server. My guess > is, that these feeds are not generated anymore. > I don't know if this was an automatic or a manual process. > Sourceforge seems to work. If you install the 2017.03.01 version or any older from https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice you will be notified to update to 2017.05.01 (I noticed this because on my old XP laptop I still had version 2015.10.01 and was notified about updates after installing 4.1.9RC1) So the last notification is from version 2017.05.01 and nobody noticed because 2017 was probably when the Update function was broken. I hope this helps fixing the issue ;) Regards, Pedro
Re: Check for English spelling extension updates broken?
Hi, My understanding is: AOO is looking for an "update feed", quite similar to the release updates. (Release update feeds are generated by hand after every release) In this case it looks for the feed on the SourceForge server. My guess is, that these feeds are not generated anymore. I don't know if this was an automatic or a manual process. Regards, Matthias Am 19.01.21 um 14:15 schrieb Marco A.G. Pinto: > I am the maintainer, but I don't remember making any changes that > could be causing this. > > All I change are the dictionary files, version number of the extension > and the release notes. > > Not sure why it happens. > > On 19/01/2021 12:04, Pedro Lino wrote: >> Hi all >> >> I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the >> English spelling extension I have installed is from 2020.07.01 but Checking >> for updates does not report any new version. >> This is particularly odd because this extension is updated monthly >> (including in January 2021). >> >> Installing an older version of another extension does detect new versions so >> this not a problem with Checking for Extension Updates but seems specific >> for this extension (and maybe for others too). >> >> Can someone confirm this problem? >> >> Just to be clear: this is not a regression or an obstacle for the release of >> 4.1.9 RC1, the problem also occurs in 4.1.8 >> >> Thanks! >> Pedro >> > > -- smime.p7s Description: S/MIME Cryptographic Signature
Re: Check for English spelling extension updates broken?
Hi Czeslaw > On 01/19/2021 1:14 PM Czesław Wolański wrote: > 4.1.9 RC1, Windows 7 > English spelling extension: > I can confirm your observation - checking for update of any version > (2020.07.01 - 2020.12.01) > results in a message "No new updates are available.". Thank you for confirming! There is also no information on new versions available when using AOO version 4.1.8 under Ubuntu 20.04 (which included the English spelling extension from 2020.10.01) which means it is also not a Windows problem, but it is specific to this extension. Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Marco This may be broken for a long time. Please remember that checking for updates (extensions or program) was broken for years. It is only since 4.1.8 that it is working again. But this is only a problem for people who need the English dictionary but do not use the Windows English installer (which is very likely a minority...) Regards, Pedro > On 01/19/2021 1:15 PM Marco A.G. Pinto wrote: > > > I am the maintainer, but I don't remember making any changes that could > be causing this. > > All I change are the dictionary files, version number of the extension > and the release notes. > > Not sure why it happens. > > On 19/01/2021 12:04, Pedro Lino wrote: > > > > > > Hi all > > > > I am testing version 4.1.9 RC1 under Windows 7 and I just noticed > > that the English spelling extension I have installed is from 2020.07.01 but > > Checking for updates does not report any new version. > > This is particularly odd because this extension is updated monthly > > (including in January 2021). > > > > Installing an older version of another extension does detect new > > versions so this not a problem with Checking for Extension Updates but > > seems specific for this extension (and maybe for others too). > > > > Can someone confirm this problem? > > > > Just to be clear: this is not a regression or an obstacle for the > > release of 4.1.9 RC1, the problem also occurs in 4.1.8 > > > > Thanks! > > Pedro > > > > > > > -- >
Re: Check for English spelling extension updates broken?
I am the maintainer, but I don't remember making any changes that could be causing this. All I change are the dictionary files, version number of the extension and the release notes. Not sure why it happens. On 19/01/2021 12:04, Pedro Lino wrote: Hi all I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the English spelling extension I have installed is from 2020.07.01 but Checking for updates does not report any new version. This is particularly odd because this extension is updated monthly (including in January 2021). Installing an older version of another extension does detect new versions so this not a problem with Checking for Extension Updates but seems specific for this extension (and maybe for others too). Can someone confirm this problem? Just to be clear: this is not a regression or an obstacle for the release of 4.1.9 RC1, the problem also occurs in 4.1.8 Thanks! Pedro -- OpenPGP_signature Description: OpenPGP digital signature
Re: Check for English spelling extension updates broken?
Hi Pedro, 4.1.9 RC1, Windows 7 English spelling extension: I can confirm your observation - checking for update of any version (2020.07.01 - 2020.12.01) results in a message "No new updates are available.". Regards, Czesław Am Di., 19. Jan. 2021 um 13:04 Uhr schrieb Pedro Lino : > Hi all > > I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the > English spelling extension I have installed is from 2020.07.01 but Checking > for updates does not report any new version. > This is particularly odd because this extension is updated monthly > (including in January 2021). > > Installing an older version of another extension does detect new versions > so this not a problem with Checking for Extension Updates but seems > specific for this extension (and maybe for others too). > > Can someone confirm this problem? > > Just to be clear: this is not a regression or an obstacle for the release > of 4.1.9 RC1, the problem also occurs in 4.1.8 > > Thanks! > Pedro >
Check for English spelling extension updates broken?
Hi all I am testing version 4.1.9 RC1 under Windows 7 and I just noticed that the English spelling extension I have installed is from 2020.07.01 but Checking for updates does not report any new version. This is particularly odd because this extension is updated monthly (including in January 2021). Installing an older version of another extension does detect new versions so this not a problem with Checking for Extension Updates but seems specific for this extension (and maybe for others too). Can someone confirm this problem? Just to be clear: this is not a regression or an obstacle for the release of 4.1.9 RC1, the problem also occurs in 4.1.8 Thanks! Pedro
RE: Spelling of Ancient Greek
> > > > The hyphenation and other formatting information is on the Hunspell site > > https://hunspell.github.io/ > > Actually this is the spelling assistant not the hyphenator. This module is described in the following URL: https://www.openoffice.org/lingucomponent/hyphenator.html There I read the following: You need to put an indicator of the character encoding used as the first line of the dictionary file (look in hyph_en.dic). Possible values are: ISO8859-1, ISO8859-2, ..., ISO8859-10, KOI8-R So in the era of Unicode, OpenOffice insists on using single byte encodings which practically means that it is impossible to hyphenate ancient Greek text. The reason? You need UTF-8 hyphenation patterns which of course exist in the TeX world and are used by XeTeX. A.S. -- Apostolos Syropoulos Xanthi, Greece
Re: Spelling of Ancient Greek
On Sat, 2 Jul 2016 21:29:07 +0300 Απόστολος Συρόπουλος <asyropoulos...@hotmail.com> wrote: > >Date: Wed, 29 Jun 2016 14:58:34 -0400 > > From: lui...@gmail.com > > To: dev@openoffice.apache.org > > Subject: Re: Spelling of Ancient Greek > > > > > > louis=C2=A0 > > > > Which means what? BTW, let me ask again: Where are the > hyphenation files and how they are created? > > A.S. > > -- > Apostolos Syropoulos > Xanthi, Greece > > The hyphenation and other formatting information is on the Hunspell site https://hunspell.github.io/ -- Rory O'Farrell <ofarr...@iol.ie> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
