please
please
PLEASE
on a multi-language site having to make the same page over and over in four languages, with only one or two differences is a major waste of time.
PLEASE
i guess it's not gonna be hard to do, is it?
page cloning
- Fulvio Romanin
- Posts: 394
- Joined: Thu 4. Dec 2003, 11:12
- Location: Udine, Italy
- Contact:
page cloning
Completeness is reached through subtraction, not through addition
maybe there could be a new contenttype for multilang "articles for multilang":
when adding a new article you would get something like:
English
Title / subtitle...
Textfield (spaw, fckeditor etc.)
German
Title / subtitle
Textfield ((spaw, fckeditor etc.)
Spanish
Title / subtitle
Textfield ((spaw, fckeditor etc.)
Urdu
Title / subtitle
Textfield ((spaw, fckeditor etc.)
etc...
(the langs and how many could be defined in backedn)
so when you add a new article you get a list with all the lang into where you can put content and the content is automatic put into the right template - I don´t know if im clear enough But it could be powerfull and userfriendly
when adding a new article you would get something like:
English
Title / subtitle...
Textfield (spaw, fckeditor etc.)
German
Title / subtitle
Textfield ((spaw, fckeditor etc.)
Spanish
Title / subtitle
Textfield ((spaw, fckeditor etc.)
Urdu
Title / subtitle
Textfield ((spaw, fckeditor etc.)
etc...
(the langs and how many could be defined in backedn)
so when you add a new article you get a list with all the lang into where you can put content and the content is automatic put into the right template - I don´t know if im clear enough But it could be powerfull and userfriendly
http://www.studmed.dk Portal for doctors and medical students in Denmark
I think the copy/paste article/template/layout/css/menu branch is a good idea and one that has been mentioned a few times before, I'm sure I remember it in OG's todo list on this bb.
I think frolds Idea is not to dificult to implement but having many more articles created while you are creating the origonal can be messy. It alos semas that you have a nightmare trying to keep track adn debug all those replacment tags. As well as having to go in to each article and change the language to the intended langauge, it could be a pain.
I would preffer just thr copy/paste idea as it is very easy to understand - you copy and you paste, job done.
I think frolds Idea is not to dificult to implement but having many more articles created while you are creating the origonal can be messy. It alos semas that you have a nightmare trying to keep track adn debug all those replacment tags. As well as having to go in to each article and change the language to the intended langauge, it could be a pain.
I would preffer just thr copy/paste idea as it is very easy to understand - you copy and you paste, job done.
I do not understand...Why copy/paste a article from one lang to another.. It is not being translated during that?pSouper wrote: I would preffer just thr copy/paste idea as it is very easy to understand - you copy and you paste, job done.
The point with my little note was that you would get a new content type that let you easy add the content for the langs you had set in the backend and then easy create eg. 4 new article in 4 diffrents langs.
http://www.studmed.dk Portal for doctors and medical students in Denmark
- Fulvio Romanin
- Posts: 394
- Joined: Thu 4. Dec 2003, 11:12
- Location: Udine, Italy
- Contact:
I understand now F, yes that is a nice solution, not only for laguages but for other situations too.
I think that they are two seperate Ideas though and have thier own benefits.
I would not hope to have either one implemented as a solution to both problems.
ps. it could work as an 'IF THEN' type statment based on a conditional that is set via a rep-tag and based on a condition set from a textfield in the ADMIN/Structure template.
eg..
you could enter any word in to the field within the admin/structure area. this word is caught by the replacement tag and the IF/THEN is perfomed.
make sence to anyone ?
I think that they are two seperate Ideas though and have thier own benefits.
I would not hope to have either one implemented as a solution to both problems.
ps. it could work as an 'IF THEN' type statment based on a conditional that is set via a rep-tag and based on a condition set from a textfield in the ADMIN/Structure template.
eg..
Code: Select all
{IF_THEN_TAG:condition1,condition2} // this tells the content part to only display the content within the required condition.
[ITT] lots of german (condition1) text here [/ITT] // this is the case for condition1
some other stuff here that is not in the conditional
[ITT] some english (condition2) text here [/ITT] // this is the case for condition2.... and so on.
make sence to anyone ?