Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Offline
#17 2008-01-10 18:28:03
- els
- Moderator

- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: [contrib] Idea for the new year : translation of the main TXP website...
Pat64 wrote:
For now : 3 persons offered help for French translation (Niconemo, Dragondz and Pat64) ; 1 personn for Italian translation (citizenk)
Gocom wrote:
I possibly could translate it to Finnish :)
When I said “I think that is a very good idea” I meant of course that I’ll do the Dutch translation ;)
Offline
Offline
#19 2008-01-11 03:40:52
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: [contrib] Idea for the new year : translation of the main TXP website...
I’ve been asked about this before. I’m not against the idea per se, my only problem is how to go about it. I really would prefer not to use hacks/mods of any kind on txp.com.
There’s always the old fashioned way of multiple Txp installs in subdomains or something, but that seems an awful lot of work.
If you can come up with a purely native/plugin based solution, I can try implementing it.
Offline
#20 2008-01-11 05:01:35
- net-carver
- Archived Plugin Author
- Registered: 2006-03-08
- Posts: 1,648
Re: [contrib] Idea for the new year : translation of the main TXP website...
Mary
I really would prefer not to use hacks/mods of any kind on txp.com.
I agree with you 100%. In the case of this specific project, I think the MLP Pack is the wrong solution.
All
That is not a vote of no-confidence in my work — I put long hours into the development and ongoing support of it — but IMO, it doesn’t fit the requirement of Textpattern driving it’s own site. If the MLP Pack wasn’t a mod, I’d back the idea to use it. As it is, I think it is far better to do this with native Txp or with a minimal amount of plugins.
Patrick
Am I correct in thinking that you only want to translate the main page of textpattern.com?…
… If that is the case, why not just go for a one-section-per-language solution and have each section have a single article which is a translation of the main page? A simple language switcher based on the txp:section_list tag can then be included into either the main page template or a form that it calls.
Can you give us an more complete description of the limits of what you want each translation to include? Do you want the side-bars etc translated as well? How about the contact page? etc… etc…
— Steve
Offline
Re: [contrib] Idea for the new year : translation of the main TXP website...
Els wrote:
When I said “I think that is a very good idea” I meant of course that I’ll do the Dutch translation ;)
Hi Els, I can help you if you want. I’m also maintaining the txp-nl localization.
kees
Offline
#22 2008-01-11 11:10:06
- els
- Moderator

- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: [contrib] Idea for the new year : translation of the main TXP website...
Mary wrote:
If you can come up with a purely native/plugin based solution, I can try implementing it.
I’ve used this technique before, it’s easy and native, would you have a look at it Mary?
net-carver wrote:
How about the contact page?
Hmm… what would the dev team do with messages in all kinds of languages? ;)
kees-b wrote:
Hi Els, I can help you if you want. I’m also maintaining the txp-nl localization.
Great! And I did not mean to take over your responsabilities, Kees ;)
Offline
Re: [contrib] Idea for the new year : translation of the main TXP website...
As Els said it seems no need to translate the contact form.
Steve said before
Patrick
“Am I correct in thinking that you only want to translate the main page of textpattern.com?…”
(…) “Can you give us an more complete description of the limits of what you want each translation to include? Do you want the side-bars etc translated as well? How about the contact page? etc… etc…”
The limit is the main page only. For the links, it will be interesting to add “Lang: US” in front of each. It seems interesting to translate the side-bars only for the description of TXP features.
I’m going to start the french translation into the French Forum and submit it to all person who want to collaborate in it.
What do you think?
Cheers,
Last edited by Pat64 (2008-01-11 18:15:56)
Patrick.
Github | CodePen | Codier | Simplr theme | Wait Me: a maintenance theme | [\a mi.ni.ma]: a “Low Tech” simple Blog theme.
Offline
#24 2008-01-11 18:29:25
- net-carver
- Archived Plugin Author
- Registered: 2006-03-08
- Posts: 1,648
Re: [contrib] Idea for the new year : translation of the main TXP website...
Patrick
Hello again.
Sounds like you’re only interested in a very limited translation after all. Perhaps this could be arranged as mentioned before — a section per language with one article in each section. The article body could hold the translation of the main page and the excerpt might be used as translated side-bar content. The addition of a language selector would be very easy using URLs pointing to the appropriate section.
No need for anything special at all in the way of MLP or even plugins.
— Steve
Offline
Re: [contrib] Idea for the new year : translation of the main TXP website...
Hi Steve.
Sure, you’re right. I’d told about MLP before just to promote your amazing plugin :)
Best regards,
Patrick.
Github | CodePen | Codier | Simplr theme | Wait Me: a maintenance theme | [\a mi.ni.ma]: a “Low Tech” simple Blog theme.
Offline
#26 2008-01-11 20:35:49
- guiguibonbon
- Member
- Registered: 2006-02-20
- Posts: 296
Re: [contrib] Idea for the new year : translation of the main TXP website...
Sorry for being annoying again, and feel totally free to totally ignore me. Textpattern is supposed to be flexible, elegant and easy-to-use. The very website that says so is expected to be a living proof of that.
Not only would translating the website imply we have a lively multi-lingual community, it would now also pretend that you can build a multi-lingual website with textpattern in an elegant and easy way. Those are two big lies.
One section per language is neither an elegant, nor an easy solution.
Last edited by guiguibonbon (2008-01-11 20:37:10)
Offline
#27 2008-01-11 21:58:08
- els
- Moderator

- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: [contrib] Idea for the new year : translation of the main TXP website...
I don’t agree at all. Making the front page article available in no matter how many languages doesn’t pretend either of the things you mention. What it does show is that you can easily build a website using your own language.
Last edited by els (2008-01-11 21:59:01)
Offline
#28 2008-01-11 22:21:48
- guiguibonbon
- Member
- Registered: 2006-02-20
- Posts: 296
Re: [contrib] Idea for the new year : translation of the main TXP website...
Els wrote:
What it does show is that you can easily build a website using your own language.
The intention is clearly not to make x amount of websites. The intention is to make one website with x amount of languages, although making multilingual websites is clearly not a textpattern feature.
Perhaps the most honest solution is to make separate websites dedicated to communities of a specific language. With their own domain and corresponding suffix.
Offline
Re: [contrib] Idea for the new year : translation of the main TXP website...
Hi!
Personaly, I think we could make this model :
The use of MLP plugin only for this excellent feature : the ability to reconize the web browser language and to switch automaticly to the corresponding translation – OR added a script to point to the translated page depending of the visitor language ;
Only one flag (US one) to switch to the original content.
Here is the work in process for the french translation. (Translators : Niconemo, Dragondz and I)
Cheers,
Patrick.
Github | CodePen | Codier | Simplr theme | Wait Me: a maintenance theme | [\a mi.ni.ma]: a “Low Tech” simple Blog theme.
Offline
Re: [contrib] Idea for the new year : translation of the main TXP website...
Here is the Finnish translation in process: http://www.rahinaa.biz/txp/
You may know that I also validated the XHTML and changed the header image to main header, h1-tag :) It should also be done to the real Txp.com frontpage.
Cheers!
Offline