Re: Multilingual site options?
Simon Rönnqvist <[email protected]>
| Newsgroups | gmane.comp.cms.bitflux.general |
|---|---|
| Message-ID | <[email protected]> |
On Monday 14 November 2005 00:04, Simon Rönnqvist wrote:
> On Sunday 13 November 2005 20:10, Christian Stocker wrote:
> > On 13.11.2005 18:28 Uhr, Simon Rönnqvist wrote:
> > > On Sunday 13 November 2005 17:00, Christian Stocker wrote:
> > >>On 13.11.2005 1:04 Uhr, Simon Rönnqvist wrote:
> > >>> Hi!
> > >>>
> > >>>I'm coming back to an old post here... but hope you can refresh your
> > >>>memory by checking archive... ;-)
> > >>>
> > >>>On Oct 6, 2005, at 12:43, Christian Stocker wrote:
> > >>>>On 6.10.2005 11:35 Uhr, Simon Rönnqvist wrote:
> > >>>>>On Oct 3, 2005, at 21:28, Simon Rönnqvist wrote:
> > >>>>>>However, when I changed the sitedescription variable to
> > >>>>>>sitedescription_fi I find another problem... all the scandinavian
> > >>>>>>characters come out encoded on the webpage.
> > >>>>>>Or let's say ä comes out as &#228; in the XHTML code and
> > >>>>>>therefore the browser views ä instead of having it in the
> > >>>>>> code... ;-) (I remember some problem like this with the standard
> > >>>>>> usage of sitename, etc. some time earlier on, but that one got
> > >>>>>> fixed.)
> > >>>>>
> > >>>>> But do you have any suggestion on a solution for this?
> > >>>>
> > >>>>It was in my last mail, but maybe not really clear
> > >>>>***
> > >>>>
> > >>>>>And then this in master.xsl:
> > >>>>>> <xsl:variable name="sitedescription" select="php:functionString
> > >>>>>>('bx_helpers_config::getOption',concat('sitedescription_',$lang))"/
> > >>>>>>>
> > >>>>
> > >>>>try adding disable-output-escaping="yes" to where you do
> > >>>><xsl:value-of select="$sitedescription"/>, that may help. Or we have
> > >>>> to change bx_helpers_config::getOption, so that it resolves the
> > >>>> entities. But try the disable-output-escaping first :)
> > >>>
> > >>>Yes, it works... for the H2-tag... but how to make Google happy?
> > >>><meta name="description" content="{$sitedescription}"/>
> > >>
> > >><meta name="description">
> > >> <xsl:attribute name="content"><xsl:value-of select="$sitedescription"
> > >>disable-output-escaping="yes"/></xsl:attribute>
> > >></meta>
> > >>
> > >>(untested)
> > >
> > > I tried it with the result below...
> >
> > Works for me. Are you sure, you don't have anything between the opening
> > <meta> and <xsl:attribute> except whitespace? Otherwise that doesn't work
>
> Well I had copied and pasted the code from your post...
> Now that I also deleted all the whitespace it stopped complaining about
> errors, so probably the whitespace included some invisible character.
>
> But the strange thing is that the disable-output-escaping="yes" seems
> totally ignored in this case.
>
> cheers, Simon
And one more thing... ;-)
I just noticed that if I'm using disable-output-escaping (even only for the
content of the h2-tag (as discussed earlier)) BXE doesn't want to open pages
for editing. It gets stuck at the splash screen and Firefox complanes "no
'body' element found in your external XHTML document". (When opening
something else BXE complanes about something which I haven't been able to
read since it disappears as the next page loads.)
cheers, Simon
PS. Another more kind of cosmetic thing which I noticed is that when using
BXE, the stuff outside of the editable area seems to be viewed in the default
language and not the language of the page being edited. Doesn't do much harm,
but could be confusing for some users.
--
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms