← Back to team overview

mahara-contributors team mailing list archive

[Bug 786923] Re: Strings in pieforms.php are not used in foreign languages

 

Hi Dominique-Alain,

So do the pieforms strings work in pieforms?  If you go to Site
Administration and try to edit a user's account settings at
admin/users/edit.php, do you see the month names in the Expiry date
selector in French or English?  Those are the ones from pieforms.php,
and are a bit of a hangover from when pieforms was a separate project to
Mahara.


For the month names in most other places on the site (like the dates under Latest Pages on the dashboard), you need to get the locales string exactly right.  To get it to work in Ubuntu, all I had to do was this:

1. Install the French locale on the server with "sudo apt-get install language-pack-fr"
2. Put 'fr_FR.utf8' as the first item in the locales string in langconfig.php - others have said that windows users will need 'french' in there as well, but I haven't tried it myself.

So you should try 'fr_FR.utf8' if you haven't tried it already.  For me,
'fr_FR.utf8', 'fr_FR.UTF-8', and 'fr_FR.utf-8' all work, but 'fr.utf8',
'fr.utf-8', and 'french' don't do anything.

When I tried it yesterday with the Spanish langpack I thought I needed
to restart apache too, but I was wrong about that.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/786923

Title:
  Strings in pieforms.php are not used in foreign languages

Status in Mahara ePortfolio:
  Incomplete

Bug description:
  Using cpds pluging and after a email chat with its programmer, I have
  discover a problem with the dates in localised versions of Mahara.

  When displaying date, the month names are not taken from the
  translated version of pieforms.php. Therfore, the month names are
  still in English even with a French or German pieforms.php in the
  according xx.utf8 in the langpacks folder.

  This bug is visible in cpds and plans artefacts.

  I didn't check the code to find the origin of the problem.


References