Simplify creation of multilingual sites

[cmb]

Hmm, thought the voting was made for that option:
viewtopic.php?f=29&t=6625#p37628
see here: viewtopic.php?f=29&t=6625&start=10#p37638 -- and this solution gets my vote .

That solution is already implemented since XH 1.6 (it has been there before r1017). This topic is about further simplification.

[Holger]

That solution is already implemented since XH 1.6 (it has been there before r1017). This topic is about further simplification.

Thought that too, but have not re-checked, sorry. I got confused by the posts about the problem with safe-mode...

So the options are
- Tatas suggestion with renamed folders

He suggested to rename 2lang/ to 2lang-copy_rename_xx/ or so, and to add a respective subfolder to content/.

and
- move existing files from 2lang to /content/LANG/... instead of creating the folderstructure below /content as it is now

Another option would be to automatically move the necessary folder and files to content/, if a second language is accessed, and the structure is not already there, but still resides in 2lang/.

Am I right?

[cmb]

Thought that too, but have not re-checked, sorry.

No problem.

Am I right?

Yes. However, I'm not sure how to handle this with the limited capabilities of the roadmap. If the voting would have ended already, we had a "yes", but not for the same solution. Actually, I generally don't know how to handle such multi-option votes best.

[svasti]

Actually, I generally don't know how to handle such multi-option votes best.

Every option gets its own task line (one ofter the other). In the Explanation you state it's multi option belonging to the same task.

[cmb]

Actually, I generally don't know how to handle such multi-option votes best.

Every option gets its own task line (one ofter the other). In the Explanation you state it's multi option belonging to the same task.

Well, what happens if both options are voted to "yes"? In this case it might make sense, but not necessarily in others (for instance, for the vote regarding $cf[title][format]). And how many votes should be given -- one for each option, or one for the task? In the latter case it is not clear where to vote for later/no.

IMO these are ugly bureaucratic details, but it might be better to clarify them in advance, or to avoid them alltogether (I'm not shure how, though). Otherwise it might give the "release manager" some headaches (what already happened in the past more than once).

[svasti]

Well, what happens if both options are voted to "yes"?

Depending on the task we could put in the Notes either: One one vote "now"/"not now" allowed, or: Multiple votes allowed.
If result is indecisive, "not now" could be added to "now" and "never" subtracted from "now". If still indecisive, a second emergency voting on this point by pm could be held.

[cmb]

Depending on the task we could put in the Notes either: One one vote "now"/"not now" allowed, or: Multiple votes allowed.
If result is indecisive, "not now" could be added to "now" and "never" subtracted from "now".

Sounds somewhat complicated.

If still indecisive, a second emergency voting on this point by pm could be held.

Guess we can somehow manage it this way.

FWIW: I've just pushed the Todo_XH plugin to Github. Not sure if it's worth to put much effort into it, but let's see.

[cmb]

I 've added "check for save mode=on" on the roadmap

.
I've added the check (r1416). I have not internationalized the text, though, because "session.use_trans_sid off" and "session.use_only_cookies on" are not internationalized either. However, for XH 1.7 we should consider to make that consistent with "Magic quotes runtime off".