search

Taapeli / isotammi-addons

Gramps addons for Isotammi project / Isotammen Gramps-lisäosia
11 stars 3 forks source link

re-target help_url for the AddSources Gramplet #38

Open emyoulation opened 2 months ago

emyoulation commented 2 months ago

the current help_url registered for the Add Sources gramplet points to a webpage that will never exist. (It does not follow the naming convention.)

https://github.com/Taapeli/isotammi-addons/blob/402390a5e9a085fc8326709dcf2542cecf174234/source/AddSourcesGramplet/AddSourcesGramplet.gpr.py#L23

You could use the fully qualified URL https://gramps-project.org/wiki/index.php/Addon:Isotammi_addons#Add_Sources_Gramplet

or the relative form: Addon:Isotammi_addons#Add_Sources_Gramplet

kkujansuu commented 2 months ago

OK. Will be in the next version.

emyoulation commented 2 months ago

Just for completeness -- If you want to maintain the major_version registration... before 5.2 there was no support for secure http URLs in help_url. And browsers started complaining when given insecure http:// URLs

There still isn't (to my understanding) a good option for the .gpr.py to point to native language URL.

Nick was not satisfied with prefixing the string with an underscore to add it to the PO dictionary. He said that the Weblate and wiki translators were breaking too many help buttons.

And I agree. It is frustrating that translators of the wiki don't realize the limitation and amplify the problem.

For instance, the German translator of the Gramps Glossary is kind enough to maintain dual-language anchors e.g., <span id="active_person"><span id="aktive_person">. But they translated the "Glossary" in the webpage title from a https://gramps-project.org/wiki/index.php?title=Gramps_Glossary to a https://gramps-project.org/wiki/index.php/De:Gramps_Glossar URL.

So a user cannot just insert a De: language code after the ?title= in an anchored URL (https://gramps-project.org/wiki/index.php?title=Gramps_Glossary#active_person) to have the browser scroll to the right entry.

This is unfortunate ... since the extra translation makes a user of a translated GUI work harder to lookup the native language equivalent of an English instruction.

We need a public discussion to determine if there is a better solution. The translators and the non-english-speaking users deserve a better option.