The translations of the wiki’s status page (User manual translations) are varying degrees of outdated. Only the pages of 3 languages are current.
Most are so different that starting fresh with the 6.0 English page would be closer than trying to update the old revision. Should the versions prior to 5.1 simply be deleted?
This portal table was for the program translation itself and manually updated to show coverage as detailed on the templates page , but now that we use Weblate, it is automatically updated on that website. I’ve removed those coverage columns on the wiki.
I’m aware and the issue this time is on Weblates end, waiting on them to fix/whitelist the Gramps domain. Fortunately visiting the URL directly does work.
That may be, but deletion is not the answer, I suggest simply adding a message that page is outdated and to use the English user manual kind of like how @Gioto & @Patsyblefebre are going with the followingtemplate?
I just discovered today that the French translation of the wiki is entirely missing an important chunk.
A geneanet posting exhibited a complete misunderstanding about adding to the Projects list of curated collections. (They were trying to manually download SuperTool addon via the raw.githubuser URL.)
From a quick check, it looks like “most of them” are missing the Addon Manager
Chapter 10: Navigation is the wrong place for this content anyway. The only reason it is in “Navigation” is because it is a Toolbar icon.
What do people think of moving it to Chapter 11: Plugin Manager and renaming the chapter to “Plugin Management”? (But leaving the original anchor intact for backward compatibility.) And that Toolbar mention can be reduced to a simple Glossary-like entry with a link to the full introduction in Chapter 11
It would be a good place to explain why there is a separate Plugin Manager and how it differs fro Addon Manager.
It seems that the formatting of the wiki text is preventing translation.
Additionally, probably some terms associated with tools and actions in Gramps, which are translated by humans (Weblate) and not automatically, may differ between the English documentation based on what is stated in Gramps and that in Weblate.
After reviewing the Chapter 10 section, I am even more convinced that the introduction to Addon Manager is the misplaced content for the chapter. That chapter is more about strategies for getting more out of a feature.
The introduction would transplant easily into Chapter 11 and would help users realize that it is different from the Plugin Manager
But what Addon Manager strategies could replace it? How can users get more out of the tool?
We need to do something about this, but I’m not sure what. Translations make the search almost unusable. Are translations not in their own namespaces so that we can restrict search results? I assumed they were since the names match the Namespace:PageName format, but when I restrict to the main namespace in a search, it still returns translations. Can we re-org the Wiki somehow?
And that is what I’ve done personally, but I do think that a functioning wiki is vital to the adoption of this software by more people. I’m not sure if that needs to be a whole other conversation or what. But just knowing that search is useless means we have a lot of work to do.
That objection is a bit overly dramatic. The wiki is functioning. The search may not be useful but information content has become vastly more complete in the last few years. And the “wiki” portion continues to work… it lets contributors continue to colloratively enhance the site.
And the downloadable Manual was recently restored. (After being broken for many years. Thanks again @GaryGriffin !) The Gramps Glossary has recently evolved into a viable curated index. And the GUI-based Help buttons were just hugely enhanced to make plug-in help more useful.
But index is a symptom of a more systemic issue. That the MediaWiki CMS is not sucessfully allowing updates, nor plug-in installations.
The internal indexer also seems to ignore mediwiki tags that suppress indexing of certain (like obsolete) pages.
And translated pages tend to be “fresher” than the English base pages. (Because updates to the English pages are triggers that remind translators to update.)
I started to translate the user manual few days ago, and I ask myself for whom are you translating the manual? The answer is for those genealogists who do not have an IT or programmer background and those that are not fluent in English.
And this leads to a dilemma - the user manual is very technical and covers all aspects of Gramps. That is a lot of stuff a plain user does not care about, so why should I spend time translating all this?
My suggestion is that we divide the user manual in two - a User Guide and a Reference Manual.
The User Guide should be translated, but the Reference Manual only in English. This will solve two problems. There will be less text to translate, and search in the Reference Manual will avoid all the different language pages, which most regard useless.
