RAWR-Template-0.0.3 BETA

[TSG]

This template has ALWAYS been UTF-8! I have never changed it! If the language files work properly then special chars should work in other sections! I am growing tired of this. It makes no sense. The template is rendered in UTF-8 so special characters should work the same as they did in previous builds. I cannot do much more to improve it. If someone knows the solution tell me.  Every time you post rejetto you say its not HFS, but I still think it is, why would only values coming from %symbols% display wrong??? I'm blaming HFS

Yes I have known about the hide/show buttons since 0.0.2, Firefox sees the line break as firstChild thats why its not working, I have fixed it for the next build.

That last bug is a bug with the load macro i think. I attempted to fix it by putting {{$special:begin}} for each separate page in the template which seemed to fix it for me...

[rejetto]

Will you build your opinions on the facts/tests made by people, or on your laziness? Bad boy.

If you don't want to work on it you can postpone it by putting it in a to-do, or just say "I won't".

[TSG]

I am asking for help with this, the translators ladiko, MarkV, even parade, what charset do you guys normally use and what do I have to change to make it display properly in German. Same goes for Russian, I think the other languages are ok.

I want this solved before the next release. But I am too tired to work on it atm. It's 1:30am and the screen is getting blurry

How is the other language files holding up out of curiosity?

[parade]

I am asking for help with this, the translators ladiko, MarkV, even parade, what charset do you guys normally use and what do I have to change to make it display properly in German.

I normally use UTF-8 and Firefox.
There is no problem with UTF-8, HFS 2.3 build 178 and RAWR 0.0.1.
If I switch to any other charset available in Firefox I get wrong special characters.

UTF-8, HFS 2.3 build 178 and RAWR 0.0.3:
I get wrong special characters.
If I switch to any other charset of Firefox the special characters are o.k.
The language file entries are always o.k

Good luck 
parade

[jonas]

I normally use UTF-8 and Firefox.
There is no problem with UTF-8, HFS 2.3 build 178 and RAWR 0.0.1.
If I switch to any other charset available in Firefox I get wrong special characters.

UTF-8, HFS 2.3 build 178 and RAWR 0.0.3:
I get wrong special characters.
If I switch to any other charset of Firefox the special characters are o.k.
The language file entries are always o.k

The problem is with RAWR 0.0.3.

[TSG]

I normally use UTF-8 and Firefox.
There is no problem with UTF-8, HFS 2.3 build 178 and RAWR 0.0.1.
If I switch to any other charset available in Firefox I get wrong special characters.

UTF-8, HFS 2.3 build 178 and RAWR 0.0.3:
I get wrong special characters.
If I switch to any other charset of Firefox the special characters are o.k.
The language file entries are always o.k

The problem is with RAWR 0.0.3.

Does no one see my problem? cause jonas that was bloody useless.

There is no reason for 0.0.3 to be any different from 0.0.1, I have not changed the sections you speak of as showing wrong since 0.0.1. This is why I'm confused. Simply coming on here and telling me that its a problem with 0.0.3 is not helpful jonas.

If it worked in 0.0.1 why wouldn't it work in 0.0.3?? Take a look at the source from 0.0.1 and the source from 0.0.3, The only difference is that I insert language variables. I have not changed or moved the sections you speak of %comment%, %filename%, %bread-name%. There is no reason for the page to render any different.

[parade]

If it worked in 0.0.1 why wouldn't it work in 0.0.3?? Take a look at the source from 0.0.1 and the source from 0.0.3, The only difference is that I insert language variables. I have not changed or moved the sections you speak of %comment%, %filename%, %bread-name%. There is no reason for the page to render any different.

I had a look at the tpl and I am far away from understanding all of it.
I looked for charset, found charset={{!lv_charset}}, changed it to charset=UTF-8 and so far I can see all characters look fine.

Greetings
parade

[TSG]

So it is HFS. Cause UTF-8 is shown on the client side. But HFS must do language variables after page generation then send it to the browser.... and so characters imported from %item-name%, %comment% and %bread-name% are not encoded correctly within HFS cause HFS isn't fully Unicode. How to get around this I wonder I understand {{Macro}} must run after %Symbol% for parameters...

How can i set the charset as a string variable so it can be packaged in the language file.... maybe use
[charset]
{{!lv_charset}}

then have {{$charset}} in the meta tags... but i dont think that would make a difference cause macro runs after symbol and that cannot be changed....

I guess we have to default it to UTF-8 and languages like Chinese will have to manually change the value.

[TSG]

Ok for now the charset is locked to UTF-8 manually.

I have upgraded the template for HFS 179, shoutbox post deletion had to be removed, other than that the effects are un-noticeable with the new security rules.

I urge all RAWR-Template users to update to this build as 179 completely screws 0.0.3.

A note to all RAWR-Designs users!
If a check update feature fails, click the readme link and it will redirect to the correct homepage, we are taking care to cover all dead links for the new homepage.