Ofer Weisglass wrote: > Plone has very good workflow for publishing pages and other information > it is very easy to change how can create and approve the pages before > publishing. > > You talk about hebrew content - there is nothing in Hebrew right now so > what are the plans? because if it is going to be Hebrew site or English > site? > > It is very important to know that for the website design > > Re: Languagaes
OK - I'll give a detailed review of the picture I have in mind. Everyone is welcome to comment/criticize I'm talking about a site whose primary language is Hebrew, where some pages are provided in English too (or any other language someone cares to translate into). The main page and maybe a few other key pages must be provided in English too. (A lot of the current contents should be translated to Hebrew, but we can do that gradually. Until that's done - some pages will be English only). Pages which are provided in several languages would be shown in the language of choice according to the browser's language preferences. Possible override - logged on users can change their language preferences. Override - the user can switch languages any time through the web interface, provided that the current page has contents in this language. (maybe a tiny language tool bar - will offer visual cue as to which translations are available plus means to go and watch them). > Can you write more what you mean by spam that people write? > Sorry, I don't understand the question. If you mean people who write inappropriate stuff we might wish to "censor" - I never encountered such on python-IL. If your'e asking what type of spam we experience at the current wiki, it's typical "spamdexing" http://en.wikipedia.org/wiki/Wiki_spam In short - long lists of urls and keywords are inserted (usually hidden) into valid wiki pages. I don't believe people are doing it manually - most probably it's scripts that scan the web for wikis to pollute. (I believe technically, had it been done manually it would be called vandalism rather then spam) Note that current protective measures (given Shlomi's additional steps) seem to suffice - you normally wouldn't notice the spam unless you watch the changes log. My major problem with current policy is not security, but the psychological effect of having to open an account for editing pages. I believe this barrier is too high if we really want to exploit public editability. "Captcha" based verification could solve this problem (and most probably be much more effective against the spam-scripts, as I explained in previous post). Regards, Amit
