Personally, I'd be very annoyed if I just had clean slate to start my newkitten wrote:Hi,
Yes, but see my explanation for this behaviour above -- IMO it's more confusing than helpful. If I want to work on a translation, I can always copy & paste the version I want to work with.wesley wrote:I tested kitten's code and while it does what he said it should do, it does
not retain the previous language's contents to a 'new' language entry. It
seems to always query for the DB, so if there is none, the entry is cleared
and this makes it difficult for creating a translated work.
Anyway, in the meantime I continued to work on this plugin and I might propose a new version to the mailing list soon.
language version. In fact if I had to manually copy & paste I would not
have bothered to maintain the current multilingual system on my blog.
So it's clear that there really does need to be a configuration option for
the behaviour - people have different preferences & needs. So in light of
that I've added the configuration option that lets the user choose this
behaviour just before committing the new version into CVS.
for the code and suggestions. I think I like the way it works now.
Okay, meanwhile, I fully agree that the current handling of 'default
language' by s9y in relation to multilingual plugin is not exactly ideal
and is in need of a new handling method. And your idea of 'transparent
switching' seems to be a good way out of this. I'm looking forward to
seeing the outcome.