Translating strings in templates

Next topic

Author	Message
Alejandro Serrano	Wednesday 24 January 2007 3:28:43 am Hi, I'm trying to set up a multilingual site using eZ Publish 3.8 from another not multilingual site. I've managed to add everything and it works fine. However, I've read that the usual approach to multilingual sites is to create a different siteaccess and a different set of templates for each of the "translated sites". I don't mind creating different siteaccesses, but I need templates to be in just one folder. My question is: is there any way to mantain some kind of "central repository" of strings, so a template could make a call to obtain each string that it needs to work in the language the user has? Thanks in advance, Alejandro Serrano
Mark Marsiglio	Wednesday 24 January 2007 4:54:05 am You will want to set the same design and database for each stieaccess. Just copy the settings to each language siteaccess, and all of them will use the same design and data. http://www.thinkcreative.com Turning Ideas Into Strategic Solutions
Xavier Dutoit	Wednesday 24 January 2007 4:54:36 am Yes, create an extension with only translations in them (see the one under shared/translations) for the format. then you use \|i18n( template operator (all the standards templates use it). X+ http://www.sydesy.com

Author

Message

Wednesday 24 January 2007 3:28:43 am

Hi,
I'm trying to set up a multilingual site using eZ Publish 3.8 from another not multilingual site. I've managed to add everything and it works fine.
However, I've read that the usual approach to multilingual sites is to create a different siteaccess and a different set of templates for each of the "translated sites". I don't mind creating different siteaccesses, but I need templates to be in just one folder.
My question is: is there any way to mantain some kind of "central repository" of strings, so a template could make a call to obtain each string that it needs to work in the language the user has?

Thanks in advance,
Alejandro Serrano

Mark Marsiglio

Wednesday 24 January 2007 4:54:05 am

You will want to set the same design and database for each stieaccess. Just copy the settings to each language siteaccess, and all of them will use the same design and data.

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

Xavier Dutoit

Wednesday 24 January 2007 4:54:36 am

Yes, create an extension with only translations in them (see the one under shared/translations) for the format.

then you use |i18n( template operator (all the standards templates use it).

X+

http://www.sydesy.com

eZ debug

Timing:	Jan 31 2025 03:41:32
Script start
Timing:	Jan 31 2025 03:41:32
Module start 'layout'
Timing:	Jan 31 2025 03:41:32
Module start 'content'
Timing:	Jan 31 2025 03:41:32
Module end 'content'
Timing:	Jan 31 2025 03:41:32
Script end

Main resources:

Total runtime	0.0249 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0053	588.1563	151.2109
Module start 'layout'	0.0053	0.0045	739.3672	220.6875
Module start 'content'	0.0098	0.0137	960.0547	997.8047
Module end 'content'	0.0234	0.0014	1,957.8594	33.9922
Script end	0.0249		1,991.8516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	10.4269	14	0.0002
Check MTime	0.0011	4.2282	14	0.0001
Mysql Total
Database connection	0.0008	3.3678	1	0.0008
Mysqli_queries	0.0021	8.5339	3	0.0007
Looping result	0.0000	0.0756	1	0.0000
Template Total	0.0010	4.1	1	0.0010
Template load	0.0008	3.2319	1	0.0008
Template processing	0.0002	0.8068	1	0.0002
Override
Cache load	0.0006	2.2519	1	0.0006
General
dbfile	0.0019	7.7405	8	0.0002
String conversion	0.0000	0.1043	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs