jump to article
...intermittent thoughts

valid RSS with Umlauts again - äöü

Rocky praised my umlaut fix at first and then complained about the break of RSS sometimes coming with it. He was absolutely right! Today I had time to look at it - and I think there's a solution (uh yes - to the bug in my fix :-( ):

The Design-Element (Page) stories.rss generates the code for the RSS-Feed of Blogsphere but defines it to some certain character set. This character set may not be the same as the one your Domino Web Engine uses to generate the page. Since that characters sets have to be the same the broken RSS may occur if you have special characters like umlauts in it. I have changed that line and my RSS-Feed appeared again to be vaild by the feed validator. and also appered again in SharpReader. I think that's how the fix of the fix works:

Simply change the first line in your sories.rss page in Blogsphere to the value you have in your Domino Web Engine configuration to be used as default settings character set. In my case this is Western which is configured to be ISO-8859-1. If you have other settings, you need to enter the other value :-)

The result is a valid RSS: Image:valid RSS with Umlauts again - äöü

Of course I have tried to automatize this setting to avoid manual change of that design element. Sorrily a complete automatization seems to be impossible or  in sight to the effort inadequate: If you try to read the accordingn fields from the current server document you need to give Anonymous Reader rights to your NAB, since the @DBLookup is done from the user agents authenticity. Well, simply not a useful hint! Another way would be rewriting the page's code to a Form with SaveOptions=0 and a WebQueryOpen Agent which is setting some certain field to the Form to the value of the Domino Web Engine Setting - executetd by the Agent Signer's right or on behalf of some adequatly granted user id. But this is also not really beautiful because of performance reasons (remember only one value is calculated by reading just to fields and that is only for the few Blogsphere instances using charcters above ASCII-127 when running a complete Agent). The third and maybe only useful way is to place a setting to the Blogsphere config Profile Document which is read when generating the feed. But this would be some part of a couple of definitions around the whole RSS and should not be done as the only one option in the profile document. I had already started to create some more complex and more configurable feed-functionality than Blogsphere has at the moment, but did'nt had the time to finish it until now.

What do you think?

Add Comment
Web Site:
Comment:  (No HTML - Links will be converted if prefixed http://)
Remember Me?