Re: OpenOffice 4.1.10 crashes when loading .odm file
On 2021/08/06 08:09:06, Michael Bouschen wrote: > Hi > > resending my message to dev@openoffice.apache.org (as proposed by Martin > Groenescheij). > > Regards Michael > > > Hi, > > > > the Apache JDO project (https://db.apache.org/jdo/) is using OpenOffice > > for its specification document. We have a OpenDocument Master Document > > JDO_master.odm and several .odt files for the chapters of the specification. > > > > OpenOffice crashes after a few seconds after opening the JDO_master.odm > > document and clicking yes on "Update all links". > > > > I'm using OpenOffice 4.1.10 > > (Apache_OpenOffice_4.1.10_MacOS_x86-64_install_en-US.dmg) on a Mac with > > BigSur version 11.5.You find the mac crash report > > (OpenOfficeCrashReport.txt) attached below with some more details about > > the system and the crash. The document JDO_master.odm and the other .odt > > files may be found here: > > https://github.com/apache/db-jdo/tree/0349ede94788be58f3ff2a439bf740a56833dee2/specification/OOO > > > > I tried other OpenOffice versions: 4.1.10, 4.1.8 and 4.1.5 do crash, but > > versions 4.1.2 and 4.1.0 work fine. > > > > I hope to get some help. For the time being i will will continue using > > OpenOffice 4.1.2. > > > > Regards Michael FYI, just opened fine on my Win10 and AOO 4.1.10 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Typo in navigation bar website www.openoffice.org
Just noticed a typo in the navigation bar on the website pages for www.openoffice.org In the bar it says: "Extentions & Templates" which should be "Extensions & Templates" (It is the bar below the announcement: "Released: Apache OpenOffice 4.1.10") I've been looking some time to find the responsible element, but can't find it anywhere in Github. It is probably the element called: topbara I have no idea where to look for it anymore. Would someone be so kind to fix it for us, or point me to the right place ? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Typo in navigation bar website www.openoffice.org
On 2021/08/26 13:22:08, Dick Groskamp wrote: > Just noticed a typo in the navigation bar on the website pages for > www.openoffice.org > > In the bar it says: "Extentions & Templates" which should be "Extensions & > Templates" > (It is the bar below the announcement: "Released: Apache OpenOffice 4.1.10") > > I've been looking some time to find the responsible element, but can't find > it anywhere in Github. > > It is probably the element called: topbara > > I have no idea where to look for it anymore. > Would someone be so kind to fix it for us, or point me to the right place ? > Should probably be the element : Sorry - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[FIXED] Re: Typo in navigation bar website www.openoffice.org
On 2021/08/26 13:30:53, Dick Groskamp wrote: > > > On 2021/08/26 13:22:08, Dick Groskamp wrote: > > Just noticed a typo in the navigation bar on the website pages for > > www.openoffice.org > > > > In the bar it says: "Extentions & Templates" which should be "Extensions & > > Templates" > > (It is the bar below the announcement: "Released: Apache OpenOffice 4.1.10") > > > > I've been looking some time to find the responsible element, but can't find > > it anywhere in Github. > > > > It is probably the element called: topbara > > > > I have no idea where to look for it anymore. > > Would someone be so kind to fix it for us, or point me to the right place ? > > > Should probably be the element : > Sorry > > - Found it in openoffice-org/content/topnav.md (need better glasses I presume) Fixed - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [GitHub] [openoffice] dave2wave commented on pull request #80: Fixed - single file patches combined into one PR and commit 97a1911
On 2021/10/08 15:46:03, GitBox wrote: > > dave2wave commented on pull request #80: > URL: https://github.com/apache/openoffice/pull/80#issuecomment-938744005 > > >Does this patch replace #76, #75, and #74? > > @dave2wave : "Does this patch replace #76, #75, and #74?" No, it doesn't. Those are subsequent patches regarding the superfluous spaces in the Help files which show up in the translation tool Pootle. These patches fix that. I was then (march 2020) just starting out with Github. Didn't know if it could handle so much fixes in one patch, so I split them up. There were very much files to fix. Hence the patches #74, #75 and #76. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release Notes (pl) - missing letters in the exported .pdf file
On 2021/10/21 11:08:33, Czesław Wolański wrote: > Hi, > > AOO 4.1.11 Release Notes - Polish version > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191333544 > > The "Export to PDF" option produces the .pdf file but some Polish letters > with diacritics > are missing. Export in Word format is correct. > > File with screenshots is available at the address: > https://drive.google.com/file/d/1Pw2Kj6DIKqcfgYDTuU9bzg6zqpOxMOBA/view?usp=sharing > > Does anyone know what the problem is? > > > Regards, > Czesław > Seems to be a bug in Confluence. See answer at https://jira.atlassian.com/browse/CONFCLOUD-59512 Solution seems to be to use the Print option in your browser and then Save as PDF. Seems to work on my machine (Win10) but then again, I have no clue of Polish charcters :-) It surely looks better than the example from Czeslaw - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: unfortunately I have to say goodbye to the AOO project
Jörg, thanks for all your efforts these past years. Wishing you and your family all the best for the future. Stay safe. On 2021/12/27 05:13:50 Jörg Schmidt wrote: > Hello everyone, > > unfortunately I have to say goodbye to the AOO project, the reasons are > family related. > > I would like to thank everyone involved in AOO and OOo for the last 16 years. > > > I wish you all and the AOO project all the best. > > > greetings > Jörg > > (committer-ID: "joesch") > > > - > 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: [openoffice] branch AOO41X updated: Fixed strings in en-GB, es, fr, pl SDF
Matthias, Looks OK. Thanks for that :-) Dick On 2022/02/01 16:38:23 Matthias Seidel wrote: > Hi Dick, > > Am 31.01.22 um 19:40 schrieb Dick Groskamp: > > Matthias, > > should nl also be changed? > > I see it is mostly a change in the number for the .png > > (src=\"sw/imglst/sc20244.png to src=\"sw/imglst/sc20234.png) > > Yes, indeed. This change is independent from translation and can be > enabled for more languages. > > "Patching" the SDF is a bit nasty but the two strings are easily found > by their id. I just did it for nl. > > Be sure that this is corrected in Pootle: > > https://translate.apache.org/nl/aoo40help/translate/helpcontent2/source/text/swriter/guide.po#unit=32252128 > > https://translate.apache.org/nl/aoo40help/translate/helpcontent2/source/text/swriter/01.po#unit=32252124 > > Regards, > > Matthias > > > > > > On 2022/01/23 13:10:48 msei...@apache.org wrote: > >> This is an automated email from the ASF dual-hosted git repository. > >> > >> mseidel pushed a commit to branch AOO41X > >> in repository https://gitbox.apache.org/repos/asf/openoffice.git > >> > >> > >> The following commit(s) were added to refs/heads/AOO41X by this push: > >> new 6536859 Fixed strings in en-GB, es, fr, pl SDF > >> 6536859 is described below > >> > >> commit 6536859c5c208e2daf8ee56bacec44b8abef37d3 > >> Author: mseidel > >> AuthorDate: Sun Jan 23 14:10:24 2022 +0100 > >> > >> Fixed strings in en-GB, es, fr, pl SDF > >> --- > >> extras/l10n/source/en-GB/localize.sdf | 4 ++-- > >> extras/l10n/source/es/localize.sdf| 4 ++-- > >> extras/l10n/source/fr/localize.sdf| 4 ++-- > >> extras/l10n/source/pl/localize.sdf| 4 ++-- > >> 4 files changed, 8 insertions(+), 8 deletions(-) > >> > >> diff --git a/extras/l10n/source/en-GB/localize.sdf > >> b/extras/l10n/source/en-GB/localize.sdf > >> index e9272f3..754f0bd 100644 > >> --- a/extras/l10n/source/en-GB/localize.sdf > >> +++ b/extras/l10n/source/en-GB/localize.sdf > >> @@ -18251,7 +18251,7 @@ helpcontent2 > >> source\text\swriter\guide\arrange_chapters.xhp 0 help > >> par_id3155461 > >> helpcontent2 source\text\swriter\guide\arrange_chapters.xhp 0 > >> helphd_id315118470 0 en-GB To Move a > >> Heading Up or Down in the Document20130618 > >> 17:22:18 > >> helpcontent2 source\text\swriter\guide\arrange_chapters.xhp 0 > >> helppar_id0915200809400790 0 en-GB > >> Ensure that all heading levels are shown in the Navigator. By default all > >> levels are shown. See steps below how to change the heading levels that > >> are shown.20130618 17:22:18 > >> helpcontent2 source\text\swriter\guide\arrange_chapters.xhp 0 > >> helppar_id3151206 71 0 en-GB On the > >> \Standard Bar\, click the \Navigator\ icon > >> \ >> width=\"0.564cm\" height=\"0.564cm\"\>\ >> id=\"alt_id5211883\"\>Icon\\ to open the > >> \Navigator\. 20130618 17:22:18 > >> -helpcontent2 source\text\swriter\guide\arrange_chapters.xhp 0 > >> helppar_id3151238 72 0 en-GB On the > >> \Navigator\, click the \Content View\ icon > >> \ >> width=\"0.564cm\" height=\"0.564cm\"\>\ >> id=\"alt_id3156338\"\>Icon\\. > >> 20130618 17:22:18 > >> +helpcontent2 source\text\swriter\guide\arrange_chapters.xhp 0 > >> helppar_id3151238 72 0 en-GB On the > >> \Navigator\, click the \Content View\ icon > >> \ >> width=\"0.564cm\" height=\"0.564cm\"\>\ >> id=\"alt_id3156338\"\>Icon\\. > >> 20130618 17:22:18 > >> helpcontent2 source\text\swriter\guide\arrange_chapters.xhp 0 > >> helppar_id3155089 74 0 en-GB Do one of > >> the following:20130618 17:22:18 > >> helpcontent2 source\text\swriter\guide\arrange_chapters.xhp 0 > >> helppar_id3155114 63 0 en-GB Drag a > >> heading to
Is certificate from https:/translate.apache.org expired ?
Tried to log in on the Pootle server at https://translate.apache.org. Firefox can't connect me, indicating that the certifcate for the server might be expired or my computerclock is off. The latter is OK. Could someone check ? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Forums OpenOffice are very slow
Sent an email to Infra since the forums are still not responding. Apache Status page does not mention any incident for today or yesterday On 2022/04/17 05:44:55 casa...@email.it wrote: > The forums have not opened for almost 24 hours. > > - Messaggio originale - > Da: "Bidouille" > A: "dev" > Inviato: Sabato, 16 aprile 2022 18:25:52 > Oggetto: Forums OpenOffice are very slow > > Hello, > Since this morning, forums are very slw. > I don't know if this comes from PhpBB or MySQL. > Maybe restart all services? > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Forums OpenOffice are very slow
Seems to happen again, at least from where I live. Created an issue for Infra (INFRA-23156) On 2022/04/17 16:38:29 Dave Fisher wrote: > Hi - > > I’ve restarted Apache HTTPD. Seems fine from California … > > Regards, > Dave > > > On Apr 17, 2022, at 8:34 AM, Rory O'Farrell wrote: > > > > On Sun, 17 Apr 2022 15:20:39 - > > Dick Groskamp wrote: > > > >> Sent an email to Infra since the forums are still not responding. > >> Apache Status page does not mention any incident for today or yesterday > >> > > > > Response has improved on Sunday (17 April 2022) though not yet perfect. My > > tests are showing > > connection problems onwards from London - traceroute timing out. > > > > RoryOF > > > > > >> > >> On 2022/04/17 05:44:55 casa...@email.it wrote: > >>> The forums have not opened for almost 24 hours. > >>> > >>> - Messaggio originale - > >>> Da: "Bidouille" > >>> A: "dev" > >>> Inviato: Sabato, 16 aprile 2022 18:25:52 > >>> Oggetto: Forums OpenOffice are very slow > >>> > >>> Hello, > >>> Since this morning, forums are very slw. > >>> I don't know if this comes from PhpBB or MySQL. > >>> Maybe restart all services? > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >>> For additional commands, e-mail: dev-h...@openoffice.apache.org > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >>> For additional commands, e-mail: dev-h...@openoffice.apache.org > >>> > >>> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> > > > > > > -- > > Rory O'Farrell > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [IMPORTANT] Scheduling Maintenance for our Forum
Thanks for the update Dave. Much appreceated.
Dutch forum looks good.
On 2022/05/04 23:06:54 Dave Fisher wrote:
> Maintenance on the Forums is completed!
>
> The Forums are now at phpBB 3.3.7 which was released March 17, 2023. The
> prior version was 3.0.9 released July 10, 2011.
>
> Very, very happy. Future updates should be much easier. I will follow up with
> the Forum sysadmins on these issues:
>
> 1. The Italian Forum has a weird display issues. I think that a post will
> need to be regenerated.
> 2. We need to find forum administrators to replace imacat for each forum.
> 3. I will need to document the process, customizations and migration steps.
>
> But I’ll need a few days away.
>
> ATB,
> Dave
>
> > On May 4, 2022, at 7:38 AM, Dave Fisher wrote:
> >
> > Https://forum.openoffice.org is now offline with a simple page to checkbook
> > later..
> >
> >> On May 4, 2022, at 7:04 AM, Dave Fisher wrote:
> >>
> >>
> >>
> >>> On May 4, 2022, at 1:14 AM, David Robley wrote:
> >>>
> >>> Registration works OK; I registered a new user, got the activation email
> >>> and activated the account. Then posted a first message and (as moderator)
> >>> approved it, but I _did not_ get the email advising of approval although
> >>> the post was cleared. I did check junk as that was where the activation
> >>> email ended up :-).
> >>>
> >>> There is an apparent inconsistency on the mod control panel; some recent
> >>> events that are displayed under the Moderator Logs tab do not appear
> >>> under the Main tab.
> >>>
> >>> While I'm on the topic, is there any chance the change to the search page
> >>> I mentioned at
> >>> https://forum.openoffice.org/en/forum/viewtopic.php?t=105949#p515320
> >>> might be implemented?
> >>
> >> Done! Try it on the EN forum and I’ll propagate to the others.
> >>
> >>>
> >>> And, pushing my (our?) luck even more, the extensions Banhammer and
> >>> stopforumspam mentioned in
> >>> https://forum.openoffice.org/en/forum/viewtopic.php?f=104&t=96141#p513871
> >>
> >> We’re going to need to take full control of the forum sysadmin role once
> >> the migration is completed.
> >>
> >>>
> >>> On 5/2/22 17:28, Dave Fisher wrote:
> The en and fr forums are available to test:
>
> https://openoffice-vm1-lw-us.apache.org/
>
> Please test these forums.
>
> Known work to do:
> - Restore the Apache Open Office logo in the header
> - Return the Apache and Get OpenOffice information in the footer
> - Avatars have moved in 3.3.7 need to determine how to move them.
>
> The automatic mySQL migration from 3.0.9 seems to work but takes quite
> some time.
>
> ATB,
> Dave
>
> > On May 1, 2022, at 11:16 AM, Dave Fisher wrote:
> >
> > Apologies for the late communication.
> >
> > The forums are being updated from phpBB 3.0.9 to 3.3.7.
> >
> > Differences so far:
> > 1. The subsilver2 theme is no longer available.
> > 2. Analytics are removed due to new ASF privacy policies. We can add
> > back analytics that are compliant in the next weeks.
> > 3. Search Display code is changed and I could not see how add
> > ({NEW_POST_COUNT}) into styles/prosilver/template/index_body.html
> > 4. /style.php is no longer included.
> > 5. /app.php is new.
> > 6. /includes/ucp/ucp_register.php will need to be tested on the French
> > forum.
> > 7. /feed.php is reorganized and it was not clear how to add the
> > customized rel=“alternate” to one of the links.
> >
> > This doesn’t seem bad.
> > Language packs were found and AOO customizations are added.
> >
> > I expect to finish late tonight - when ready there will be a test url.
> >
> > Once the forums are put into maintenance the following will happen:
> >
> > 1. Make sure all the files and images that have been uploaded are
> > copied.
> > 2. Dumps of the mysql databases will be copied over.
> > 3. Forum databases will be updated
> > 4. Forum admins will have a chance to test.
> > 5. Once live we’ll triage any issues.
> >
> > Bidouille has access to the VM … any other forum admins who are already
> > OpenOffice committers may request access.
> >
> > A warning - this same VM hosts the wiki and the mysql databases.
> >
> > I’ll be offline for a few hours before returning to this work and to
> > answer any questions.
> >
> > ATB,
> > Dave
> >
> >> On May 1, 2022, at 10:43 AM, Peter Kovacs wrote:
> >>
> >>
> >> Am 01.05.22 um 15:59 schrieb Rory O'Farrell:
> >>> On Sun, 1 May 2022 15:53:47 +0200
> >>> Peter Kovacs wrote:
> >>>
> Hello all,
>
>
> please note, that we schedule a maintenance for the Forum in order to
> move database and content to a new machine. This maintenance tasks
>
Re: [GRAPHICS] Help with SVG versions of AOO website logo and Forum Header
Dave, For Dutch (NL) you don't need a separate Forum Header. You can safely use the EN version. We Dutch do so now and again "borrow" words from other languages. Forum is one of them. NL uses the same word as in English So you can safely use the EN version then (Or copy and name it NL) On 2022/05/07 18:38:53 Dave Fisher wrote: > Hi - [ ] > The same graphic on every forum right now. Size is 450px x 77px. Extra credit > if someone can create versions for: ES, FR, HU, IT, JA, NL, and PL. VI is > read-only and ZH is non-functional and not currently available. > > (2) The website logo - > https://github.com/apache/openoffice-org/blob/main/assets/images/AOO_logos/AOO4_website_logo.png > > The size is 268px x 100px > > Best, > Dave > - > 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: Forums and FAQ
Dave, for Dutch (NL) you might want to use: 'HELP_FAQ_AOO_SPECIFIC' => 'OpenOffice gemeenschap Forum Specifieke problemen', 'HELP_FAQ_AOO_WHERE_CAN_I_FIND' => 'Waar vind ik FAQ's die specifiek een relatie hebben met producten van OpenOffice?', 'HELP_FAQ_AOO_WHERE'=> 'We onderhouden niet per se een FAQ, maar het beste is als u begint met Lees dit eerst, wat u zal uitleggen hoe het forum te gebruiken. U kunt ook specifieke handleidingen vinden in het forum Tutorials. U kunt ook de https://wiki.openoffice.org/wiki/NL/Main_Page";>OpenOffice wiki gebruiken als een kennisbron.', 'HELP_FAQ_AOO_HOW_TO_ASK' => ‘ Hoe stel ik een vraag?', 'HELP_FAQ_AOO_HOW' => 'Lees eerst het gedeelte Lees dit eerst voordat u een vraag stelt. Deze richtlijnen en regels helpen de gemeenschap om het meeste uit dit forum te halen. De rest van deze FAQ behandelt algemene problemen die te maken hebben met het gebruiken van phpBB3.', On 2022/05/10 00:25:55 Dave Fisher wrote: > Hi - > > We need versions of the following strings to add for each language: > > ./language/en/help/faq.php > 'HELP_FAQ_AOO_SPECIFIC' => 'OpenOffice.org > Community Forum Specific Issues', > 'HELP_FAQ_AOO_WHERE_CAN_I_FIND' => 'Where can I find > FAQs relating specifically to OpenOffice.org products?', > 'HELP_FAQ_AOO_WHERE'=> 'We don\'t maintain > an FAQ per se, but you is you start with our href="/en/forum/viewtopic.php?t=166">Survival Guide, this will explain > how to go about using the forum. You will also find specific tutorials in > the Tutorials forum. You can also > use the https://wiki.openoffice.org/wiki/";>OpenOffice wiki as a > knowledge source.', > 'HELP_FAQ_AOO_HOW_TO_ASK' => ‘ > How do I ask a question?', > 'HELP_FAQ_AOO_HOW' => 'Please read > the Survival Guide before you > post. These guidelines and rules help the community to make the most > of this forum. The remainder of this FAQ coverts general issues to > do with the using phpBB3.', > > Here’s where the strings are used. > > ./phpbb/help/controller/faq.php > 'HELP_FAQ_AOO_SPECIFIC', > 'HELP_FAQ_AOO_WHERE_CAN_I_FIND' => > 'HELP_FAQ_AOO_WHERE', > 'HELP_FAQ_AOO_HOW_TO_ASK' => 'HELP_FAQ_AOO_HOW', > > Regards, > Dave > > > > On May 9, 2022, at 10:33 AM, Bidouille wrote: > > > > Hello, > > > > Small problem with FAQ on all forums except EN > > https://forum.openoffice.org/fr/forum/download/file.php?id=145454 > > > > I don't know how these strings has been added. > > > > > > - > > 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: Reporting a problem with the OpenOffice Wiki and Forums
Just found another one on the wiki: http://www.openoffice.org/qa/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabaseLinks.html points to several links, of which most work correctly. However, the link to Database Wiki, which is: wiki.services.openoffice.org/wiki/Category:Database redirects to https://forum.openoffice.org/wiki/Category:Database but should redirect to https://wiki.openoffice.org/wiki/Category:Database. Therefore I think that Matthias is right. There is something going wrong on the wiki with the redirects from "wiki.services". Redirections go inadvertently to "forum.openoffice.org" They should redirect to "wiki.openoffice.org/" but they redirect now to "forum.openoffice.org" which throws a 404. Changing "forum" on the 404 to "wiki" will give you the right page. I have no clue as where to search for the error, but I assume its somewhere in the configuration of the forum On 2022/05/15 08:15:45 Peter Kovacs wrote: > Binjour! > > This list is the right place to ask. > > Both Links point to missing Articles on the Forum. Since we updated the > Forum software, could it be that links has been changed? > > Maybe searching on the en Forum would help and renew the link. > > > > Am 15.05.22 um 09:12 schrieb Troumad libertysurf: > > [FR] > > > > Bonjour > > > > Je ne sais où parler de ce problème. Si on me dit tant-pis, je ne les > > remonterais plus... > > Sur la page > > https://www.openoffice.org/api/docs/common/ref/com/sun/star/lang/EventObject.html > > > > il y a deux liens qui ne répondent plus : > > > > OfficeDev - Document Events > > Database - Events and Other Notifications > > > > > > [EN by https://www.deepl.com/] > > > > Hello > > > > I don't know where to talk about this problem. If someone tells me no > > more, I won't bring them up again... > > On the page > > https://www.openoffice.org/api/docs/common/ref/com/sun/star/lang/EventObject.html > > > > there are two links that don't work anymore: > > > > OfficeDev - Document Events > > Database - Events and Other Notifications > > > > - > 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: Smart tags
Mtthias, I've seen them in a very oold OOo. As far as I know it died quietly and has never been seen anymore. Maybe this can shed some light for you: https://wiki.openoffice.org/wiki/Writer/Smart_Tags On 2022/05/17 13:56:33 Matthias Seidel wrote: > Hi all, > > While browsing through the code, I found references to "smart tags": > > http://opengrok.openoffice.org/search?project=trunk&full=%22smart+tag%22&defs=&refs=&path=%2Fmain&hist=&type=plain&si=full > > I have never seen that in real life. Can anyone tell me, what a smart > tag is? > Are there any extensions using this? > > Regards, > > Matthias > > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wiki and Forum offliune (again)?
On 2022/08/11 11:20:45 Matthias Seidel wrote: > Subject says it all. > > Today first the Wiki then the forum went offline. I think they are on > the same machine? > > Regards, > > Matthias > They just came back on my site :-) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wiki and Forum offliune (again)?
Just noticed this one not the earlier. Sent a mail to Infra and they will probably investigate. Let you know if I hear back from them Greetings On 2022/08/11 11:57:44 Matthias Seidel wrote: > Am 11.08.22 um 13:52 schrieb Dick Groskamp: > > > > On 2022/08/11 11:20:45 Matthias Seidel wrote: > >> Subject says it all. > >> > >> Today first the Wiki then the forum went offline. I think they are on > >> the same machine? > >> > >> Regards, > >> > >> Matthias > >> > > They just came back on my site :-) > > Confirmed! > > But this was the second(?) time in a few days... > > > > > - > > 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: Forum issue
Sent an email to Infra with request to check the performance On 2023/09/12 16:57:50 Bidouille wrote: > That's seem issue is back. > Very slow connections. > > - Mail original - > > De: "Bidouille" > > À: dev@openoffice.apache.org > > Envoyé: Lundi 28 Août 2023 19:39:12 > > Objet: Re: French forum issue > > > > Seems to be an SSL issue > > https://www.wormly.com/test_ssl/h/forum.openoffice.org/i/207.244.88.139/p/443 > > See SSL Handshake Size > > > > The Sectigo certificate expire in 3 months. > > > > Somebody can take care this? > > > > - Mail original - > > > De: "Bidouille" > > > À: "dev" > > > Envoyé: Dimanche 27 Août 2023 18:20:35 > > > Objet: French forum issue > > > > > > Hello, > > > > > > Since a couple of days, our forum is abnormally slow. > > > Seems to be only for us, english forum has not this issue. > > > I have no idea how explain this. > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Are Forum and Wiki down ??
We now are experiencing downtime on Apache OpenOffice fora (https:/forum.openoffice.org/en/forum;https:/forum.openoffice.org/nl/forum) and the OpenOffice wiki (https://wiki.openoffice.org/wiki). Sites report error to Firefox and Firefox says it can't connect Earlier (2023-09-13) I mailed about slow performance: We are experiencing a very slow performance on Apache OpenOffice fora (https:/forum.openoffice.org/en/forum;https:/forum.openoffice.org/nl/forum) and the OpenOffice wiki (https://wiki.openoffice.org/wiki). Also reported on the mailinglist dev@openoffice.apache.org by French user Bidouille __ Could?Would you check please ? -- DiGro ___ Apache OpenOffice 4.1.14 (Dutch) and scanned with Ziggo Safe Online (F-Secure)
Fora and wiki down
Reported to Infra (JIRA- issue https://issues.apache.org/jira/browse/OPENOFFICE-200) We now are experiencing downtime on Apache OpenOffice fora (https:/forum.openoffice.org/en/forum;https:/forum.openoffice.org/nl/forum) and the OpenOffice wiki (https://wiki.openoffice.org/wiki). Sites report error to Firefox and Firefox says it can't connect Earlier (2023-09-13) I mailed about slow performance: We are experiencing a very slow performance on Apache OpenOffice fora (https:/forum.openoffice.org/en/forum;https:/forum.openoffice.org/nl/forum) and the OpenOffice wiki (https://wiki.openoffice.org/wiki). Also reported on the mailinglist dev@openoffice.apache.org by French user Bidouille __ Could?Would you check please ? -- DiGro ___ Apache OpenOffice 4.1.14 (Dutch) and scanned with Ziggo Safe Online (F-Secure)
Re: AOO crashes at start if Sitka*.ttc font
Works for me on Windows 11. AOO 4.1.15 (Dutch) On 2024/01/13 08:07:58 "Paweł (Tomasz)" wrote: > Hello > > If there is any Sitka.ttc font in .fonts folder AOO crashes at start. > > guest@me:~$ openoffice4 > Application Error > > Fatal exception: Signal 6 > Stack: > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37c3a)[0x7f1409e37c3a] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37d6c)[0x7f1409e37d6c] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37e09)[0x7f1409e37e09] > /lib64/libc.so.6(+0x40f10)[0x7f1409612f10] > /lib64/libc.so.6(pthread_kill+0xfc)[0x7f1409663e3c] > /lib64/libc.so.6(raise+0x12)[0x7f1409612e72] > /lib64/libc.so.6(abort+0xc1)[0x7f14095fa49b] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x1557dd)[0x7f14051557dd] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libsofficeapp.so(+0x2354b)[0x7f1409a2354b] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x17ff2e)[0x7f140517ff2e] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x36a02)[0x7f1409e36a02] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37dea)[0x7f1409e37dea] > /lib64/libc.so.6(+0x40f10)[0x7f1409612f10] > /lib64/libc.so.6(pthread_kill+0xfc)[0x7f1409663e3c] > /lib64/libc.so.6(raise+0x12)[0x7f1409612e72] > /lib64/libc.so.6(abort+0xc1)[0x7f14095fa49b] > /usr/lib64/libfontconfig.so.1(+0x875c)[0x7f14033bf75c] > /usr/lib64/libfontconfig.so.1(+0x1df55)[0x7f14033d4f55] > /usr/lib64/libfontconfig.so.1(+0x1e2d7)[0x7f14033d52d7] > /usr/lib64/libfontconfig.so.1(+0x1e3d7)[0x7f14033d53d7] > /usr/lib64/libfontconfig.so.1(FcFontMatch+0x68)[0x7f14033d6178] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x137375)[0x7f1405137375] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x137406)[0x7f1405137406] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZN3psp16PrintFontManager20countFontconfigFontsERSt8hash_mapIN3rtl7OStringEiNS2_11OStringHashESt8equal_toIS3_EE+0x35)[0x7f1405138c3b] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZN3psp16PrintFontManager10initializeEv+0x247)[0x7f1405144243] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZN3psp16PrintFontManager3getEv+0x49)[0x7f1405145107] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvclplug_gen.so(_ZN14X11SalGraphics14GetDevFontListEP15ImplDevFontList+0x2c)[0x7f13fbc70156] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x25ab4c)[0x7f140525ab4c] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x261682)[0x7f1405261682] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZNK12OutputDevice14GetFontCharMapER11FontCharMap+0x33)[0x7f140526172d] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZNK12OutputDevice9HasGlyphsERK4FontRK6Stringtt+0x82)[0x7f1405261804] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x3857de)[0x7f14053857de] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x3858c4)[0x7f14053858c4] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x392017)[0x7f1405392017] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x3153df)[0x7f14053153df] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x3154e3)[0x7f14053154e3] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x39ca26)[0x7f140539ca26] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZN10WorkWindowC1EP6Windowl+0x3e)[0x7f140539cc3e] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libootk.so(+0x1bac78)[0x7f14065bac78] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libootk.so(+0x1bb191)[0x7f14065bb191] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libootk.so(+0x1bb3c3)[0x7f14065bb3c3] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libfwk.so(+0x121de2)[0x7f13ff321de2] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libfwk.so(+0x12291a)[0x7f13ff32291a] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libfwk.so(+0x920de)[0x7f13ff2920de] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libfwk.so(+0x10484f)[0x7f13ff30484f] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libsofficeapp.so(+0x2e0e6)[0x7f1409a2e0e6] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x180813)[0x7f1405180813] > /mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_Z6SVMainv+0x1e)[0x7f14051808de] > /mnt/sda2/porteux/x86_6
Re: [PR] Remove Urchin Tracker - a use of google analytics [openoffice-org]
Dave, feel free to dump it. It is a relic from the past On 2024/05/14 19:59:29 "dave2wave (via GitHub)" wrote: > > dave2wave commented on PR #92: > URL: https://github.com/apache/openoffice-org/pull/92#issuecomment-2111040621 > >@DiGro Does this very old page have any use? > http://www.openoffice.org/nl/thankyoupage/. It has a tracker on it and seems > to exist from Sun -> Oracle times. I would like to rip it out > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Not yet translated functions UNICODE and UNICHAR
I'm currently working my way through the Helpfiles, trying to synchronize between Pootle and the available SDF and the existing Help-pages for Dutch. I noticed several discrepancies between those instances. One of the most significant is the missing translation in the SDF for the functions UNICODE and UNICHAR, that is, they are mentioned for the Help-files, but not for the UI (there they still are UNICODE and UNICHAR) Would it be possible to already add the translations for these functions, or do I have to go to all the Help-files first to get POOTLE fully up to date? It concerns just two small strings for the UI: formula source\core\resource\core_resource.src 0 string RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICODE -> nl UNI.CODE formula source\core\resource\core_resource.src 0 string RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICHAR --> nl UNI.TEKEN I've already added them to Pootle, but don't know how to get them in the upcoming builds. If they are not there, only way to use them is to use English names, but, as you understand, that's not synchronized with Help -- DiGro ___ Apache OpenOffice 4.1.15 (Dutch) and scanned with Ziggo Safe Online (F-Secure)
Re: Not yet translated functions UNICODE and UNICHAR
Matthias, I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated 20200411. I think it is the most recent one. Problems I see is that they are also out of sync. nl Help-files are not in sync with SDF and also not with Pootle. For now I fixed the discrepancies by updating the Help-files and put them into the *.jars of the nl Help on my machine. That seems to work for now. I also plan to update Pootle with the corrections. That will be a manual task I'm afraid :-) Then, when translation process would work again, Pootle is in sync and updated, which should deliver correct sdf. Greetings On 2024/07/25 14:58:18 Matthias Seidel wrote: > Hi Dick, > > Am 23.07.24 um 15:12 schrieb Dick Groskamp: > > I'm currently working my way through the Helpfiles, trying to > > synchronize between Pootle and the available SDF and the existing > > Help-pages for Dutch. > > > > I noticed several discrepancies between those instances. > The available SDF (which ones exactly?) are out of date. > > > > One of the most significant is the missing translation in the SDF for > > the functions UNICODE and UNICHAR, > > > > that is, they are mentioned for the Help-files, but not for the UI > > (there they still are UNICODE and UNICHAR) > > > > Would it be possible to already add the translations for these > > functions, or do I have to go to all the Help-files first to get > > POOTLE fully up to date? > > > > It concerns just two small strings for the UI: > > > > formula source\core\resource\core_resource.src 0 string > > RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICODE -> nl UNI.CODE > > formula source\core\resource\core_resource.src 0 string > > RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICHAR --> nl UNI.TEKEN > > > > > > I've already added them to Pootle, but don't know how to get them in > > the upcoming builds. > > *When* the translation process is working again, you will find them in > AOO42X. > > Regards, > > Matthias > > > > > If they are not there, only way to use them is to use English names, > > but, as you understand, that's not synchronized with Help > > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Not yet translated functions UNICODE and UNICHAR
BTW, does someone know what is wrong/defect with the translation process ?? On 2024/07/25 14:58:18 Matthias Seidel wrote: > Hi Dick, > > Am 23.07.24 um 15:12 schrieb Dick Groskamp: > > I'm currently working my way through the Helpfiles, trying to > > synchronize between Pootle and the available SDF and the existing > > Help-pages for Dutch. > > > > I noticed several discrepancies between those instances. > The available SDF (which ones exactly?) are out of date. > > > > One of the most significant is the missing translation in the SDF for > > the functions UNICODE and UNICHAR, > > > > that is, they are mentioned for the Help-files, but not for the UI > > (there they still are UNICODE and UNICHAR) > > > > Would it be possible to already add the translations for these > > functions, or do I have to go to all the Help-files first to get > > POOTLE fully up to date? > > > > It concerns just two small strings for the UI: > > > > formula source\core\resource\core_resource.src 0 string > > RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICODE -> nl UNI.CODE > > formula source\core\resource\core_resource.src 0 string > > RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICHAR --> nl UNI.TEKEN > > > > > > I've already added them to Pootle, but don't know how to get them in > > the upcoming builds. > > *When* the translation process is working again, you will find them in > AOO42X. > > Regards, > > Matthias > > > > > If they are not there, only way to use them is to use English names, > > but, as you understand, that's not synchronized with Help > > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Not yet translated functions UNICODE and UNICHAR
On 2024/07/26 11:42:26 Matthias Seidel wrote: > Hi Dick, > > Am 26.07.24 um 09:22 schrieb Dick Groskamp: > > Matthias, > > > > I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated > > 20200411. > > I think it is the most recent one. > Yes, the "most recent one" (for NL) is 4 years old... > > > > Problems I see is that they are also out of sync. > > nl Help-files are not in sync with SDF and also not with Pootle. > Everything is out of sync. > > > > For now I fixed the discrepancies by updating the Help-files and put them > > into the *.jars of the nl Help on my machine. That seems to work for now. > > I also plan to update Pootle with the corrections. That will be a manual > > task I'm afraid :-) > > Translation in Pootle has always been a manual process? Yes, but I wonder how the strings from Pootle for nl ever got in Helpfiles :-) I have no clue at all. After that then the Helpfiles are packaged somehow and delivered to the download package I assume > > > Then, when translation process would work again, Pootle is in sync and > > updated, > > which should deliver correct sdf. > > Whenever that will be... ;-) I haven't seen any new strings come in the last four/five years so I can slowly move forwards. One example: Image for STOP for BASIC macro (sc_basicstop.png) was sc_stop.png in nl Help file, showing nothing :-( > > Regards, > > Matthias > > > > > Greetings > > > > On 2024/07/25 14:58:18 Matthias Seidel wrote: > >> Hi Dick, > >> > >> Am 23.07.24 um 15:12 schrieb Dick Groskamp: > >>> I'm currently working my way through the Helpfiles, trying to > >>> synchronize between Pootle and the available SDF and the existing > >>> Help-pages for Dutch. > >>> > >>> I noticed several discrepancies between those instances. > >> The available SDF (which ones exactly?) are out of date. > >>> One of the most significant is the missing translation in the SDF for > >>> the functions UNICODE and UNICHAR, > >>> > >>> that is, they are mentioned for the Help-files, but not for the UI > >>> (there they still are UNICODE and UNICHAR) > >>> > >>> Would it be possible to already add the translations for these > >>> functions, or do I have to go to all the Help-files first to get > >>> POOTLE fully up to date? > >>> > >>> It concerns just two small strings for the UI: > >>> > >>> formula source\core\resource\core_resource.src 0 string > >>> RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICODE -> nl UNI.CODE > >>> formula source\core\resource\core_resource.src 0 string > >>> RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICHAR --> nl UNI.TEKEN > >>> > >>> > >>> I've already added them to Pootle, but don't know how to get them in > >>> the upcoming builds. > >> *When* the translation process is working again, you will find them in > >> AOO42X. > >> > >> Regards, > >> > >> Matthias > >> > >>> If they are not there, only way to use them is to use English names, > >>> but, as you understand, that's not synchronized with Help > >>> > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Not yet translated functions UNICODE and UNICHAR
OK, looked into it a bit. >From the en-us.sdf new templates have to be created, which are then uploaded >to Pootle. (This will add new strings and mark deprecated ones) After that, all existing translations have to be downloaded to disk Then the downloaded translations can be updated with the new templates. One catch though: each language has to be individually been updated. After that has been done, syncing the updated files with Pootle is the last step. Cumbersome :-( On 2024/07/26 15:26:49 Matthias Seidel wrote: > Hi Dick, > > Am 26.07.24 um 16:55 schrieb Dick Groskamp: > > On 2024/07/26 11:42:26 Matthias Seidel wrote: > >> Hi Dick, > >> > >> Am 26.07.24 um 09:22 schrieb Dick Groskamp: > >>> Matthias, > >>> > >>> I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is dated > >>> 20200411. > >>> I think it is the most recent one. > >> Yes, the "most recent one" (for NL) is 4 years old... > >>> Problems I see is that they are also out of sync. > >>> nl Help-files are not in sync with SDF and also not with Pootle. > >> Everything is out of sync. > >>> For now I fixed the discrepancies by updating the Help-files and put them > >>> into the *.jars of the nl Help on my machine. That seems to work for now. > >>> I also plan to update Pootle with the corrections. That will be a manual > >>> task I'm afraid :-) > >> Translation in Pootle has always been a manual process? > > Yes, but I wonder how the strings from Pootle for nl ever got in Helpfiles > > :-) > > The last export was done by an IBM employee in 2014. > > Then I spoke to Mechtilde in 2019 and she got the process running again, > but everything was manually. > > At one point the process broke (Pootle update?) and here we are. > > > I have no clue at all. After that then the Helpfiles are packaged somehow > > and delivered to the download package I assume > >>> Then, when translation process would work again, Pootle is in sync and > >>> updated, > >>> which should deliver correct sdf. > >> Whenever that will be... ;-) > > I haven't seen any new strings come in the last four/five years so I can > > slowly move forwards. > > There were a lot of new strings in that time, but Pootle simply wasn't > updated. > > > > > One example: > > Image for STOP for BASIC macro (sc_basicstop.png) > > was sc_stop.png in nl Help file, showing nothing :-( > > I *think* that was solved at one point, but the changes didn't make it > into Pootle. > > But you can always try the en-US build to see the actual development... > > BTW, SDF for en-US is not in our source, it gets exported weekly by our > buildbot: > > https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D > > Regards, > > Matthias > > >> Regards, > >> > >> Matthias > >> > >>> Greetings > >>> > >>> On 2024/07/25 14:58:18 Matthias Seidel wrote: > >>>> Hi Dick, > >>>> > >>>> Am 23.07.24 um 15:12 schrieb Dick Groskamp: > >>>>> I'm currently working my way through the Helpfiles, trying to > >>>>> synchronize between Pootle and the available SDF and the existing > >>>>> Help-pages for Dutch. > >>>>> > >>>>> I noticed several discrepancies between those instances. > >>>> The available SDF (which ones exactly?) are out of date. > >>>>> One of the most significant is the missing translation in the SDF for > >>>>> the functions UNICODE and UNICHAR, > >>>>> > >>>>> that is, they are mentioned for the Help-files, but not for the UI > >>>>> (there they still are UNICODE and UNICHAR) > >>>>> > >>>>> Would it be possible to already add the translations for these > >>>>> functions, or do I have to go to all the Help-files first to get > >>>>> POOTLE fully up to date? > >>>>> > >>>>> It concerns just two small strings for the UI: > >>>>> > >>>>> formula source\core\resource\core_resource.src 0 string > >>>>> RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICODE -> nl UNI.CODE > >>>>> formula source\core\resource\core_resource.src 0 string > >>>>> RID_STRLIST_FUNCTION_NAMES SC_OPCODE_UNICHAR --> nl UNI.TEKEN >
Re: Not yet translated functions UNICODE and UNICHAR
Matthias On 2024/07/28 08:17:48 Matthias Seidel wrote: > Hi Dick, > > Am 27.07.24 um 15:37 schrieb Dick Groskamp: > > OK, looked into it a bit. > > > > >From the en-us.sdf new templates have to be created, which are then > > >uploaded to Pootle. > > (This will add new strings and mark deprecated ones) > > After that, all existing translations have to be downloaded to disk > The translation does not need to be downloaded. Maybe, but I didn't have the karma :-) > > Then the downloaded translations can be updated with the new templates. > That should happen on the Pootle server. Well, as I understand it, that is the part that is broken :-( Seems that automated version could leave Pootle in a bad state https://stackoverflow.com/questions/33630137/what-is-update-against-templates-in-pootle-2-7 Also Pootle is still Python 2 > > One catch though: each language has to be individually been updated. > Of course. > > After that has been done, syncing the updated files with Pootle is the last > > step. > The last step would be to export the new translations to SDF files and > to merge them with our code. True > > > > Cumbersome :-( > > Until we find someone who is willing to work on the process we are not > able to release 4.2.0 (after all these years). > > The PMC should stop ignoring this fact. > > Regards, > > Matthias I did manage to download nl and update the template with pot2po (all on my disk obviously) I just had a quick look at the difference between earlier SDF (2020) and the current one (2024) There seems to be a difference of sixty lines (60) Now the challenge is to find them :-) > > > > On 2024/07/26 15:26:49 Matthias Seidel wrote: > >> Hi Dick, > >> > >> Am 26.07.24 um 16:55 schrieb Dick Groskamp: > >>> On 2024/07/26 11:42:26 Matthias Seidel wrote: > >>>> Hi Dick, > >>>> > >>>> Am 26.07.24 um 09:22 schrieb Dick Groskamp: > >>>>> Matthias, > >>>>> > >>>>> I picked the SDF from trunk (nl lokalize.sdf) on 24-06-2024. It is > >>>>> dated 20200411. > >>>>> I think it is the most recent one. > >>>> Yes, the "most recent one" (for NL) is 4 years old... > >>>>> Problems I see is that they are also out of sync. > >>>>> nl Help-files are not in sync with SDF and also not with Pootle. > >>>> Everything is out of sync. > >>>>> For now I fixed the discrepancies by updating the Help-files and put > >>>>> them into the *.jars of the nl Help on my machine. That seems to work > >>>>> for now. > >>>>> I also plan to update Pootle with the corrections. That will be a > >>>>> manual task I'm afraid :-) > >>>> Translation in Pootle has always been a manual process? > >>> Yes, but I wonder how the strings from Pootle for nl ever got in > >>> Helpfiles :-) > >> The last export was done by an IBM employee in 2014. > >> > >> Then I spoke to Mechtilde in 2019 and she got the process running again, > >> but everything was manually. > >> > >> At one point the process broke (Pootle update?) and here we are. > >> > >>> I have no clue at all. After that then the Helpfiles are packaged somehow > >>> and delivered to the download package I assume > >>>>> Then, when translation process would work again, Pootle is in sync and > >>>>> updated, > >>>>> which should deliver correct sdf. > >>>> Whenever that will be... ;-) > >>> I haven't seen any new strings come in the last four/five years so I can > >>> slowly move forwards. > >> There were a lot of new strings in that time, but Pootle simply wasn't > >> updated. > >> > >>> One example: > >>> Image for STOP for BASIC macro (sc_basicstop.png) > >>> was sc_stop.png in nl Help file, showing nothing :-( > >> I *think* that was solved at one point, but the changes didn't make it > >> into Pootle. > >> > >> But you can always try the en-US build to see the actual development... > >> > >> BTW, SDF for en-US is not in our source, it gets exported weekly by our > >> buildbot: > >> > >> https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D > >> > >> Regards, > >> > >> Matthias > >> > >>>> Regards, > >>>> > >>>
Re: (openoffice) branch trunk updated: Removed some superfluous formatting
No problem. Should it go in AOO41x too ?? On 2024/08/16 12:31:48 Matthias Seidel wrote: > Hi Dick, > > Another good find! > > I would like to cherry-pick that for AOO42X, if you don't mind? > > Regards, > > Matthias > > Am 15.08.24 um 17:00 schrieb di...@apache.org: > > This is an automated email from the ASF dual-hosted git repository. > > > > digro pushed a commit to branch trunk > > in repository https://gitbox.apache.org/repos/asf/openoffice.git > > > > > > The following commit(s) were added to refs/heads/trunk by this push: > > new 5b7df03c0f Removed some superfluous formatting > > 5b7df03c0f is described below > > > > commit 5b7df03c0fc7e7e9269b3d60c906db77e70e2bfa > > Author: DiGro > > AuthorDate: Thu Aug 15 16:44:52 2024 +0200 > > > > Removed some superfluous formatting > > --- > > main/helpcontent2/source/text/shared/guide/print_faster.xhp | 6 ++ > > main/helpcontent2/source/text/shared/guide/space_hyphen.xhp | 3 +-- > > main/helpcontent2/source/text/shared/optionen/01010400.xhp | 3 +-- > > main/helpcontent2/source/text/smath/01/03090600.xhp | 6 ++ > > 4 files changed, 6 insertions(+), 12 deletions(-) > > > > diff --git a/main/helpcontent2/source/text/shared/guide/print_faster.xhp > > b/main/helpcontent2/source/text/shared/guide/print_faster.xhp > > index db2da07f7f..f468aaba54 100644 > > --- a/main/helpcontent2/source/text/shared/guide/print_faster.xhp > > +++ b/main/helpcontent2/source/text/shared/guide/print_faster.xhp > > @@ -51,11 +51,9 @@ > > > >> l10n="NEW">Click one of the following settings options: > > > > -Printer > > -- to define options for reducing data while printing directly > > to a printer > > +Printer - to define options for reducing data while printing > > directly to a printer > > > > -Print to file > > -- to define options for reducing data while printing to a > > file > > +Print to file - to define options for reducing data while > > printing to a file > > > > > >> l10n="NEW">Select any combination of the four options, then click > > OK. > > diff --git a/main/helpcontent2/source/text/shared/guide/space_hyphen.xhp > > b/main/helpcontent2/source/text/shared/guide/space_hyphen.xhp > > index 889a64f733..8cbd8c0af3 100644 > > --- a/main/helpcontent2/source/text/shared/guide/space_hyphen.xhp > > +++ b/main/helpcontent2/source/text/shared/guide/space_hyphen.xhp > > @@ -50,8 +50,7 @@ > >> l10n="U" oldref="62">Non-breaking dash > >> oldref="32">An example of a non-breaking dash is a company name such as > > A-Z. Obviously you would not want A- to appear at the end of a line and Z > > at the beginning of the next line. To solve this problem, press Shift+Ctrl+ > > minus sign. In other words, hold down the Shift and Ctrl keys and press the > > minus key. > >> l10n="U" oldref="65">Hyphen, dash > > - > oldref="66">In order to enter longer dashes, you can find under Tools > > - AutoCorrect Options > > -- Options the Replace dashes option. This option > > replaces one or two minus signs under certain conditions with an en-dash or > > an em-dash (see > name="$[officename] Help">$[officename] Help). > > + > oldref="66">In order to enter longer dashes, you can find under Tools > > - AutoCorrect Options - Options the Replace dashes > > option. This option replaces one or two minus signs under certain > > conditions with an en-dash or an em-dash (see > href="text/shared/01/06040100.xhp" name="$[officename] Help">$[officename] > > Help). > >> oldref="67">For additional replacements see the replacements table under > > Tools - AutoCorrect Options > > - > name="Replace">Replace. Here you can, among other > > things, replace a shortcut automatically by a dash, even in another > > font. > >> l10n="U" oldref="63">Definite separator > > diff --git a/main/helpcontent2/source/text/shared/optionen/01010400.xhp > > b/main/helpcontent2/source/text/shared/optionen/01010400.xhp > > index fe5e3dba65..3b679457ed 100644 > > --- a/main/helpcontent2/source/text/shared/optionen/01010400.xhp > > +++ b/main/helpcontent2/source/text/shared/optionen/01010400.xhp > > @@ -56,8 +56,7 @@ > > The > > configuration allows for two different directories: one folder where the > > user has write permissions, and one without write permissions. The user can > > only edit and delete the user dictionaries that are located in the writable > > path. Other dictionaries can be read only. > >> branch="hid/cui:PushButton:RID_SFXPAGE_LINGU:PB_LINGU_MODULES_EDIT" > > id="bm_id3154898" localize="false"/> > >> l10n="U" oldref="36">Edit > > - > oldref="37"> > hid="SVX_PUSHBUTTON_RID_SFXPAGE_LINGU_PB_LINGU_MODULES_EDIT">To edit a > > language module, select it and click Edit. The > href="text/shared/optionen/01010401.xhp" name="Edit > > Modules">Edit > > -Modules dialog appears. > > + > oldref="37"> > hid="SVX_PUSHBUTTON_RID_SFXPAGE_LINGU_PB_LINGU_MODULES_EDIT">To edit a > > language module, select it and cli
Re: (openoffice) branch trunk updated: Removed some superfluous formatting
OK, fine with me :-) On 2024/08/16 18:13:55 Matthias Seidel wrote: > Hi Dick, > > Am 16.08.24 um 20:11 schrieb Dick Groskamp: > > No problem. > OK, I will cherry-pick it now. > > Should it go in AOO41x too ?? > > No, the Help files are too different and in the end it would only end up > in en-US, since we do no translation for the branch anymore. > > We should concentrate on AOO42X. > > Regards, > > Matthias > > > > > On 2024/08/16 12:31:48 Matthias Seidel wrote: > >> Hi Dick, > >> > >> Another good find! > >> > >> I would like to cherry-pick that for AOO42X, if you don't mind? > >> > >> Regards, > >> > >> Matthias > >> > >> Am 15.08.24 um 17:00 schrieb di...@apache.org: > >>> This is an automated email from the ASF dual-hosted git repository. > >>> > >>> digro pushed a commit to branch trunk > >>> in repository https://gitbox.apache.org/repos/asf/openoffice.git > >>> > >>> > >>> The following commit(s) were added to refs/heads/trunk by this push: > >>>new 5b7df03c0f Removed some superfluous formatting > >>> 5b7df03c0f is described below > >>> > >>> commit 5b7df03c0fc7e7e9269b3d60c906db77e70e2bfa > >>> Author: DiGro > >>> AuthorDate: Thu Aug 15 16:44:52 2024 +0200 > >>> > >>> Removed some superfluous formatting > >>> --- > >>>main/helpcontent2/source/text/shared/guide/print_faster.xhp | 6 ++ > >>>main/helpcontent2/source/text/shared/guide/space_hyphen.xhp | 3 +-- > >>>main/helpcontent2/source/text/shared/optionen/01010400.xhp | 3 +-- > >>>main/helpcontent2/source/text/smath/01/03090600.xhp | 6 ++ > >>>4 files changed, 6 insertions(+), 12 deletions(-) > >>> > >>> diff --git a/main/helpcontent2/source/text/shared/guide/print_faster.xhp > >>> b/main/helpcontent2/source/text/shared/guide/print_faster.xhp > >>> index db2da07f7f..f468aaba54 100644 > >>> --- a/main/helpcontent2/source/text/shared/guide/print_faster.xhp > >>> +++ b/main/helpcontent2/source/text/shared/guide/print_faster.xhp > >>> @@ -51,11 +51,9 @@ > >>> > >>> >>> l10n="NEW">Click one of the following settings options: > >>> >>> l10n="NEW"> > >>> -Printer > >>> -- to define options for reducing data while printing > >>> directly to a printer > >>> +Printer - to define options for reducing data while > >>> printing directly to a printer > >>> >>> l10n="NEW"> > >>> -Print to file > >>> -- to define options for reducing data while printing to a > >>> file > >>> +Print to file - to define options for reducing data while > >>> printing to a file > >>> > >>> > >>> >>> l10n="NEW">Select any combination of the four options, then click > >>> OK. > >>> diff --git a/main/helpcontent2/source/text/shared/guide/space_hyphen.xhp > >>> b/main/helpcontent2/source/text/shared/guide/space_hyphen.xhp > >>> index 889a64f733..8cbd8c0af3 100644 > >>> --- a/main/helpcontent2/source/text/shared/guide/space_hyphen.xhp > >>> +++ b/main/helpcontent2/source/text/shared/guide/space_hyphen.xhp > >>> @@ -50,8 +50,7 @@ > >>> >>> l10n="U" oldref="62">Non-breaking dash > >>> >>> l10n="U" oldref="32">An example of a non-breaking dash is a company name > >>> such as A-Z. Obviously you would not want A- to appear at the end of a > >>> line and Z at the beginning of the next line. To solve this problem, > >>> press Shift+Ctrl+ minus sign. In other words, hold down the Shift and > >>> Ctrl keys and press the minus key. > >>> >>> l10n="U" oldref="65">Hyphen, dash > >>> - >>> l10n="CHG" oldref="66">In order to enter longer dashes, you can find > >>> under Tools - AutoCorrect Options > >>> -- Options the Replace dashes option. This > >>> option replaces one or two minus signs under certain conditions with an > >>> en-dash or an em-dash (see >>> name="$[officename] Help">$[officename] Help). > >>> + >
Re: Question to all developers and translators: How integrated should translation be ?
Op 6-9-2013 14:30, janI schreef: Hi I am copying this mail to the l10n list, in order to involve the translators that do not follow dev@. But lets please keep the discussion on dev@. As its hopefully known, I have been working on a new workflow for the whole translation process for quite a long time. Now I have released the first major part of the workflow, my ultimate commit has lead to some valid concerns from Jürgen and Herbert, this is the second time (during development) that I hear the essentially same concern. Therefore we a a community need to decide which road we want to follow. The workflow I am developing, would in the final phase look like (without technical details). 1) at regular intervals en-US text are extracted from our source tree, transferred to pootle as templates, and all languages are updates with new/changed/deleted keys. This part is partly manual (starting the build, updating the languages). 2) Translators work on pootle, Translator-comitters update languages in svn from pootle and start an offline language-pack build. 3) Translators test their translation using the binary from our buildbot + language pack (translators debug tool). Turnaround time < 1 day. 4) Buildbot automatically include changed translations on regular builds (e.g. weekly). The 2 concerns that have been raised are: 1) Letting committers do "svn commit" and "svn up" directly in pootle, might produce a build breaker for our buildbots. Suggestion let an admin do it e.g. once a week. my opinion: We do not need an admin in the loop, we dont have a controlling for developers and they are even more likely to produce build breakers. Remember a .po file build breaker will only affect the language in question and can be repaired just as fast. 2) Containing the .po files (translations) inside main/ cost 600Mb extra for en-US developers to download. Suggestion keep the .po file away from main in extras. my opion: Translator work is NOT "extra", its an essential needed part for our builds. In contrast to e.g. cliparts, the .po are part of the setup package (of course transformed, similar to a C++ source). My workflow can work, not as efficient with 1), but 2) breaks the workflow for technical reasons (think of someone extracting en-US strings from an updated /main to an old /extra and the published it to pootle == LOT of extra translation in all languages. I see translators working at the same level as developers, not as something /extras, and therefore the work should be treated as such. I have stopped work on further integration of genLang, until I either get lazy consensus on my workflow, or we decide to go for another workflow. thanks in advance for your comments (please all on dev@). rgds jan I. In general I have no problem with this workflow and think it might speed up things for the builders side of the proces. The only problem I have is that I'm no techie and SVN is, to be honest, to complicated for me. Would it be possible, for instance after the deadline for translation has passed, for a builder/developer/admin to update ALL languages from POOTLE? I think with something like that we would have have ALL alterations into SVN at once. Mind you I have no idea how much work that would be, but it seems to me it gives some assurance about the imported strings. -- DiGro ___ Apache OpenOffice 4.0.0 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Testing for OpenOffice 4.0.1 (RC) Start! Call for volunteers!
I'll give it a try Testlink-ID ; DiGro Platform: Windows 7 -- DiGro ___ Apache OpenOffice 4.0.0 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Reporting a problem with the OpenOffice website (could use Dutch translator help)
Kay, what is the problem? I'll see if I canhelp you out -- DiGro ___ Apache OpenOffice 4.0.0 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE]: Release Apache OpenOffice 4.0.1 (RC3)
+1 -- DiGro ___ Apache OpenOffice 4.0.0 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE 4.0.1][Product Update Notification Service] updated XML feeds for the former versions to be notified about version 4.0.1
Dutch landing pages changed and published -- DiGro ___ Apache OpenOffice 4.0.0 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CWiki] new default access rights active
Please whitelist me username: digro Full name: Dick Groskamp DiGro ___ Apache OpenOffice 4.0.1 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [LAZY CONSENSUS] maintenance of ooo-wiki2-vm.a.o and ooo-forums.a.o
+1 -- DiGro ___ Apache OpenOffice 4.0.1 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Labels
Jane, you have probably not yet registered your database within AOO. Take a look here: http://www.oooforum.org/forum/viewtopic.phtml?t=112224&highlight=labels+register That should set you on the right track (cc-ed OP) -- DiGro ___ Apache OpenOffice 4.0.1 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE] Dennis Hamilton as new AOO Chair.
Please vote [X] +1, I want Dennis Hamilton as new Chair [ ] +0, I do not care if Dennis Hamilton becomes new Chair [ ] -1, I am against Dennis Hamilton becomes new chair (out of curtesy, please add another suggestion). -- DiGro ___ Apache OpenOffice 4.1.1 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: FW: Internationalization of 4.1.2-patch1 (was RE: a question about "APPLY-4.1.2-patch1.bat")
Op 20-8-2016 om 21:49 schreef Dennis E. Hamilton: https://dist.apache.org/repos/dist/dev/openoffice/4.1.2- >patch1/hotfix.html I've translated README, APPLY.bat (messages) and REVERT.bat (messages) into Dutch I've adjusted the page Jörg made at CWIKI with a table to register translations. Two questions though: 1. do you only need the messages from APPLY.bat and REVERT.bat or can I sent the complete file somewhere ? 2. where do I put the translations. I'm not that a tech savvy Greetings -- DiGro ___ Apache OpenOffice 4.0.1 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: FW: Internationalization of 4.1.2-patch1 (was RE: a question about "APPLY-4.1.2-patch1.bat")
Dutch translated files added to issue 127084 (https://bz.apache.org/ooo/show_bug.cgi?id=127084) -- DiGro ___ Apache OpenOffice 4.1.2 (Dutch) and scanned with Ziggo extended security (F-Secure)
Re: Editing the release notes wiki
Added Patricia's draft text to the template for Release notes 4.1.3. -- DiGro ___ Apache OpenOffice 4.1.2 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Testing 4.1.3 - release notes
Op 11-10-2016 om 23:11 schreef Marcus: Am 10/04/2016 10:29 PM, schrieb Marcus: OK, binary and source code testing is on a good way. What about the release notes. Are these somewhere reachable/readable already? Hi Dirk and Joerg, we have finished the release notes. Please check if you need to incorporate the latest changes into your translations. Thanks Marcus Done -- DiGro ___ Apache OpenOffice 4.1.2 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: error on MWiki link
Peter/Matthias,
the used template is: https://wiki.openoffice.org/wiki/Template:Uno/UDKlink
This contains a hardcoded link:
[http://{{{2|udk}}}.openoffice.org/source/browse/{{{2|udk}}}/{{{1}}}
{{{2|udk}}}/{{{1}}}][[Category:Wiki Templates]]
I suppose that the path to /source/browse no longer exists.
Can't find anything that looks like it
--
DiGro
___
Apache OpenOffice 4.1.6 (Dutch) and scanned with Ziggo Safe Online (F-Secure)
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
GSIcheck lost - does someone have a spare ?
Due to a crash of my old computer I lost GSIcheck. Link http://ooo.services.openoffice.org/gsicheck/ is no longer working Does anyone know where I can download it ? -- DiGro ___ Apache OpenOffice 4.1.6 (Dutch) and scanned with Ziggo Safe Online (F-Secure)
Re: GSIcheck lost - does someone have a spare ?
Mechtilde, thanks, but that was not my intention. GSIcheck was (as far as I know) a separate program, version 1.9.0 being the last I think, and was zipped and hosted on the ooo.services. That services are dead and there is no way to obtain the packed program I'm afraid. So I was actually looking for someone who still had the zipped program. Or is it obtainable from wthout the build environment (not really a techie this one so :-( ) I would like to have it again to perform some tests on translations in Pootle to look for warnings/errors -- DiGro ___ Apache OpenOffice 4.1.6 (Dutch) and scanned with Ziggo Safe Online (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: GSIcheck lost - does someone have a spare ?
Op 9-9-2019 om 19:58 schreef denni...@libre.ce.org: Am 09.09.2019 14:37, schrieb Dick Groskamp: Due to a crash of my old computer I lost GSIcheck. Link http://ooo.services.openoffice.org/gsicheck/ is no longer working Does anyone know where I can download it ? Try that link: http://web.archive.org/web/20100108222913/http://ooo.services.openoffice.org/gsicheck/ Dennis, thanks for the link. Unfortunately they don't seem to work anymore. Downloaded the files but they can't be unpacked (not a valid archive) -- DiGro ___ Apache OpenOffice 4.1.6 (Dutch) and scanned with Ziggo Safe Online (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Where did the "old" CMS go to ? Can't find it :-)
Can anyone tell me where the old CMS was moved to ? Ik know it went to Git/Github but I can't seem to fiond it. Noticed that 4.1.7 was out but the Dutch webpage still mentions some 4.1.6-text on the page. Want to commit a pull request for that, but since I can't find it :-( -- DiGro ___ Apache OpenOffice 4.1.6 (Dutch) and scanned with Ziggo Safe Online (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Where did the "old" CMS go to ? Can't find it :-)
Thanks Matthias. -- DiGro ___ Apache OpenOffice 4.1.6 (Dutch) and scanned with Ziggo Safe Online (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.1.8 Release Notes - draft
Fixed the entries mentioned bij Czeslaw On 2020/10/12 14:49:01, Matthias Seidel wrote: > Hi, > > Am 12.10.20 um 16:44 schrieb Czesław Wolański: > > Hi Matthias, > > > >> You might not know, but as a committer > >> you can log into cWiki by using > >> your ASF credentials. > > Yes, I might not know, with emphasis placed on "might". > > Better late then ever. ;-) > > Shouldn't that be "than never" then? ;-) > > Regards, > > Matthias > > > > > > > Regards, > > Czesław > > > > > > пн, 12 окт. 2020 г. в 16:10, Matthias Seidel : > > > >> Hi Czesław, > >> > >> Am 12.10.20 um 13:36 schrieb Czesław Wolański: > >>> Hi, > >>> > >>> Draft AOO 4.1.8 Release Notes, section "Known Issues" - "For macOS > >> users": > >>> *1. Space* > >>> Space is needed in "password.This". > >>> (space is present in AOO 4.1.7 Release Notes) > >>> > >>> *2. "than"* > >>> > >>> I suspect that "than" is inappropriate in the sentence: > >>> > >>>"If not able to upgrade to Java 9 than install the legacy version of > >>> Apple Java from the following link: Legacy Apple Java 6." > >>> > >>> "than" is also in AOO 4.1.7 Release Notes. Could it be changed to > >> "then"? ( > >>> Better late then ever ;‑) ). > >> Hawkeye... ;-) > >> > >> You might not know, but as a committer you can log into cWiki by using > >> your ASF credentials. > >> > >> You should be able to edit it then. > >> > >> Regards, > >> > >>Matthias > >> > >>> See image file available at the following link: > >>> > >>> > >> https://drive.google.com/file/d/1rR3j8PGvyzfydZMxG8X31e2T80nFTmR1/view?usp=sharing > >>> > >>> Regards, > >>> Czesław Wolański > >>> > >> > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: references to OpenOffice.org in the wiki
On 2020/11/17 11:49:34, "John D'Orazio"
wrote:
> I see that in the wiki pages at https://wiki.openoffice.org/wiki/ there are
> still many references to OpenOffice.org . Am I correct in understanding
> that this was the old brand name, and now it would be more correct to refer
> to "Apache OpenOffice" or more simply "OpenOffice"? Is it alright if I
> change the references from OpenOffice.org to Apache OpenOffice or simply
> OpenOffice?
>
> --
> John R. D'Orazio
> John,
OpenOffice is the registered brand of a company in the Netherlands so you can't
use that.
Most (a lot) of references are inserted with the template {{OOo}} which is
short for OpenOffice.org
Some time ago someone entered the template {{AOo}} which is short for Apache
OpenOffice
You can replace {{OOo}} by {{AOo}} and your done :-)
Otherwise, replace OpenOffice.org by {{AOo}}
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Request of support for open office calc
On 2020/12/05 19:03:27, Eliodoro MIRANDA wrote: > I am studyng now CALC but i need support. > I have been searching in the web but I dont get the solution. > I have found a forum also in italian but I don't succeed to register in it. > Can you advise me.if there is a contact I can reach in Italy? > Thanks > Eliodoro Miranda > Italian forum is on : https://forum.openoffice.org/it/forum/ Might be a moderated list which means that once you have registered the moderator has to approve, they will then send you a notification. Otherwise, users list is: us...@openoffice.apache.org (english) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/08 14:57:16, Matthias Seidel wrote: > Hi all, > > That seems to be another one of these pages that appear to be blank > because of a missing Wiki plugin. > > After all these years, can we get the Wiki fully functional again? > > Regards, > > Matthias > > Am 08.12.20 um 14:56 schrieb r_muell...@web.de: > > Subject: > > Fwd: Broken_Link: > > "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208- > > Matthias, I think the problem is that the only existing item for that extension is in the configuration of MediaWiki. Nobody seems to have a copy of it, anywhere. Hoping that one of the sysops can retrieve it from there and secure it in one of our vaults :-) Greetings, > > > > > > Weitergeleitete Nachricht > > Betreff: Broken_Link: > > "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"; > > > > Datum: Tue, 24 Nov 2020 14:47:15 +0100 > > Von: r_muell...@web.de > > An: info...@wikimedia.org > > Kopie (CC): r_muell...@web.de > > > > Unter anderen ist in der "Open Office"-Dokumentation > > der nachfolgend Link nicht erreichbar (Link not reachable): > > > > > > https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic > > > > > > > > > > Mit freundlichen Grüßen > > Reinhard Müller > > r_muell...@web.de > > > > > > > > - > > 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: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/08 13:56:41, "r_muell...@web.de" wrote: > Subject: > Fwd: Broken_Link: > "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208- > > > Weitergeleitete Nachricht > Betreff: Broken_Link: > "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"; > Datum: Tue, 24 Nov 2020 14:47:15 +0100 > Von: r_muell...@web.de > An: info...@wikimedia.org > Kopie (CC): r_muell...@web.de > > Unter anderen ist in der "Open Office"-Dokumentation > der nachfolgend Link nicht erreichbar (Link not reachable): > > > https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic > > > > Mit freundlichen Grüßen > Reinhard Müller > r_muell...@web.de > > I fixed it. It should be accessible now. Seems that the IDLTags extension in MediaWiki partially functions. tags do work. tags don't work (changed to normal link) tags don't work. (changed to normal link) I walked through the Developers Guide and all seems to be accessible now. I will check once again tomorrow - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/08 18:56:25, Carl Marcum wrote: > > There are still hundreds of broken pages in the dev guide. > Yes it seems to be idls and ildm tags. > > There is a new upgraded VM setup for the wiki waiting to get changed to > but I had hoped to look into before it get switched over. > But I have had limited time and I haven't been able to do any testing > with it since the URL is being redirected. > I don't know anything about MediaWiki extensions, yet anyway :) > > The Infra ticket for our VM is [1]. > > The only place I know where the code is in the current wiki under: > extensions/OOoIDLtags/OOoIDLtags.php > > > [1] https://issues.apache.org/jira/browse/INFRA-20339 > > Best regards, > Carl > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > Carl, thanks i will check into it. Is it possible to export/copy the IDLTags extension from the MWiki to a more accessible place ? That way it might be accessible for editing or reversed engineering. I think for now it is not reachable. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Fixing not showing pages of DevGuide
Started this morning to fix the pages that are not showing in the DevGuide. Due to a broken extension tags , and prevent pages from displaying content. However, content is there. Content is editable by tweaking the URL of the not showing page For instance: https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic needs to become: https://wiki.openoffice.org/w/index.php?title=Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic&action=edit so: replacing wiki/ by w/index.php?title= and add &action=edit to the end of the URL. Content is then editable. tag can be changed to to make it work again tag and need to be replaced by an url to the page. Like [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XMultiComponentFactory.html#createInstanceWithContext, followed by the content of the tag en closing bracket ] Like [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XMultiComponentFactory.html#createInstanceWithContext com.sun.star.lang.XMultiComponentFactory:createInstanceWithContext] It is a manual job and there are a lot of pages. (I'll be busy :-) ) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/09 11:34:03, Carl Marcum wrote:
> Hi Dick,
>
> I have copied it out and it's contents are below.
>
> It should be in github or svn but I haven't had time to do anything with it.
>
> On 12/9/20 5:42 AM, Dick Groskamp wrote:
> >
> > On 2020/12/08 18:56:25, Carl Marcum wrote:
> >> There are still hundreds of broken pages in the dev guide.
> >> Yes it seems to be idls and ildm tags.
> >>
> >> There is a new upgraded VM setup for the wiki waiting to get changed to
> >> but I had hoped to look into before it get switched over.
> >> But I have had limited time and I haven't been able to do any testing
> >> with it since the URL is being redirected.
> >> I don't know anything about MediaWiki extensions, yet anyway :)
> >>
> >> The Infra ticket for our VM is [1].
> >>
> >> The only place I know where the code is in the current wiki under:
> >> extensions/OOoIDLtags/OOoIDLtags.php
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/INFRA-20339
> >>
> >> Best regards,
> >> Carl
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >>
> > Carl, thanks i will check into it.
> >
> > Is it possible to export/copy the IDLTags extension from the MWiki to a
> > more accessible place ?
> > That way it might be accessible for editing or reversed engineering. I
> > think for now it is not reachable.
> >
> >
> The filename is OOoIDLtags.php
>
> /**
> * IDL Tag extension
> * The IDLTagExtension was written to manage the IDL links in the
> OpenOffice.org Developer's Guide.
> * The extension converts Java paths to links back to the online IDL
> documentation.
> * @version 1.0.2
> * @link http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
> */
>
> if ( !defined( 'MEDIAWIKI' ) ) {
> die( 'This file is a MediaWiki extension, it is not a valid entry
> point' );
> }
>
> // Extension credits that will show up on Special:Version
> $wgExtensionCredits['parserhook'][] = array(
> 'name' => 'IDL Tags',
> 'version' => '1.0.2',
> 'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
> 'description' => 'Manage the IDL links in the OOo Dev Guide ',
> 'url' =>
> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
> );
>
> global $wgExtIDLtags;
> $wgExtIDLtags = new RenderIDLtags;
> $wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );
>
> class RenderIDLtags {
>
> function oooIDLTags() {
> global $wgParser;
> $wgParser->setHook( 'idl', array( &$this, 'renderIDL' ) );
> $wgParser->setHook( 'idlm', array( &$this, 'renderIDLM' ) );
> $wgParser->setHook( 'idls', array( &$this, 'renderIDLS' ) );
> $wgParser->setHook( 'idlmodule', array( &$this,
> 'renderIDLMODULE' ) );
> $wgParser->setHook( 'idltopic', array( &$this, 'renderIDLTOPIC'
> ) );
> }
>
> function renderIDL( $input, $args, $parser ) {
> $parser->disableCache();
> $output = $parser->recursiveTagParse( $input );
> $output = 'http://api.openoffice.org/docs/common/ref/' .
> str_replace ('.','/',$output).'.html" class="external
> text">'.$output.'';
> return $output;
> }
>
> function renderIDLM( $input, $args, $parser ) {
> $parser->disableCache();
> $output = $parser->recursiveTagParse( $input );
> $page = ereg_replace ('\.','/',$output);
> $anchor = ereg_replace (':','.html#',$page);
> $function = ereg_replace ('^.*:','',$page);
> $output = 'http://api.openoffice.org/docs/common/ref/' .
> $anchor.'" class="external text">'.$function.'';
> return $output;
> }
>
> function renderIDLS( $input, $args, $parser ) {
> $parser->disabl
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/10 01:09:49, Carl Marcum wrote:
> Hi Arrigo,
>
>
> On 12/9/20 2:51 PM, Arrigo Marchiori wrote:
> > Hello,
> >
> > trying a shot in the dark...
> >
> > On Wed, Dec 09, 2020 at 05:24:41PM -, Dick Groskamp wrote:
> >
> >> On 2020/12/09 11:34:03, Carl Marcum wrote:
> >>> Hi Dick,
> >>>
> >>> I have copied it out and it's contents are below.
> >>>
> >>> On 12/9/20 5:42 AM, Dick Groskamp wrote:
> >>>> On 2020/12/08 18:56:25, Carl Marcum wrote:
> >>>>> There are still hundreds of broken pages in the dev guide.
> >>>>> Yes it seems to be idls and ildm tags.
> > [...]
> >>> function renderIDLM( $input, $args, $parser ) {
> >>> $parser->disableCache();
> >>> $output = $parser->recursiveTagParse( $input );
> >>> $page = ereg_replace ('\.','/',$output);
> >>> $anchor = ereg_replace (':','.html#',$page);
> >>> $function = ereg_replace ('^.*:','',$page);
> > [...]
> >> Thanks,
> >> now I only have to figure out why it isn't working :-)
> > Could the culprit be the deprecated ereg_replace function, that was
> > removed since PHP 7.0.0?
> >
> > Pointers:
> > https://www.php.net/manual/en/function.ereg-replace.php
> > https://stackoverflow.com/questions/3649574/replace-ereg-replace-with-preg-replace
> >
> > HTH,
> Thanks for the tip.
>
> If I can get the redirect removed from the new mwiki VM I can try that.
>
> Best regards,
> Carl
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
Carl, would it then make sense to stop changing the tags to hardcoded urls and
wait to see if replacing ereg_replace works?
If that should be a yes should I than revert the changes I have already made ?
I think Rigo has a point since we use PHP 7.0.33 on the wiki, which has
ereg_replace removed.
If it won't work I can always resume changing again.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/09 19:51:57, Arrigo Marchiori wrote:
> Hello,
>
> trying a shot in the dark...
>
> On Wed, Dec 09, 2020 at 05:24:41PM -, Dick Groskamp wrote:
>
> > On 2020/12/09 11:34:03, Carl Marcum wrote:
> > > Hi Dick,
> > >
> > > I have copied it out and it's contents are below.
> > >
> > > On 12/9/20 5:42 AM, Dick Groskamp wrote:
> > > >
> > > > On 2020/12/08 18:56:25, Carl Marcum wrote:
> > > >> There are still hundreds of broken pages in the dev guide.
> > > >> Yes it seems to be idls and ildm tags.
>
> [...]
> > > function renderIDLM( $input, $args, $parser ) {
> > > $parser->disableCache();
> > > $output = $parser->recursiveTagParse( $input );
> > > $page = ereg_replace ('\.','/',$output);
> > > $anchor = ereg_replace (':','.html#',$page);
> > > $function = ereg_replace ('^.*:','',$page);
> [...]
> > Thanks,
> > now I only have to figure out why it isn't working :-)
>
> Could the culprit be the deprecated ereg_replace function, that was
> removed since PHP 7.0.0?
>
> Pointers:
> https://www.php.net/manual/en/function.ereg-replace.php
> https://stackoverflow.com/questions/3649574/replace-ereg-replace-with-preg-replace
>
> HTH,
> --
> rigo
>
> http://rigo.altervista.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
That might probably also be the reason why the tag does work. It uses
str_replace and NOT ereg_replace.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/10 13:57:39, Dick Groskamp wrote:
>
>
> On 2020/12/09 19:51:57, Arrigo Marchiori wrote:
> > Hello,
> >
> > trying a shot in the dark...
> >
> > On Wed, Dec 09, 2020 at 05:24:41PM -, Dick Groskamp wrote:
> >
> > > On 2020/12/09 11:34:03, Carl Marcum wrote:
> > > > Hi Dick,
> > > >
> > > > I have copied it out and it's contents are below.
> > > >
> > > > On 12/9/20 5:42 AM, Dick Groskamp wrote:
> > > > >
> > > > > On 2020/12/08 18:56:25, Carl Marcum wrote:
> > > > >> There are still hundreds of broken pages in the dev guide.
> > > > >> Yes it seems to be idls and ildm tags.
> >
> > [...]
> > > > function renderIDLM( $input, $args, $parser ) {
> > > > $parser->disableCache();
> > > > $output = $parser->recursiveTagParse( $input );
> > > > $page = ereg_replace ('\.','/',$output);
> > > > $anchor = ereg_replace (':','.html#',$page);
> > > > $function = ereg_replace ('^.*:','',$page);
> > [...]
> > > Thanks,
> > > now I only have to figure out why it isn't working :-)
> >
> > Could the culprit be the deprecated ereg_replace function, that was
> > removed since PHP 7.0.0?
> >
> > Pointers:
> > https://www.php.net/manual/en/function.ereg-replace.php
> > https://stackoverflow.com/questions/3649574/replace-ereg-replace-with-preg-replace
> >
> > HTH,
> > --
> > rigo
> >
> > http://rigo.altervista.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
> >
> That might probably also be the reason why the tag does work. It uses
> str_replace and NOT ereg_replace.
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
Just tested with a page with just one tag .
Changing it to renders the page correctly.
Changing to does NOT render the page, nor does
Seems to me that ereg_replace is the culprit, but I'm no developer, nor
technician
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/10 23:12:06, Carl Marcum wrote:
> Hi Dick,
>
> On 12/10/20 8:27 AM, Dick Groskamp wrote:
> >
> > On 2020/12/10 01:09:49, Carl Marcum wrote:
> >> Hi Arrigo,
> >>
> >>
> >> On 12/9/20 2:51 PM, Arrigo Marchiori wrote:
> >>> Hello,
> >>>
> >>> trying a shot in the dark...
> >>>
> >>> On Wed, Dec 09, 2020 at 05:24:41PM -, Dick Groskamp wrote:
> >>>
> >>>> On 2020/12/09 11:34:03, Carl Marcum wrote:
> >>>>> Hi Dick,
> >>>>>
> >>>>> I have copied it out and it's contents are below.
> >>>>>
> >>>>> On 12/9/20 5:42 AM, Dick Groskamp wrote:
> >>>>>> On 2020/12/08 18:56:25, Carl Marcum wrote:
> >>>>>>> There are still hundreds of broken pages in the dev guide.
> >>>>>>> Yes it seems to be idls and ildm tags.
> >>> [...]
> >>>>> function renderIDLM( $input, $args, $parser ) {
> >>>>> $parser->disableCache();
> >>>>> $output = $parser->recursiveTagParse( $input );
> >>>>> $page = ereg_replace ('\.','/',$output);
> >>>>> $anchor = ereg_replace (':','.html#',$page);
> >>>>> $function = ereg_replace ('^.*:','',$page);
> >>> [...]
> >>>> Thanks,
> >>>> now I only have to figure out why it isn't working :-)
> >>> Could the culprit be the deprecated ereg_replace function, that was
> >>> removed since PHP 7.0.0?
> >>>
> >>> Pointers:
> >>> https://www.php.net/manual/en/function.ereg-replace.php
> >>> https://stackoverflow.com/questions/3649574/replace-ereg-replace-with-preg-replace
> >>>
> >>> HTH,
> >> Thanks for the tip.
> >>
> >> If I can get the redirect removed from the new mwiki VM I can try that.
> >>
> >> Best regards,
> >> Carl
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> > Carl, would it then make sense to stop changing the tags to hardcoded urls
> > and wait to see if replacing ereg_replace works?
> > If that should be a yes should I than revert the changes I have already
> > made ?
> >
> > I think Rigo has a point since we use PHP 7.0.33 on the wiki, which has
> > ereg_replace removed.
> > If it won't work I can always resume changing again.
> >
>
> I started down this road back in May [1] and soon discovered there are
> hundreds of affected pages in the dev guide alone.
> If I thought we couldn't fix it I would say go ahead.
>
> I found out at the same time a new VM was being provisioned for us with
> an updated OS so I have access to that machine to look into this.
> I ran into a roadblock in that the URL I should be able to see the test
> wiki is being redirected.
>
> I've been occupied with other things in the meantime at let it slide but
> now that the subject has come up again it would be good to put it to
> rest one way or another.
> Last night I put in a ticket to have the redirect removed so I can see
> the results of any changes.
>
> I can change that method call and see if that works once I can see the
> test wiki.
> I'm hesitant to make the change live on our production instance however.
>
> [1]
> https://lists.apache.org/thread.html/rda96615951628eb0fafc004a8f0aa1177559fd3b5d9c9f30ce9cebc9%40%3Cdev.openoffice.apache.org%3E
>
> Best regards,
> Carl
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
Carl,
thanks for the response. I must have been hibernating in May. Missed that
completely. ;-)
I'm no tech or programmer but replacing ereg_replace by pereg_replace (which
should work on > PHP 7.0.*) seems to be the best and fastest way to correct
this.
Since IDLTags is "just" a way to put rendering or format on to the tags it
probably won't affect the actual text in the wiki. No big impact on the
existing wiki I think. Just my 2 cents
If that works, everything is OK and we don't have to change anything more.
If it fails we can put the old OOoIDLTags.php back I should think. Then we
should replace all the failing tags , and .
seems to do nothing.
I will look into pereg_replace today to see if I can help make it function
again.
Let me know if I can do anything else to help.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fixing not showing pages of DevGuide
On 2020/12/10 19:13:38, "Keith N. McKenna" wrote: > On 12/9/2020 11:42 AM, Dick Groskamp wrote: > > Started this morning to fix the pages that are not showing in the DevGuide. > > Due to a broken extension tags , and prevent pages > > from displaying content. > > > > However, content is there. > > Content is editable by tweaking the URL of the not showing page > > > > For instance: > > https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic > > > > needs to become: > > https://wiki.openoffice.org/w/index.php?title=Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic&action=edit > > > > so: replacing wiki/ by w/index.php?title= and add &action=edit to the end > > of the URL. > > > > Content is then editable. > > > > tag can be changed to to make it work again > > tag and need to be replaced by an url to the page. > > > > Like > > [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XMultiComponentFactory.html#createInstanceWithContext, > > followed by the content of the tag en closing bracket ] > > > > Like > > [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XMultiComponentFactory.html#createInstanceWithContext > > com.sun.star.lang.XMultiComponentFactory:createInstanceWithContext] > > > > It is a manual job and there are a lot of pages. (I'll be busy :-) ) > > > Dick; I will be more than happy to help if you would like to coordinate > what is done and what we each can do. > > Regards > Keith > > > Keith, thanks for the offer, much appreciated. In the other thread https://lists.apache.org/thread.html/r9b07bbcb478d65bb24cb34e41d2dbd68ee6a36ddc734befe391a3148%40%3Cdev.openoffice.apache.org%3E I'm talking to Carl to see if it is possible to make a change to the extension IDLTags by replacing the obsolete ereg_replace function by pereg_replace function, which should work on PHP > 7.0.* My suggestion is to see/wait if that is possible on a short term and if not, or if it won't work, to go on with replacing the tags , and by hardcoded URLs. The tag is still working, probably because it uses str_replace function and not the obsolete ereg_replace function. Most frequent tag seems to be , but the problem is that if one of the other tags is on the same page the whole page won't show. I hope someone with more knowledge of PHP can help us with this on the short term. In the mean time I will check the pages to see where the conflicting tags are, so we have a kind of index to the pages we might have to change. That way we have an impression on how much there is to do and how we, if necessary, can divide the workload. Does that make sense ? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/11 15:01:35, Matthias Seidel wrote: > Hi Peter, > > I am not sure what you are talking about here... > > The discussion is about a non working extension for our Wiki server. > > The repository is for our Media Wiki extension? > > 2 totally different things... > > Matthias > > Am 11.12.20 um 12:22 schrieb Peter Kovacs: > > I have created the Repository for MWiki extensions with my Proposed name: > > > > openoffice-mwiki-ext.git > > <https://gitbox.apache.org/repos/asf/openoffice-mwiki-ext.git> > > > > It is ready to add our MWiki extensions. > > > > > > On 10.12.20 20:35, Keith N. McKenna wrote: > >> On 12/9/2020 5:38 PM, Marcus wrote: > >>> Am 09.12.20 um 18:35 schrieb Peter Kovacs: > >>>> How about we create a OpenOffice-Mwiki-ext Repo in gitbox? > >>>> > >>>> We could do the same for the forums customizations. > >>>> > >>>> So we have more control over our support code. > >>> +1 > >>> This increases the chance that also others can have a look and give > >>> some > >>> hints when problems arise. > >>> > >>> Marcus > >>> > >> +1 > >> > >> Keith > >>> > >>>> On 09.12.20 18:24, Dick Groskamp wrote: > >>>>> On 2020/12/09 11:34:03, Carl Marcum wrote: > >>>>>> Hi Dick, > >>>>>> > >>>>>> I have copied it out and it's contents are below. > >>>>>> > >>>>>> It should be in github or svn but I haven't had time to do anything > >>>>>> with it. > >>>>>> > >>>>>> On 12/9/20 5:42 AM, Dick Groskamp wrote: > >>>>>>> On 2020/12/08 18:56:25, Carl Marcum wrote: > >>>>>>>> There are still hundreds of broken pages in the dev guide. > >>>>>>>> Yes it seems to be idls and ildm tags. > >>>>>>>> > >>>>>>>> There is a new upgraded VM setup for the wiki waiting to get > >>>>>>>> changed to > >>>>>>>> but I had hoped to look into before it get switched over. > >>>>>>>> But I have had limited time and I haven't been able to do any > >>>>>>>> testing > >>>>>>>> with it since the URL is being redirected. > >>>>>>>> I don't know anything about MediaWiki extensions, yet anyway :) > >>>>>>>> > >>>>>>>> The Infra ticket for our VM is [1]. > >>>>>>>> > >>>>>>>> The only place I know where the code is in the current wiki under: > >>>>>>>> extensions/OOoIDLtags/OOoIDLtags.php > >>>>>>>> > >>>>>>>> > >>>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-20339 > >>>>>>>> > >>>>>>>> Best regards, > >>>>>>>> Carl > >>>>>>>> > >>>>>>>> > >>>>>>>> - > >>>>>>>> > >>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >>>>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org > >>>>>>>> > >>>>>>>> > >>>>>>> Carl, thanks i will check into it. > >>>>>>> > >>>>>>> Is it possible to export/copy the IDLTags extension from the MWiki > >>>>>>> to a more accessible place ? > >>>>>>> That way it might be accessible for editing or reversed > >>>>>>> engineering. I think for now it is not reachable. > >>>>>>> > >>>>>>> > >>>>>> The filename is OOoIDLtags.php > >>>>>> > >>>>>> >>>>>> /** > >>>>>> * IDL Tag extension > >>>>>> * The IDLTagExtension was written to manage the IDL links in the > >>>>>> OpenOffice.org Developer's Guide. > >>>>>> * The extension converts Java paths to links back to the > >>>>>> o
Re: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/11 17:57:33, Matthias Seidel wrote: > Hi Peter, > > Am 11.12.20 um 18:47 schrieb Peter Kovacs: > > +1 for Dave's ideas. > > I just wanted to enable. In doubt we delete the repo and create new ones. > > > > I created it because the feedback did suggest it is good way. Maybe I was > > to quick with going forward. I am sorry. > > No need to be sorry, but maybe the naming was a bit confusing. > > I am +1 to put something like our AOO skin it a Repository. > And the forum modifications in another. > > Regards, > > Matthias OK, clear. I missed the Forum part. Sounds like a good plan to have two repo's, one for MWiki and one for Forum +1 for Dave's proposal > > > > > Am 11. Dezember 2020 17:34:31 MEZ schrieb Dave Fisher > > : > >> Excuse the top post, but I thought Peter had proposed two repositories > >> > >> (1) mwiki for all of the mediawiki configuration including this > >> extension. But somehow this has become a tiny repository for just this > >> particular extension? > >> > >> (2) forums for the forum configuration. I’ll take this one up within > >> the next month or two. I have notes from the last upgrade and the VM > >> does need to be upgraded. > >> > >> Regards, > >> Dave > >> > >> Sent from my iPhone > >> > >>> On Dec 11, 2020, at 8:14 AM, Dick Groskamp wrote: > >>> > >>> > >>> > >>>> On 2020/12/11 15:01:35, Matthias Seidel > >> wrote: > >>>> Hi Peter, > >>>> > >>>> I am not sure what you are talking about here... > >>>> > >>>> The discussion is about a non working extension for our Wiki server. > >>>> > >>>> The repository is for our Media Wiki extension? > >>>> > >>>> 2 totally different things... > >>>> > >>>> Matthias > >>>> > >>>>> Am 11.12.20 um 12:22 schrieb Peter Kovacs: > >>>>> I have created the Repository for MWiki extensions with my Proposed > >> name: > >>>>> openoffice-mwiki-ext.git > >>>>> <https://gitbox.apache.org/repos/asf/openoffice-mwiki-ext.git> > >>>>> > >>>>> It is ready to add our MWiki extensions. > >>>>> > >>>>> > >>>>> On 10.12.20 20:35, Keith N. McKenna wrote: > >>>>>> On 12/9/2020 5:38 PM, Marcus wrote: > >>>>>>> Am 09.12.20 um 18:35 schrieb Peter Kovacs: > >>>>>>>> How about we create a OpenOffice-Mwiki-ext Repo in gitbox? > >>>>>>>> > >>>>>>>> We could do the same for the forums customizations. > >>>>>>>> > >>>>>>>> So we have more control over our support code. > >>>>>>> +1 > >>>>>>> This increases the chance that also others can have a look and > >> give > >>>>>>> some > >>>>>>> hints when problems arise. > >>>>>>> > >>>>>>> Marcus > >>>>>>> > >>>>>> +1 > >>>>>> > >>>>>> Keith > >>>>>>>> On 09.12.20 18:24, Dick Groskamp wrote: > >>>>>>>>> On 2020/12/09 11:34:03, Carl Marcum wrote: > >>>>>>>>>> Hi Dick, > >>>>>>>>>> > >>>>>>>>>> I have copied it out and it's contents are below. > >>>>>>>>>> > >>>>>>>>>> It should be in github or svn but I haven't had time to do > >> anything > >>>>>>>>>> with it. > >>>>>>>>>> > >>>>>>>>>> On 12/9/20 5:42 AM, Dick Groskamp wrote: > >>>>>>>>>>> On 2020/12/08 18:56:25, Carl Marcum > >> wrote: > >>>>>>>>>>>> There are still hundreds of broken pages in the dev guide. > >>>>>>>>>>>> Yes it seems to be idls and ildm tags. > >>>>>>>>>>>> > >>>>>>>>>>>> There is a new upgraded VM setup for the wiki waiting to get > >>>>>>>>>>>> changed to > >>>>>>>>
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/11 17:23:20, Matthias Seidel wrote: > Hi Dick, > > Am 11.12.20 um 17:14 schrieb Dick Groskamp: > > The extension is not broken, it is outdated. It cannot be updated > because that would need a newer version of Wiki. > However, our AOO skin for the Wiki must be adapted to the newer Wiki > version... > > At least that is what I understood from Andrea's posts regarding the > Wiki server in 2019 [1] > Well, if it is outdated and it doesn't do its job, I think it is broken. What I meant to say is that it doesn't work the way it was designed anymore. > > See above, the extension is not ours. It is from mediaWiki.org (?) > Well, I think it is ours. It was especially created by former developers for this purpose and it is probably nowhere else available/usable and just works on our wiki. I haven't read Andrea's post yet, I focused more on getting this defective extension IDLTags repaired. Problem is the deprecation of the ereg_replace function from PHP 7.0.* That was the function that was used in this IDLTags extension and made it work as it did. This is the reason that several pages in the DevGuide show blank. If we can replace the used ereg_replace function by a still usable preg_replace function it should work again and all should be well :-) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/11 19:34:47, Matthias Seidel wrote: > Hi Dick, > > Am 11.12.20 um 20:29 schrieb Dick Groskamp: > > > > On 2020/12/11 17:23:20, Matthias Seidel wrote: > >> Hi Dick, > >> > >> Am 11.12.20 um 17:14 schrieb Dick Groskamp: > >> > >> The extension is not broken, it is outdated. It cannot be updated > >> because that would need a newer version of Wiki. > >> However, our AOO skin for the Wiki must be adapted to the newer Wiki > >> version... > >> > >> At least that is what I understood from Andrea's posts regarding the > >> Wiki server in 2019 [1] > >> > > Well, if it is outdated and it doesn't do its job, I think it is broken. > > What I meant to say is that it doesn't work the way it was designed anymore. > >> See above, the extension is not ours. It is from mediaWiki.org (?) > >> > > Well, I think it is ours. It was especially created by former developers > > for this purpose and it is probably nowhere else available/usable and just > > works on our wiki. > > Who would that developer be?! Do you know a name? It was somewhere up in this thread: // Extension credits that will show up on Special:Version $wgExtensionCredits['parserhook'][] = array( 'name' => 'IDL Tags', 'version' => '1.0.2', 'author' => array( 'Clayton Cornell', 'Terry Ellison' ), 'description' => 'Manage the IDL links in the OOo Dev Guide ', 'url' => 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension', ); > > Isn't it more likely that it is a mediawiki extension like: > > https://www.mediawiki.org/wiki/Extension:SyntaxHighlight > That is probably where the confusion comes from. You can develop your own extensions if you want, just like our own .oxt's. The whole IDLTags extension is the PHP-page Carl copied from the configuration. That's all > > > > I haven't read Andrea's post yet, I focused more on getting this defective > > extension IDLTags repaired. > > Well, that would be a workaround for the moment, but we should "simply" > fix the source of the problem... > With "source of the problem" I assume you mean upgrading the wiki version and updating the skin etc as mentioned in Andrea's post As far as I know has Carl a new updated VM available to go along with that, but he has a tiny problem getting access. I think that will be the next step. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/11 22:37:20, Carl Marcum wrote:
> It's been awhile since I've done any PHP so I've been doing some testing
> in an online PHP Sandbox [1].
>
> [1] https://sandbox.onlinephpfunctions.com/
>
> See below:
>
> On 12/11/20 3:30 PM, Dave Fisher wrote:
> >
> > Sent from my iPhone
> >
> >> On Dec 11, 2020, at 11:46 AM, Dick Groskamp wrote:
> >>
> >>
> >>
> >>> On 2020/12/11 19:34:47, Matthias Seidel
> >>> wrote:
> >>> Hi Dick,
> >>>
> >>>> Am 11.12.20 um 20:29 schrieb Dick Groskamp:
> >>>>
> >>>> On 2020/12/11 17:23:20, Matthias Seidel
> >>>> wrote:
> >>>>> Hi Dick,
> >>>>>
> >>>>> Am 11.12.20 um 17:14 schrieb Dick Groskamp:
> >>>>>
> >>>>> The extension is not broken, it is outdated. It cannot be updated
> >>>>> because that would need a newer version of Wiki.
> >>>>> However, our AOO skin for the Wiki must be adapted to the newer Wiki
> >>>>> version...
> >>>>>
> >>>>> At least that is what I understood from Andrea's posts regarding the
> >>>>> Wiki server in 2019 [1]
> >>>>>
> >>>> Well, if it is outdated and it doesn't do its job, I think it is broken.
> >>>> What I meant to say is that it doesn't work the way it was designed
> >>>> anymore.
> >>>>> See above, the extension is not ours. It is from mediaWiki.org (?)
> >>>>>
> >>>> Well, I think it is ours. It was especially created by former developers
> >>>> for this purpose and it is probably nowhere else available/usable and
> >>>> just works on our wiki.
> >>> Who would that developer be?! Do you know a name?
> >> It was somewhere up in this thread:
> >> // Extension credits that will show up on Special:Version
> >> $wgExtensionCredits['parserhook'][] = array(
> >> 'name' => 'IDL Tags',
> >> 'version' => '1.0.2',
> >> 'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
> > This clearly an OOo extension.
> >
> > Clayton didn’t really join AOO and Terry did the Forum move but seemed to
> > get frustrated and left.
> >
> > I think that the approach could be separate from Carl’s new Wiki VM effort.
> >
> > Someone will need to look at the current VM and try your idea about
> > changing the function.
> >
> > If Andrea can’t then I’ll have a look early next week.
> >
> > Regards,
> > Dave
> >
> >> 'description' => 'Manage the IDL links in the OOo Dev Guide ',
> >> 'url' =>
> >> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
> >> );
> >>> Isn't it more likely that it is a mediawiki extension like:
> >>>
> >>> https://www.mediawiki.org/wiki/Extension:SyntaxHighlight
> >>>
> >> That is probably where the confusion comes from. You can develop your own
> >> extensions if you want, just like our own .oxt's. The whole IDLTags
> >> extension is the PHP-page Carl copied from the configuration. That's all
> >>>> I haven't read Andrea's post yet, I focused more on getting this
> >>>> defective extension IDLTags repaired.
> >>> Well, that would be a workaround for the moment, but we should "simply"
> >>> fix the source of the problem...
> >>>
> >> With "source of the problem" I assume you mean upgrading the wiki version
> >> and updating the skin
> >> etc as mentioned in Andrea's post
> >>
> >> As far as I know has Carl a new updated VM available to go along with
> >> that, but he has a tiny
> >> problem getting access. I think that will be the next step.
> >>
> >>
>
> I think Arrigo's finding about the deprecated method may be it.
>
> I have commented out the old method call and folled with the replacement.
> Testing a string that might be used in tag:
> $input = 'com.sun.star.uno.XComponentContext:getServiceManager';
> print("input = $input \n");
>
> // $page = ereg_replace('\.','/',$input);
> $page = preg_replace('/\./','/',$input);
> print("p
Re: [openoffice-mwiki-ext] branch master created (now 61af533)
On 2020/12/12 18:33:15, Dave Fisher wrote: > Create a new branch and then ask Infra to make it the default branch. That’s > what I did with the websites. > > Sent from my iPhone > > > On Dec 12, 2020, at 9:40 AM, Carl Marcum wrote: > > > > Hi Matthias, > > > >> On 12/12/20 11:44 AM, Matthias Seidel wrote: > >> Hi Carl, > >> > >>> Am 12.12.20 um 17:40 schrieb Carl Marcum: > >>> Hi Matthias, > >>> > >>> On 12/12/20 10:49 AM, Matthias Seidel wrote: > And now we have a branch "master"... > > Anyone who can rename it to main?! > >>> Do you mean trunk? > >> I would have loved "trunk" but GitHub now defaults to main. Somehow ASF > >> Infra still creates repos with "master". > >> > >> Our repos for both homepages were already changed to "main"... > > > > I hadn't noticed that change. > > > > Thanks, > > Carl > > > >> > >> Regards, > >> > >>Matthias > >> > Regards, > > Matthias > > Am 12.12.20 um 16:41 schrieb di...@apache.org: > > This is an automated email from the ASF dual-hosted git repository. > > > > digro pushed a change to branch master > > in repository > > https://gitbox.apache.org/repos/asf/openoffice-mwiki-ext.git. > > > > > >at 61af533 Added original extension IDLTags to repo > > > > This branch includes the following new commits: > > > > new 61af533 Added original extension IDLTags to repo > > > > The 1 revisions listed above as "new" are entirely new to this > > repository and will be described in separate emails. The revisions > > listed as "add" were already present in the repository and have only > > been added to this reference. > > > > > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >>> For additional commands, e-mail: dev-h...@openoffice.apache.org > >>> > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > My bad. Sorry guys. I had trouble adding the file to the repo because it was empty then. Had to grab back on older documentation and that's how it became what it is. Don't know if it is possible to delete this one and make a new branch, for instance IDLTags, to differentiate the coming content of the repo? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [openoffice-mwiki-ext] branch master created (now 61af533)
On 2020/12/12 19:51:00, Matthias Seidel wrote: > Hi Dick, > > Am 12.12.20 um 20:45 schrieb Dick Groskamp: > > My bad. Sorry guys. > > I had trouble adding the file to the repo because it was empty then. > > Had to grab back on older documentation and that's how it became what it is. > > Don't know if it is possible to delete this one and make a new branch, for > > instance IDLTags, to differentiate the coming content of the repo? > > I already created a branch "main" > > I will ask Infra to set it to default, then we can delete "master" > > Regards, > > Matthias > Great! thanks > > > > - > > 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: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-
On 2020/12/11 22:37:20, Carl Marcum wrote:
> It's been awhile since I've done any PHP so I've been doing some testing
> in an online PHP Sandbox [1].
>
> [1] https://sandbox.onlinephpfunctions.com/
>
> See below:
>
> On 12/11/20 3:30 PM, Dave Fisher wrote:
> >
> > Sent from my iPhone
> >
> >> On Dec 11, 2020, at 11:46 AM, Dick Groskamp wrote:
> >>
> >>
> >>
> >>> On 2020/12/11 19:34:47, Matthias Seidel
> >>> wrote:
> >>> Hi Dick,
> >>>
> >>>> Am 11.12.20 um 20:29 schrieb Dick Groskamp:
> >>>>
> >>>> On 2020/12/11 17:23:20, Matthias Seidel
> >>>> wrote:
> >>>>> Hi Dick,
> >>>>>
> >>>>> Am 11.12.20 um 17:14 schrieb Dick Groskamp:
> >>>>>
> >>>>> The extension is not broken, it is outdated. It cannot be updated
> >>>>> because that would need a newer version of Wiki.
> >>>>> However, our AOO skin for the Wiki must be adapted to the newer Wiki
> >>>>> version...
> >>>>>
> >>>>> At least that is what I understood from Andrea's posts regarding the
> >>>>> Wiki server in 2019 [1]
> >>>>>
> >>>> Well, if it is outdated and it doesn't do its job, I think it is broken.
> >>>> What I meant to say is that it doesn't work the way it was designed
> >>>> anymore.
> >>>>> See above, the extension is not ours. It is from mediaWiki.org (?)
> >>>>>
> >>>> Well, I think it is ours. It was especially created by former developers
> >>>> for this purpose and it is probably nowhere else available/usable and
> >>>> just works on our wiki.
> >>> Who would that developer be?! Do you know a name?
> >> It was somewhere up in this thread:
> >> // Extension credits that will show up on Special:Version
> >> $wgExtensionCredits['parserhook'][] = array(
> >> 'name' => 'IDL Tags',
> >> 'version' => '1.0.2',
> >> 'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
> > This clearly an OOo extension.
> >
> > Clayton didn’t really join AOO and Terry did the Forum move but seemed to
> > get frustrated and left.
> >
> > I think that the approach could be separate from Carl’s new Wiki VM effort.
> >
> > Someone will need to look at the current VM and try your idea about
> > changing the function.
> >
> > If Andrea can’t then I’ll have a look early next week.
> >
> > Regards,
> > Dave
> >
> >> 'description' => 'Manage the IDL links in the OOo Dev Guide ',
> >> 'url' =>
> >> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
> >> );
> >>> Isn't it more likely that it is a mediawiki extension like:
> >>>
> >>> https://www.mediawiki.org/wiki/Extension:SyntaxHighlight
> >>>
> >> That is probably where the confusion comes from. You can develop your own
> >> extensions if you want, just like our own .oxt's. The whole IDLTags
> >> extension is the PHP-page Carl copied from the configuration. That's all
> >>>> I haven't read Andrea's post yet, I focused more on getting this
> >>>> defective extension IDLTags repaired.
> >>> Well, that would be a workaround for the moment, but we should "simply"
> >>> fix the source of the problem...
> >>>
> >> With "source of the problem" I assume you mean upgrading the wiki version
> >> and updating the skin
> >> etc as mentioned in Andrea's post
> >>
> >> As far as I know has Carl a new updated VM available to go along with
> >> that, but he has a tiny
> >> problem getting access. I think that will be the next step.
> >>
> >>
>
> I think Arrigo's finding about the deprecated method may be it.
>
> I have commented out the old method call and folled with the replacement.
> Testing a string that might be used in tag:
> $input = 'com.sun.star.uno.XComponentContext:getServiceManager';
> print("input = $input \n");
>
> // $page = ereg_replace('\.','/',$input);
> $page = preg_replace('/\./','/',$input);
> print("
Re: MWiki Developer Guide Blank Pages
On 2020/12/16 23:53:56, Carl Marcum wrote: > Hi All, > > I think I've fixed the blank pages problem in the Developer Guide. > I've spot checked through all of the spreadsheet pages that had many > broken and they all display now. > > Please check any that you have reported and let me know if you find any > that are still blank. > > For those interested it was in the OOoIDLtags.php extension and the > solution was pointed out by Arrigo Marchiori as a deprecated method in > new versions of PHP. > > So a big thanks to Arrigo! > > Thanks, > Carl > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > Just checked the odd 50 pages I worked on this week in case your solution might not work. Guess what.. IT WORKS. All pages display correct. Thanks for the fix and your effort, also a big thanks to Rigo for pointing us in the right direction. Did encounter some odd tags and [IDL: ], but that has nothing to do with the solution. I'll try to find the odd tags and fix them. For now I think all is well,,. . as it should be in this times. Greetings - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Help with GIT. PR #74 Removed whitespace from files Helpcontent2
Back in February I started working on removing superfluous whitespace between tags in files in the folder Helpcontent2. These files contain the content for the Help files in AOo. In the very past superfluous whitespace was introduced by former participants, probably to make the code in the files more readable. However, in the application POOTLE, which we use for translating the Help files, these whitespace needlessly shows up in the segments to translate. This creates confusion for the translators whether they should remove the whitespace or not. Removing it will instantiate errors in POOTLE. Removing these whitespaces would bring the original segments in sync with translated ones in terms of formatting. It should also removed unneccessary warnings/errors in Pootle. The changes I made are only to text, no coding, also some typo's corrected if I can across them. Starting this was also my first attempt to try using GIT. Obviously I made some mistakes, for instance by not incorporating all changes in one commit but acrosse several, but I had no idea how many changes GIT could handle in one time. Now I'm ended up with four outstanding PR's which should contain my changes and are waiting to be incorporated. Today I had another look at the changes for PR 74 by fetching upstream trunk to my local fork. Then I merged upstream trunk to my local fork. Checked out to branch Latest and rebased that. Now I need help to continue. How can I integrate my changes in upstream trunk/main/source/helpcontent2 Can I do that myself or does someone has to approve my PR and have a look at it. Or would it be more simple to start over en delte the old PR's ? Greetings, Dick - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Help with GIT. PR #74 Removed whitespace from files Helpcontent2
On 2020/12/18 12:56:06, Dick Groskamp wrote: > Back in February I started working on removing superfluous whitespace between > tags in files in the folder Helpcontent2. > These files contain the content for the Help files in AOo. In the very past > superfluous whitespace was introduced by former participants, probably to > make the code in the files more readable. > > However, in the application POOTLE, which we use for translating the Help > files, these whitespace needlessly shows up in the segments to translate. > This creates confusion for the translators whether they should remove the > whitespace or not. Removing it will instantiate errors in POOTLE. > > Removing these whitespaces would bring the original segments in sync with > translated ones in terms of formatting. It should also removed unneccessary > warnings/errors in Pootle. The changes I made are only to text, no coding, > also some typo's corrected if I can across them. > > Starting this was also my first attempt to try using GIT. Obviously I made > some mistakes, for instance by not incorporating all changes in one commit > but acrosse several, but I had no idea how many changes GIT could handle in > one time. Now I'm ended up with four outstanding PR's which should contain my > changes and are waiting to be incorporated. > > Today I had another look at the changes for PR 74 by fetching upstream trunk > to my local fork. > Then I merged upstream trunk to my local fork. > Checked out to branch Latest and rebased that. > > Now I need help to continue. > How can I integrate my changes in upstream trunk/main/source/helpcontent2 > Can I do that myself or does someone has to approve my PR and have a look at > it. > > Or would it be more simple to start over en delte the old PR's ? > > Greetings, > Dick > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > I should have mentioned that there was 1 conflict, which I resolved. Should I now again do git commit or not ? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: MWiki Developer Guide Blank Pages
On 2020/12/17 23:42:31, Carl Marcum wrote: > Hi Dick, > > On 12/17/20 12:57 PM, Dick Groskamp wrote: > > > > On 2020/12/16 23:53:56, Carl Marcum wrote: > >> Hi All, > >> > >> I think I've fixed the blank pages problem in the Developer Guide. > >> I've spot checked through all of the spreadsheet pages that had many > >> broken and they all display now. > >> > >> Please check any that you have reported and let me know if you find any > >> that are still blank. > >> > >> For those interested it was in the OOoIDLtags.php extension and the > >> solution was pointed out by Arrigo Marchiori as a deprecated method in > >> new versions of PHP. > >> > >> So a big thanks to Arrigo! > >> > >> Thanks, > >> Carl > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> > >> > > Just checked the odd 50 pages I worked on this week in case your solution > > might not work. > > > > Guess what.. IT WORKS. > > > > All pages display correct. > > > > Thanks for the fix and your effort, also a big thanks to Rigo for pointing > > us in the right direction. > > > > Did encounter some odd tags and [IDL: ], but that has nothing to do > > with the solution. > > I'll try to find the odd tags and fix them. For now I think all is well,,. > > . as it should be in this times. > > > > > And thanks to you for trying to do something to fix it as well. > > From what I can tell from the extension the tags are idl, idlm, idls, > idlmodule, and idltopic [1]. > > It looks like someone deleted a wiki page about the idl tag extension 8 > years ago [2]. > Although I don't know if it had any content. > > It would be good to have a page about it one day :) > > [1] https://github.com/apache/openoffice-mwiki/blob/main/OOoIDLtags.php > [2] http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > Just put up a new page on the wiki https://wiki.openoffice.org/wiki/MediaWiki_Extension/Extension_IDLTags#IDLTags_extension_for_Mediawiki Feel free to adjust/add - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Design Docs?
On 2020/12/19 01:06:29, Steve Lubbs wrote: > Hi All, > > I asked this question in recruitment but this may be the proper place > for it. > > Is there any design documentation, especially related to structure (what > are the modules, what is their function, how do they interact, etc.), > however minimal, that you can point me to to help in wading through the > code? I'm hoping to avoid reverse engineering the code. > > If the answer to my query is available somewhere I should have seen it, > I apologize. > > Thanks in advance, > > Steve Lubbs > Would this be of any help ? https://www.openoffice.org/marketing/ooocon2006/presentations/tuesday_d2.pdf - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Is this a typo or is it intentional?
I'm definitely no developer but when I added the new Japanse era Reiwa to the
file
openoffice-trunk/main/i18npool/source/calendar/calendar_gregorian.cxx,
I noticed this code:
132 Calendar_gregorian::Calendar_gregorian()
133 {
134 init(NULL);
135 }
136 Calendar_gregorian::Calendar_gregorian(Era *_earArray)
137 {
138 init(_earArray);
139 }
_
on line 140 it says however: Calendar_gregorian::init(Era *_eraArray)
It seems to me that _eraArray is right because it is used further on in the
code.
QUESTION:
Are the *_earArray on line 136 and _earArray on line 138 intentional or are
they typo's ?
Could someone with more knowledge enlighten me or at least check if it is
correct as it is ?
Couldn't file an issue on GitHub so mentioned it here
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: <code> Is this a typo or is it intentional?
Rigo / Matthias,
thanks for the info. Now I know that I saw it right then.
I'm not touching the code as I have no idea how to fix it.
On 2021/03/05 09:51:58, Matthias Seidel wrote:
> Hi all,
>
> It really seems to be a typo and OpenGrok can only find two instances of it:
>
> http://opengrok.openoffice.org/search?project=trunk&full=%22_earArray%22&defs=&refs=&path=&hist=&type=&si=full
>
> So I think it would be without risk to correct this.
>
> Regards,
>
> Matthias
>
> Am 05.03.21 um 08:31 schrieb Arrigo Marchiori:
> > Hello Dick,
> >
> > On Thu, Mar 04, 2021 at 06:25:10PM -, Dick Groskamp wrote:
> >
> >> I'm definitely no developer but when I added the new Japanse era Reiwa to
> >> the file
> >> openoffice-trunk/main/i18npool/source/calendar/calendar_gregorian.cxx,
> >> I noticed this code:
> >>
> >> 132 Calendar_gregorian::Calendar_gregorian()
> >> 133 {
> >> 134 init(NULL);
> >> 135 }
> >> 136 Calendar_gregorian::Calendar_gregorian(Era *_earArray)
> >> 137 {
> >> 138 init(_earArray);
> >> 139 }
> >> _
> >> on line 140 it says however: Calendar_gregorian::init(Era *_eraArray)
> >>
> >> It seems to me that _eraArray is right because it is used further on in
> >> the code.
> >>
> >> QUESTION:
> >> Are the *_earArray on line 136 and _earArray on line 138 intentional or
> >> are they typo's ?
> > I think that "ear" instead of "era" is a typo.
> >
> > If you look at the corresponding include file
> > main/i18npool/inc/calendar_gregorian.hxx at line 51:
> >
> > 45 class Calendar_gregorian : public CalendarImpl
> > 46 {
> > 47 public:
> > 48
> > 49// Constructors
> > 50Calendar_gregorian();
> > 51Calendar_gregorian(Era *_eraArray);
> > 52void SAL_CALL init(Era *_eraArray);
> >
> > The parameter is spelled correctly there.
> >
> > However the code compiles and works fine, because the typo is ``used
> > consistently'' inside Calendar_gregorian::Calendar_gregorian(Era *)
> >
> > If you don't like to have that typo in the code, I believe you can fix
> > it straight away as it is a ``trivial edit'' (i.e. no need to review
> > before committing), as I think you did for the new Japanese era.
> >
> > I hope this helps.
> >
> > Best regards,
>
>
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Help file misunderstanding
On 2021/04/14 07:13:40, Bidouille wrote: > Hello folks, > > In helpcontent2/source/text/swriter/00.po > We have a lot of > This german term should be translated? > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > I don't think so. It is de ID of the variable and should not be changed. If you do you also have to look for the places the variable is used and change it there too. I don't think it's worth it, whether the variable is called "stichwortverzeichnisverz1" or "987654321" makes no different to me. If only it is unique matters. Just my 2 cts - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draft of new Templatew for Release Notes
On 2021/05/15 16:49:46, "Keith N. McKenna" wrote: > Here is a link to a PDF of a draft of the Release Notes Template on > Confluence. The original intent of the template was to create a > consistent and professional look and feel to the documentation we > present to the public. > > A number of changes have been made and I welcome all comments and > suggestions on format, wording, and grammar. The PDF can be found at the > Following link: https://1drv.ms/f/s!AsMYmStvrJNJgQRZMOphRisXB35X > > Regards, > Keith > > > Keith, came across the following issues: ___ link Apache OpenOffice - should be HTTPS link here - should be HTTPS http://www.openoffice.org/download/other.html should be https://www.openoffice.org/download/other.html OpenOffice4.1.10 - add space before 4.1.10 Windows - remove space before Windows Apache OpenOffice 4.1.5 should be 4.1.11 http://www.openoffice.org/download/common/instructions.html - should be HTTPS remove Google+ and replace by YouTube (https://www.youtube.com/openoffice) channel Jst my 2 cts - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: RE: Many subpages of the de-website not reachable anymore?
On 2021/05/23 09:50:32, Jörg Schmidt wrote: > Hello Peter, > > > -Original Message- > > From: Peter Kovacs [mailto:pe...@apache.org] > > Sent: Sunday, May 23, 2021 11:35 AM > > To: dev@openoffice.apache.org > > Subject: Re: Many subpages of the de-website not reachable anymore? > > > > Hello Jörg, > > > > > > I am not sure what is wrong. The link at [1] works for me. I see no > > differences to the archive., Also the History at [2] does not > > show any > > changes. > > > > From which link do you start or which one is broken? > > i start from "Ich benötige Hilfe zu OpenOffice", and the Link is: > > https://www.openoffice.org/about-ooo/about-mailinglist.html > > without "de" in the link. > > > (I hope that this is just a carelessness error and not related to a schematic > approach to the CMS conversion, because I have always warned about the > consequences of the latter, because the national sites are not uniform.) > > > greetings, > Jörg > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > Could it be that https://www.openoffice.org/about-ooo/about-mailinglist.html (without de in the link) doesn't exists ? It is not in the Dutch sites - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: RE: RE: Many subpages of the de-website not reachable anymore?
On 2021/05/23 10:18:48, Jörg Schmidt wrote: > > -Original Message- > > From: Dick Groskamp [mailto:di...@apache.org] > > Sent: Sunday, May 23, 2021 12:09 PM > > To: dev@openoffice.apache.org > > Subject: Re: RE: Many subpages of the de-website not > > reachable anymore? > > > Could it be that > > https://www.openoffice.org/about-ooo/about-mailinglist.html > > (without de in the link) doesn't exists ? > > Yes. This is exactly the cause. That's why I wrote that the national pages > are not uniform and can not be treated the same. > > > > Jörg OK, I probably found the cause. it is in index.html. This part: Ich benötige Hilfe zu OpenOffice picks up: https://www.openoffice.org/about-ooo/mailinglist.html BUT it should pick up : https://www.openoffice.org/de/about-ooo/mailinglist.html Something is going wrong with the abbreviation of the path. I don't know enough of this to repair it. Sorry for that. Maybe someone else can have a quick peek. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: French AOO website
On 2021/06/02 08:42:32, Bidouille wrote: > Hello folks, > > We have a broken link in our documentation. > Somebody with sufficient karma can upload this document: > https://berma.pagesperso-orange.fr/Files_fr/XrayTool60_fr.odt > to this location: > https://www.openoffice.org/fr/Documentation/Basic/ > > Thanks in advance > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > File uploaded to wiki: https://wiki.openoffice.org/wiki/File:XrayTool60_fr.odt Changed link on the web page to this link. Also changed text of link to ODT instead of SXW - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: French AOO website
On 2021/06/02 12:49:35, Dick Groskamp wrote: > > > On 2021/06/02 08:42:32, Bidouille wrote: > > Hello folks, > > > > We have a broken link in our documentation. > > Somebody with sufficient karma can upload this document: > > https://berma.pagesperso-orange.fr/Files_fr/XrayTool60_fr.odt > > to this location: > > https://www.openoffice.org/fr/Documentation/Basic/ > > > > Thanks in advance [[snip]] Sorry, misread your message. File now uploaded to fr/Documentation/Basic/ Link still changed to ODT. Functions on Staging so should be OK shortly - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Changing default rounding in Writer Tables
On 2021/06/10 00:07:01, Dean.Webber <2018001...@student.sit.ac.nz> wrote: > Dear Devs, > > How hard would it be to change the default rounding in the tables to the > entered value or similar. Or perhaps, can I change it to accept text as an > entry by default (ie in settings)... > > Just a little time consuming whenever I enter 895.714285 or similar into the > table and have to change the rounding per cell. Otherwise, if it just thinks > text as default this will be better (for my situation). > > Like if I enter 895.714285, would it be hard for writer to be like "oh, > wanting 6 decimal places" instead of being "895.71"... Really bad when > entering 0.8 for example... > > Thanks, > Dean > You can set it as you wish. Select the cells you want to apply the desired format to. Right-click on the table. Choose Number Format, select Number under Category and enter 000.0 in the box Format Code Click the green checkmark next to the box Format Code. That should do it - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
re: Test builds for Windows
Matthias, would you build me a nl version ? -- DiGro ___ Apache OpenOffice 4.1.3 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Accessibility link not working
Marcus, I looked a bit deeper in this and it seems the page on spamassassin is a mirror of: http://www.openoffice.org/ui/accessibility/index.html So, instead of looking at https://eu3.spamassassin.org/ui/accessibility/index.html we should probably have to update http://www.openoffice.org/ui/accessibility/index.html with the suggestions Karla made: 1. remove the link to bobby ( I checked: bobby isn't available anymore, at least not from that link) or replace it by the one Karla suggests to http://wave.webaim.org/ 2. add a link to: http://wiht.co/guidetoaccessibility with tips on how to make an accessible site. It seems I don't have acces to the page http://www.openoffice.org/ui/accessibility/index.html from CMS ( or I don't know how to get there, which also may be a possibility :-) ) -- DiGro ___ Apache OpenOffice 4.1.4 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Accessibility link not working
Thank you both -- DiGro ___ Apache OpenOffice 4.1.4 (Dutch) and scanned with Ziggo extended security (F-Secure) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: git translation split into an po branch and a sdf branch (or seperate into 2 repos.)
I'd like to see it in one repo preferably If we could (sort of) copy the directory structure from Pootle, I think we are halfway there If space is an issue we might combine UI and HC2 if possible, however that might be a big one :-) All languages have their own PO-files and sdf On 2024/10/16 21:27:24 Peter Kovacs wrote: > hi all. > > > mechtilde has set up a translation git repository for the process to > save translations in case something goes wrong with the conversion. > > I added now a githup repository and i would like to convert our scripts > that they GitHub create a po file if a sdf file is checked in and vice > versa. > > why do we need this? > > the translation is done in po files while Apache OpenOffice uses the > self invented translation file sdf. sdf files are about 50% smaller then > po files. > > changes in the code are extracted as the sdf file for us, which is used > to introduce new text into the translation process > > > Does pootle play a role? > > not directly. po files are supported by all the translation tools while > sdf is not directly supported. But ther is an library that can do the > conversion. > > > what i like to do is: > > linux build bot -> sdf us -> github -> conversion -> po files -> > transation tool -> translator work -> po languages -> github -> > conversion -> sdf file -> language release packaging. > > > may be we could maintain multiple versions if our sdf file stays > backward compatible. my understanding is there are breaking changes > between 4.1 and 4.2. > > > What is the discussion about? > > I would like to know your thoughts about if we should try to keep > everything in one repo and branch or split into a po branch and sdf > pranch. or even into 2 repos? > > the one repo solution we already hit githubs limit of 2GB per push for > the initial split. so the thought started to try to avoid a big file > update on github. each language takes about 60 mb . > > > your thoughts? > > cheers. > > petko > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt
Again sorry, I misread the number of the graphic. Only graphics28 has to be changed to the new ContentView. Mathias mentioned graphics28 not graphics26 (the one I misread) On 2025/05/21 08:10:16 Dick Groskamp wrote: > Sorry, forgot to mention that they are in ForWiki of the Writer-Guide > > On 2025/05/21 08:09:03 Dick Groskamp wrote: > > Keith, > > > > I just uploaded two new icons for the Navigator > > (the one Mathias mentioned: DragMode(graphics26) and ContentView > > (graphics28)) > > Both to replace the older used icons in AOO41WG1-IntroducingWriter.odt > > > > On 2025/05/21 00:47:59 "Keith N. McKenna" wrote: > > > Matthias Seidel wrote: > > > > Hi Keith, > > > > > > > > Am 20.05.25 um 18:30 schrieb Keith N. McKenna: > > > >> Matthias Seidel wrote: > > > >>> Am 18.05.25 um 11:47 schrieb Dick Groskamp: > > > >>>> Keith, > > > >>>> > > > >>>> Caption of Figure 16 still refers to: "OpenOffice.org Start Center" > > > >>>> Should probably be OpenOffice or Apache OpenOffice > > > >>> > > > >>> Additionally, I changed a control in Navigator some time ago, that > > > >>> graphic (graphics28) should also be updated. > > > >>> > > > >>> Regards, > > > >>> > > > >>> Matthias > > > >>> > > > >> Figure 16 vwas changed, but there is no Figure 28 in the document. The > > > >> last is figure 26. > > > > > > > > Not "Figure", but "Graphic" (as it is shown in the Navigator) > > > > > > > > But the file I am looking at is 2 years old... Is the most recent one > > > > in > > > > our Wiki? > > > > > > > > Regards, > > > > > > > > Matthias > > > > > > No it is only In writer branch of the the documents repository. > > > regards. That is the one I fixed earlier today. > > > > > > Regards > > > Keith > > > > > > > >> > > > >> Keith > > > >> > > > >> > > > >> > > > >> - > > > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > > > >> > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > > - > 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: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt
Sorry again, I misread the number of the graphic. Only graphics28 has to be changed, not graphics26 (although that shows another picture on my system) Mathias referred to graphics28 (ContentView) no to graphics26 (as I read it) On 2025/05/20 16:30:28 "Keith N. McKenna" wrote: > Matthias Seidel wrote: > > Am 18.05.25 um 11:47 schrieb Dick Groskamp: > >> Keith, > >> > >> Caption of Figure 16 still refers to: "OpenOffice.org Start Center" > >> Should probably be OpenOffice or Apache OpenOffice > > > > Additionally, I changed a control in Navigator some time ago, that > > graphic (graphics28) should also be updated. > > > > Regards, > > > > Matthias > > > Figure 16 vwas changed, but there is no Figure 28 in the document. The > last is figure 26. > > Keith > > > > - > 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: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt
Keith, I just uploaded two new icons for the Navigator (the one Mathias mentioned: DragMode(graphics26) and ContentView (graphics28)) Both to replace the older used icons in AOO41WG1-IntroducingWriter.odt On 2025/05/21 00:47:59 "Keith N. McKenna" wrote: > Matthias Seidel wrote: > > Hi Keith, > > > > Am 20.05.25 um 18:30 schrieb Keith N. McKenna: > >> Matthias Seidel wrote: > >>> Am 18.05.25 um 11:47 schrieb Dick Groskamp: > >>>> Keith, > >>>> > >>>> Caption of Figure 16 still refers to: "OpenOffice.org Start Center" > >>>> Should probably be OpenOffice or Apache OpenOffice > >>> > >>> Additionally, I changed a control in Navigator some time ago, that > >>> graphic (graphics28) should also be updated. > >>> > >>> Regards, > >>> > >>> Matthias > >>> > >> Figure 16 vwas changed, but there is no Figure 28 in the document. The > >> last is figure 26. > > > > Not "Figure", but "Graphic" (as it is shown in the Navigator) > > > > But the file I am looking at is 2 years old... Is the most recent one in > > our Wiki? > > > > Regards, > > > > Matthias > > No it is only In writer branch of the the documents repository. > regards. That is the one I fixed earlier today. > > Regards > Keith > > > >> > >> Keith > >> > >> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt
Sorry, forgot to mention that they are in ForWiki of the Writer-Guide On 2025/05/21 08:09:03 Dick Groskamp wrote: > Keith, > > I just uploaded two new icons for the Navigator > (the one Mathias mentioned: DragMode(graphics26) and ContentView (graphics28)) > Both to replace the older used icons in AOO41WG1-IntroducingWriter.odt > > On 2025/05/21 00:47:59 "Keith N. McKenna" wrote: > > Matthias Seidel wrote: > > > Hi Keith, > > > > > > Am 20.05.25 um 18:30 schrieb Keith N. McKenna: > > >> Matthias Seidel wrote: > > >>> Am 18.05.25 um 11:47 schrieb Dick Groskamp: > > >>>> Keith, > > >>>> > > >>>> Caption of Figure 16 still refers to: "OpenOffice.org Start Center" > > >>>> Should probably be OpenOffice or Apache OpenOffice > > >>> > > >>> Additionally, I changed a control in Navigator some time ago, that > > >>> graphic (graphics28) should also be updated. > > >>> > > >>> Regards, > > >>> > > >>> Matthias > > >>> > > >> Figure 16 vwas changed, but there is no Figure 28 in the document. The > > >> last is figure 26. > > > > > > Not "Figure", but "Graphic" (as it is shown in the Navigator) > > > > > > But the file I am looking at is 2 years old... Is the most recent one in > > > our Wiki? > > > > > > Regards, > > > > > > Matthias > > > > No it is only In writer branch of the the documents repository. > > regards. That is the one I fixed earlier today. > > > > Regards > > Keith > > > > > >> > > >> Keith > > >> > > >> > > >> > > >> - > > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > > >> > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO41X Test Builds
Works for me on Win 11 x64 :-) On 2025/07/18 13:26:00 Matthias Seidel wrote: > And of course, feedback is always welcome! > > Regards, Matthias > > Am 16.07.25 um 17:26 schrieb Matthias Seidel: > > Hi All, > > > > New Windows AOO41X Test Builds are available for testing: > > > > https://drive.google.com/drive/folders/17c2sB4yY2lZI1bNep_ewO4HaYG-dOez5 > > > > Regards, > > > > Matthias > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wiki outage
Reported to JIRA
https://issues.apache.org/jira/browse/OPENOFFICE-202?jql=project%20%3DOpenOffice
On 2025/07/12 10:29:51 Damjan Jovanovic wrote:
> Hi
>
> Our Wiki is down, this is the error I get:
>
> [5aac215ba43716befda501f1] /wiki/Test_Cleanup TypeError from line 251 of
> /x1/mediawiki-1.35.14/includes/language/Message.php:
> Message::__construct(): Argument #3 ($language) must be of type ?Language,
> MediaWiki\HookContainer\HookContainer given, called in
> /x1/mediawiki-1.35.14/includes/OutputPage.php on line 352
>
> Backtrace:
>
> #0 /x1/mediawiki-1.35.14/includes/OutputPage.php(352):
> Message->__construct()
> #1 /x1/mediawiki-1.35.14/includes/context/RequestContext.php(262):
> OutputPage->__construct()
> #2 /x1/mediawiki-1.35.14/includes/Setup.php(786):
> RequestContext->getOutput()
> #3 /x1/mediawiki-1.35.14/includes/WebStart.php(89): require_once(string)
> #4 /x1/mediawiki-1.35.14/index.php(44): require(string)
> #5 {main}
>
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Strange problem when creating the Writer Guide
Looks like there is a manual page break with the wrong style (FrontMatter instead of OOoPageStyle) between end of chapter three and beginning of chapter 4. Replacing by a manual page break with style OOoPageStyle brings back the footers. On 2025/07/23 19:16:11 "keith N. McKenna" wrote: > I am creating the complete book for the 4.1 version of the Writer Guide. > Chapters 1-3 look good, but Chapter 4 looses the footer after the 3rd page. > > The templates are all correct having footers defined correctly. This one > has me baffled. > > Regards > Keith - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
