Recent Topics

1 Jul 25, 2007 02:41    

When the message.po file is saved in UTF-8, some entitys get wrong rendered. I escaped all the special chars on the messages.po with the '&entity;' notation and all entitys are honored except the entity '¡' (inverted exclamation mark).

I test to change from '¡', inverted exclamation mark unescaped, the '¡' and the numeric one '&_#161;' (w/o the '_' I write due the forum editor beaviour), but always I get wrong results.

With the '¡', (inverted exclamation mark) unescaped I get the symbol expected but with one capital A with circumflex accent in front of my inverted exlamation mark, like this '¡' and the escaped ones get rendered as literals due the system escape the leading ampersand of this entitys.

The peculiar thing is that if I save the file in ISO-8859-1 format the inverted exclamation mark unescaped is renderer OK. I don't understand why the dev team it recommends to use UTF-8 when using ISO-8859-1 works correctly.

Please help! this is geting me crazy.
Ramon

2 Jul 26, 2007 12:06

No one?... Great system where devs does not say anything to bug reports and uploaded patchs. Maybe, b2evo is not for me.

3 Jul 26, 2007 19:01

Please don't get nervous if the dev team doesn't respond fast. In fact they may not repond at all and just take your remarks and develop there code. That's what they like to do and that's what I like them to do.

If your entity doesn't get honoured and it should, this is not a B2evo problem, but it has something to do with the browser you are working on or the database you are working with.

There is a fourth way of escaping characters: the unicode way. use &uxxxx; where you replace the xxxx with the fout digit unicode entity.

Good luck

4 Jul 26, 2007 20:12

I'll back up Afwas and add to it by saying the dev team RARELY engages here unless they need more info. They see this stuff - oh they certainly do! - but to engage in discussion takes them away from putting out a good product.

Plus if no one else has an answer you won't see an answer. As a rule, the forum junkies will answer what they can when they can. Sometimes we don't know how to help, so we don't reply. Sometimes no one knows what the answer is, so no one replies. If you want to consider "no one knows the answer to my question" as reason to downgrade then so be it, but that type of 'bump' usually doesn't trigger a happy response from those of us who spend way too much time here trying to be helpful.

Especially if you expect the development team to respond to your issues!

5 Jul 27, 2007 18:13

Hi Afwas (Foppe?) and Ed,

Thanks for the reply, first of all I don't get nervous only a little disappointed, I know that the developers cannot be programming and responding in the forum at the same time and personally I prefer also that they dedicate his time at the most important, develop!. But IMHO I think we need there one 'guy in the middle' between users and developers, not to reply all but at least to reply 'thanks guy I take note and blah, blah...' this is what turns a user a defender of the product, personally I moderate a few lists of development and this is what they value the users more (democratic poll). A advanced moderator in all the sections is not necessary, but in the 'bugs' sections, I think that it is essential. That's all :)

...this is not a B2evo problem, but it has something to do with the browser you are working on or the database you are working with.

There is a fourth way of escaping characters: the unicode way. use &uxxxx; where you replace the xxxx with the fout digit unicode entity.

Please read again the post:

I test to change from '¡', inverted exclamation mark unescaped, the '¡' and the numeric one '&_#161;' (w/o the '_' I write due the forum editor beaviour), but always I get wrong results.

I use others escaped entitys in the same file and work as expected, the only problem/bug is with this entity and only in UTF-8 charset.

Although all this does not have importance if I were evaluating b2evo for my personal use. But I am doing this for a group of multinational companies very conscious that the open source is the future and that donate some thousands of dollars to the projects that use, but this is not a B2evo problem.

TIA
Ramon

6 Jul 27, 2007 19:06

I like to think that I am one of the (minor) developers that does get involved on the forums on a daily basis. Unfortunately, being english, I don't have any knowledge/experience of multilingual problems so I tend to leave those to the developers that do have knowledge/experience rather than give crap advice.

This post probably helps as much as if I'd posted "ok", but I felt it was better than nothing in this situation huh? ;)

¥

*edit*
I'm sure EdB won't mind, I attached a screenshot of a post in admin ...... mind you, none of us have bothered to reply to him ;)

7 Jul 28, 2007 03:25

Yeah I don't mind. rambat hit the forums with nothing but help. Unfortunately, his need for help is beyond my abilities. Not only am I a one-language type of guy, but my "language" is American :roll:

rambat if we could help we would. You're obviously very sharp, so things you can't answer are ... well ... damn good questions.

Oh well though eh? If you need answers for a specific client and you're not getting them then obviously you have to take care of your client's needs. If b2evolution seems like the right application but you can't use it because of some translation issues that's a bummer, but it's also the way it goes sometimes.

8 Jul 28, 2007 03:34

EdB wrote:

Not only am I a one-language type of guy, but my "language" is American :roll:

Ahh mate, yer truly screwed .... have you thought of learning english? :roll:

¥

9 Jul 28, 2007 09:32

Accidentily i stumbled upon the file ./blog/conf/_formatting.php. It seemt to me it is converting all HTML entities from the format " to &_#34;
I also noticed thst B2evo has the same problem with # as this BBphp forum; it doesnt always render (probably due to some plugin settings).

¡ (this one was copied / pased. Does that work in B2evo?)

From wiki:

The inverted exclamation point can be entered by holding down the Alt key and pressing 0161, 173 or 8877 on the number pad.

Perhaps one of the other codes are valid in UTF-8, in which case it should be entered in _formatting.php in the section after line 688

Good luck


Form is loading...