On 10/13/2010 5:17 PM, howesc wrote:
I can't comment fully on the routes changes, but the errors you are
getting are errors in presenting you with the errors. the
error_message that you used to have at the bottom of your routes.py:
error_message = 'Invalid request'
needs to be upgraded to hav
I can't comment fully on the routes changes, but the errors you are
getting are errors in presenting you with the errors. the
error_message that you used to have at the bottom of your routes.py:
error_message = 'Invalid request'
needs to be upgraded to have a %s in it somewhere, perhaps like:
e
That is not a design decision. That is more of an accident of how it
was coded and may change.
On Oct 13, 11:07 am, Fabio Alessandro Locati wrote:
> I see... And that's true :) thanks :). Another question: why did you
> used external files instead of strings? For a division between content
> and
The fact is you have to use T anyway because not everything is in
markmin. why by-pass it?
On Oct 13, 10:37 am, Fabio Alessandro Locati wrote:
> So you would not use to create different folders for each lang, isn't it?
> Does the approach you are saying has more advantages?
>
> 2010/10/13 mdipier
So you would not use to create different folders for each lang, isn't it?
Does the approach you are saying has more advantages?
2010/10/13 mdipierro
> {{=MARKMIN(str(T(content_in_english_markmin)))}}
>
> and than you edit the content using the translation interface.
>
> On Oct 13, 9:48 am, Fabio
{{=MARKMIN(str(T(content_in_english_markmin)))}}
and than you edit the content using the translation interface.
On Oct 13, 9:48 am, Fabio Alessandro Locati wrote:
> thans :)
> I've seen the new design and I'm wondering about how to implement a
> multi-lang webste with markmin. I can't find any d
6 matches
Mail list logo
