[TYPO3] multiple frontend versions of a site

Andreas Becker ab.becker at web.de
Sun Jun 24 04:25:24 CEST 2007


Hi David

we did a similarthing here with one of our Minstries!

We changed the Parameters in CoolURI.XML and that did it. Also wie entered
the Names wie entered for L=1 L=2 and so on as Languages. TIP choose a
language which you will never use on your site and then you could have even
both available. Locations and Languages :-)

*<valuemaps>
   <valuemap>
      <parameter>L</parameter>
      <value key="">0</value>
      <value key="en">1</value>
      <value key="de">2</value>
      <value key="fr">3</value>
      <value key="Ort1">4</value>
      <value key="Ort2">5</value>
      <value key="Ort3">6</value>
      <value key="Hurra wer findet mich">7</value>
      <value key="Hier kann im Grunde alles moegliche stehen">8</value>
      <value key="wir machen das hier mit cooluri, geht sicher aber auch mit
anderem">9</value>
  </valuemap>
  </valuemaps>*

http://download.bednarik.org/URITransformer.pdf
http://docs.google.com/View?docid=dd33gg45_3f8j96p

Andi

2007/6/24, Georg Rehfeld <georg.rehfeld at gmx.de>:
>
> Hi David, all,
>
> David Lanier wrote:
> > - This is for an organization that has several physical locations.
> > - The site needs to be customized for each physical location.
> > - The user will select a location by clicking a link.
> > - 99% of the pages (navigation) will be the same.
> > - 50-75% of the content on those pages will be the same.
> > ...
> > 2) Use TYPO3's translation mechanism.  What we are looking for is
> > essentially all the same functionality that is already present in the
> > translation features native to typo3.  We just don't want multiple
> > languages.  We want multiple locations.
> >
> > Is that even a route worth pursuing?  Does typo3 support "ad-hoc"
> > languages? made-up languages?  (I recognize that this would certainly
> > add some issues if we ever decided to add alternate languages to the
> site.)
>
> I think creatively abusing the translation feature will be a promising
> way to go. AFAIK 'virtual' languages are possible (somewhere in the
> translation documention Kasper has given a sample for a hypothetical
> 'Marsian' language). You even might be able to use languages like
> 'location_1_en', 'location_1_de', 'location_2_en', 'location_2_de'.
> You would have to adapt all the language menu samples more or less,
> but I think, it should be possible.
>
> regards, Georg
> --
>    ___   ___
>   | + | |__    Georg Rehfeld      Woltmanstr. 12     20097 Hamburg
>   |_|_\ |___   georg.rehfeld.nospam at gmx.de    +49 (40) 23 53 27 10
>
>                (Delete .nospam from mail address)
>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>


More information about the TYPO3-english mailing list