mahara-contributors team mailing list archive

[Richard Mansfield <638497@xxxxxxxxxxxxxxxxxx>]

I've applied this for now, but it does seem to me that pieforms strings
should fall back to en.utf8 like all the strings in the rest of Mahara.
I've created a bug for that too:
https://bugs.launchpad.net/mahara/+bug/638525

** Changed in: mahara
       Status: New => Fix Committed

** Changed in: mahara
   Importance: Undecided => Low

** Changed in: mahara
     Assignee: (unassigned) => Richard Mansfield (richard-mansfield)

** Changed in: mahara
    Milestone: None => 1.3.1

-- 
en_US entries need to be added to Pieforms
https://bugs.launchpad.net/bugs/638497
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.

Status in Mahara ePortfolio: Fix Committed

Bug description:
(If I understand it correctly, Nigel's comment in http://wiki.mahara.org/Developer_Area/Language_Packs/Structure says to file a bug in the tracker when new translation strings are ready to be added to Pieforms, so here I am.)

Not sure if it's the best way to handle it or not, but I've added en_US strings to the rules files in Pieforms so that users of the en_US language pack still see an understandable message when, for example, a field is required but not filled out.

Patch attached.