Difference between revisions of "Website Maintenance"

Revision as of 13:18, 14 February 2017

Sometimes something should be improved on our website. This page is intended to collect the right procedure.

Adding or Changing Text

If you add or change text, keep in mind Gnucash and its website are multilingual. If you - like me and most other people - are not firm in all languages, you should ask the translators, to help you keeping the translations up to date.

"Coding" Style

The static structure is usually written in HTML, the dynamic parts are injectet via PHP. Translatable text is quoted:

 <?php echo T_("A translatable string");?>

Try to avoid putting URLs in translatable strings, but links to the wiki should be separate marked translatatable - there might be a translated page in the wiki.

Tips for Translators

Most important are the strings from index.phtml and externals/{menu|footer}.phtml. They are seen, when calling the page.

• Strings from search/ should be unusused now.
• {sizing|develdocs}.phtml are currently hopeless outdated.

Managing Translations

After you finished editing the english text, you should prepare the translation by

1. creating a new .pot file

   make pot

2. msgmerge all existing .po files

   make msgmerge

   and commit the updates

3. send a short mail to gnucash-devel about "Translators: Website changed ..."

   feel free to give them some clues, what changed like

   "complete new download page" or

   "fixed 42 typos in the english text".

4. As patches with reworked .po files arrive,
   1. apply them and
   2. make the .mo files, e.g. with

      make mos

   3. commit

      po/LL.po and

      locale/LL/LC_MESSAGES/gnucash-htdocs.mo

      where LL is the language code.

Further details can be found on the Translation page.

Thanks for your time and work!

Todo: Testing

Idea

Set up apache (or another webserver?)

Add your repository to your apache configuration /etc/apache2/conf.d/

View http://localhost/gnucash/