User talk:Daleathan

Thanks for the encouragement Dale!

Thanks for the encouragement Dale!

I noticed that you added the Icon template (among others) --- thanks for that too!

Sam888 has resolved the problem with MediaWiki refusing to serve context too heavily laden with graphics with the last update. (He's planning another update this weekend.) So it would be nice to finish populating the icon & iconset pages. (I'm hoping to use some icons to alleviate to large blocks of unbroken text.) But the process for uploading the family of icon sizes & SVGs is unclear. Can you help?

(I wonder if putting all the instructional text in the icon template into a transclusion noincludes would boost the performance of the icon template? It wouldn't make much difference on pages with a couple of icons... but when there are dozens?)

We're thinking about ways to suppress superseded pages while leaving them accessible for users of old revs of Gramps.

I'm sketching out a template for a warning box that uses the noindex & nocat magic words, IDs the Gramps version, the page that superseded the page & the current page kid different from the updated page.

Looking forward to hearing back from you. -Brian

Bamaustin (talk) 02:57, 28 April 2020 (UTC)

Your welcome, the only way to improve the icon template is for the webmaster(That is Sam888 right?) to install Lua scripting and then we can use the current version of the icon template that is written in Lua the benefits are improved performance and simpler to program the templates. Daleathan (talk) 23:32, 29 May 2020 (UTC)

Report writing tutorial

I just started exploring the Report writing tutorial and am trying to correlate the code snippets to working code samples in the Gramps GitHub repository.

It's a bit ugly to follow because the snippets are out of sequence. Even if they were in order, the current wiki snippets are pseudo code cannot be Frankensteined into a working sample report Gramplet. And the built-in Database Summary Gramplet doesn't directly correspond either. Perhaps a working sample Report could be made from the snippets and be made available for download? Once it is posted to GitHub, we can hotlink the snippets to a directly to the line numbers that correspond.

I messaged Sam to see if we could start to use a hotlink targeting extension. I would allow us to link to the lines of code & open in a target browser window (instead redirecting the existing browser window) to avoid interrupting the sequential flow of the tutorial.

So, if this extension was installed, we could define a CSS class and the markup could look something like:

<span class="samplecode">[https://github.com/gramps-project/gramps/blob/master/gramps/plugins/textreport/summary.py#L297 line 297]</span>

Perhaps that could even be simplified into a parameterized template.

Bamaustin (talk) 05:46, 10 May 2020 (UTC)

Same as above if Lua script was installed we could use the existing mediawiki/wikipedia templates. Daleathan (talk) 23:34, 29 May 2020 (UTC)

Sectional links issue 0013562

Hi Dale,

I have not tested but could it be that for issue 0013562 the sectional links will only work if the page name is only in English with the language extension and not redirected to the translated language page name, it feels like the redirects are interfering in passing along the sectional link? Which would mean for all the sectional links to work correctly in other languages with spans all languages would have to use the English version of the page, with some override to display the correct page Language title [1][2]?

see https://gramps-project.org/wiki/index.php/User:Patsyblefebre/User_manual_translations_check_of_redirects_per_Language

Gioto (talk) 03:14, 9 January 2025 (UTC)

You maybe right, redirects on mediawiki are a pain in the first place! I'll test and report the result. Daleathan (talk) 03:54, 9 January 2025 (UTC)

Came to the same conclusion in a past email discussion with another user (that I'm unable to find!) the end result was that the field holding the url while needing to be translated should not have been marked as a translatable field in Gramps ( underscore before the field) via weblate/poedit etc, the help url field should have the fully qualified url ( with the underscores - see my page for how they should look) so that when another language is used it goes directly to that languages translated url (not redirected via the English name url) this avoids the redirection issue and you can either use the anchor/span in English or the section names in that Language. To do this a review and change needs to be made to the Gramps code. I believe the same applies to addons. It may mean editing the existing translations on weblate for each url and adding the correct versions? Patsy B Lefebre (talk) 22:03, 9 January 2025 (UTC)