Mantis Bug Tracker - Forums

Hello,

the Admin Guide for Mantis 2.0.0 describes a new format for implementing custom strings for multiple languages via the $s_custom_messages array (https://mantisbt.org/docs/master/en-US/ ... ze.strings ).

This does not seem to work for 2.1.0. I did a quick search to see how the array is used in the code for versions 2.1.0 and 2.0.0 , but I can't seem to find any implementation that even handles that array.

Am I missing something? Thanks in advance!

There was a partial implementation of a new message format http://www.mantisbt.org/bugs/view.php?id=14099 which has been reverted at a later time.
Seems someone forgot to remove the documentation of it.

Opened http://www.mantisbt.org/bugs/view.php?id=22376 for it.

Just stumbled on this issue. v2.8.0 and the doc still suggests the new format.

OK, so how does a prolific writer with book credits, former QA manager, current business owner, and eager MantisBT user prove his worth and get access to update the Admin Guide?

Thanks @Starbuck for the offer to contribute to the project.
Any help is welcome and needed.

Contributing is quite easy, at least if you are familiar with the base technologies we use.

The high level steps are

- Open a bug report at https://www.mantisbt.org/bugs (already done for this case)
- Fork our repository at https://github.com/mantisbt/mantisbt
- Create a new branch based on latest master
- Make your changes in the new branch and reference the report in the body of your commit message (e.g. Fixes #22376)
- Send us a Pull Request (PR)
- We will review the PR, might comment, might ask for changes and will merge if all is fine

Should be no problem if you are used to work with Git / GitHub.
Let me known if you need further assistance for that.

In terms of Admin Guide, we use DocBook format and Publican generator.
This is where you would have to start https://github.com/mantisbt/mantisbt/tr ... er/docbook