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 <[email protected]> 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 format? > > Thanks in advice :) > > 2010/10/13, mdipierro <[email protected]>: > > > > > 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 <[email protected]> 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 mdipierro <[email protected]> > > >> > {{=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 <[email protected]> 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 doc :( Will it be > >> > published > >> > > soon? > > >> > > 2010/10/12 mdipierro <[email protected]> > > >> > > > It includes: > > >> > > > - new design > >> > > > - various bug fixes > >> > > > - admin has an option in models/0.py that allow it to run in demo > >> > > > mode. > > >> > > > Please report any problem. > > -- > Inviato dal mio dispositivo mobile
