Translate question: 4 sites, 4 languages?

Next topic

Author	Message
Peter Szmulik	Sunday 07 September 2003 1:43:54 pm Hi How would I handle a situation where the same content would be published in 4 different sites (.com, .dk, .no, .se), each in the appropriate language? Would I need to handle that as four different (eZ) sites or could I somehow be able to use the Translate feature in eZ?
Jan Borsodi	Monday 08 September 2003 12:24:46 am You would use the translation feature, you will need to select one of your languages as the base language (for instance english) and then translate from that to other languages. You must then use the siteaccess feature in eZ publish to map the hostnames (.com, .dk etc) to the separate siteaccesses each having their own language setting. More on siteaccess here: http://ez.no/developer/ez_publish_3/documentation/installation_and_configuration/configuration/site_access -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Sunday 07 September 2003 1:43:54 pm

How would I handle a situation where the same content would be published in 4 different sites (.com, .dk, .no, .se), each in the appropriate language? Would I need to handle that as four different (eZ) sites or could I somehow be able to use the Translate feature in eZ?

Jan Borsodi

Monday 08 September 2003 12:24:46 am

You would use the translation feature, you will need to select one of your languages as the base language (for instance english) and then translate from that to other languages.

You must then use the siteaccess feature in eZ publish to map the hostnames (.com, .dk etc) to the separate siteaccesses each having their own language setting.

More on siteaccess here:
http://ez.no/developer/ez_publish_3/documentation/installation_and_configuration/configuration/site_access

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

eZ debug

Timing:	Jan 18 2025 15:53:31
Script start
Timing:	Jan 18 2025 15:53:31
Module start 'layout'
Timing:	Jan 18 2025 15:53:31
Module start 'content'
Timing:	Jan 18 2025 15:53:31
Module end 'content'
Timing:	Jan 18 2025 15:53:31
Script end

Main resources:

Total runtime	0.0196 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0075	588.0391	152.6406
Module start 'layout'	0.0075	0.0036	740.6797	39.4922
Module start 'content'	0.0111	0.0066	780.1719	89.3984
Module end 'content'	0.0176	0.0019	869.5703	30.3047
Script end	0.0196		899.8750

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	12.9096	14	0.0002
Check MTime	0.0011	5.6718	14	0.0001
Mysql Total
Database connection	0.0012	6.0685	1	0.0012
Mysqli_queries	0.0033	16.8474	3	0.0011
Looping result	0.0000	0.1071	1	0.0000
Template Total	0.0016	7.9	1	0.0016
Template load	0.0008	4.1957	1	0.0008
Template processing	0.0007	3.5982	1	0.0007
Override
Cache load	0.0006	3.0324	1	0.0006
General
dbfile	0.0022	11.0138	8	0.0003
String conversion	0.0000	0.1789	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