ok,an interface in the backoffice for people to translate is not hard,
and I can embed a javascript editor so that they can use strong, em,
bullets, etc!
But then: how would you plug the other traslation engine into that one? I
don't want to keep two separate things. Would you just
Just a shortcut for
{{=MARKMIN(T('**bold** this text'))}}
??
Any other advantage?
El miércoles, 1 de octubre de 2014 18:52:43 UTC+2, lyn2py escribió:
Translation Markmin is available.
T.M('**bold** this text')
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
Well you need to have separate things for things that are different.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because
I think you shouldn't use the built in translation for big static texts.
Static texts should be in the db in their different language versions and
then you can pick the correct one using T.accepted_language.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
-
Let me check if I got your idea:
You mean I should create a table (slug,lang)-text
db.define_table('texts',
Field('slug', 'string'),
Field('language', 'string'),
Field('text', 'text')
)
and then use it in controllers and views like this:
def my_controller():
...
return
That seems like a good solution. And yes you will need to make an interface
in the backoffice for people to translate.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list
Translation Markmin is available.
T.M('**bold** this text')
On Wednesday, October 1, 2014 6:03:44 PM UTC+8, Pablo Angulo wrote:
I sometimes find very inconvenient the translate feature. Some views
contain a lot of static text, so if I want to translate it I would do:
p{{=T('I sometimes
7 matches
Mail list logo
