Hi,

I'm planning a feature which allowed the user to display the content of 
country name in english or japanese and for item_data name in english, in 
japanese(kanji) or in japanese pronunciation(kana).
The target user mostly foreigners which have basic japanese ability, they 
just use visual ability to match character written in website and in actual 
product.
In this context the text in website will be mixed with english and japanese.

With these table structure:
db.define_table('country',
    Field('name1', label=T('Name'), unique=True),
    Field('name2', label=T('Name(Japanese)'), unique=True),
    format='%(name1)s')

db.define_table('item_data',
    Field('name1', label=T('Name'), comment=T('Commercial name')),
    Field('name2', label=T('Name(Romaji)'), comment=T('Product name in 
romaji')),
    Field('name3', label=T('Name(Kana)'), comment=T('Product name in 
kana')),
    Field('country_id', 'reference country', label=T('Country of Origin'), 
requires=IS_EMPTY_OR(IS_IN_DB(db, 'country.id', '%(name1)s', 
orderby=db.country.id, zero=T('-- Select product country --'))), 
represent=lambda id, row: db.country(id).name1 if id else ''),
    format='%(name1)s')

db.define_table('setting',
    Field('show_country_in_kanji')


What is the best practice for this kind of feature?
Should i create the table country and table item_data with one name 
field(english only), how to display it in japanese?
If the above structure can be used, how to display the item_data.country_id 
based on user setting  for example in japanese(kanji)?


Thanks,
Reza

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to