Database update propogation schedule change?

[msittig]

Changes to the database through the Adsotrans "dictionary" page used to take effect immediately. Has there been a change in procedure? (ex: I input 免予 today, but it's still not showing up when I adso trans a passage with 免予 in it).

Dictionary look-up of 免予:

http://www.adsotrans.com/adso/uniedit.pl?word=%C3%E2%D3%E8&show_flag=on&search_english=&show_english=on&search_flag=&show_pinyin=on&search_pinyin=

Adso of 免予:

http://adsotrans.com/new/advanced2.pl?url=%E5%85%8D%E4%BA%88&service=adsotate&grammar=on&encoding=UTF-8

I seem to remember this happening before with other words, otherwise I wouldn't mention it.

[trevelyan]

Changes are still live....

What you're seeing is that our advanced editor is conservative and only makes changes to single fields. We periodically run a script that automates the generation of simplified UTF8 entries for words like this -- have just manually triggered it -- you can see that your entry is safe and sound:

http://adsotrans.com/new/advanced2.pl?url=%E5%85%8D%E4%BA%88&service=adsotate&grammar=on&encoding=UTF-8

Suggestion -- you can get around this simply by using the quick add form instead of the advanced editor when adding new words. This should be much faster and will automate the tagging of entries as well as the conversion to UTF8.

[msittig]

Sounds complicated

By "the tagging of entries", do you mean adding the pinyin and parts of speech?

[trevelyan]

The basic issue is that the advanced editing script dates back to before we supported UTF8. So yeah... it's a bit complicated.

Tagging here means part-of-speech tagging. The quick add script won't add pinyin automatically, but it will try to classify entries as nouns, verbs, personal names, etc.