Darkpony CS

+Clients
  • Content count

    19
  • Joined

  • Last visited


About Darkpony CS

  • Rank
    IPB Newbie

Contact Methods

Profile Information

  • Gender Male
  • Location UK, Greece, Cyprus
  • Interests Internet technologies

Darkpony CS's Activity

  1. Darkpony CS added a comment: Random Capitalization of letters in the text   

    Since 3.3 is not coming very soon, it would be better if you patch those files and offer them as a [b]separate download now[/b].

    People that run communities using non-Latin encoding CANNOT use IPB 3.2.x properly, it's a no go. Simple as that.

    Are those customers such a minority?
  2. Darkpony CS added a comment: Random Capitalization of letters in the text   

    Matt does the solution you propose solve the problem of storing text as utf-8 instead of HTML entities?
  3. Darkpony CS added a comment on a file: (JG32 / JG33 / JG34) Forum Spammer IP & Email Check via Stop Forum Spam   

    Isn't the IPS Spam Service doing something similar to this?
  4. Darkpony CS added a comment: Random Capitalization of letters in the text   

    The whole problem rests in the fact that CKEditor (and most WYSIWYG editors) convert non Latin characters to HTML Entities...

    If you watch carefully you'll see that even after applying the solutions above, they only thing that happens is to "convert" those entities without any errors, thus people see all the characters as they were supposed to be seen.

    BUT underneath all text is being stored as HTML Entities and not as UTF on the Database, which is not ideal for many reasons (thing about a massive forum and the overhead of using HTML Entities for each character!!!).

    The PROPER solution to this is to tell CKEditor [b]NOT[/b] to convert Greek, Cyrillic etc. characters to HTML Entities but treat them as normal UTF text. This way there is no bug at all.

    The current (default) setup [b][u]does[/u][/b] make sense for users that use [b]Latin characters[/b] and very rarely have a couple of Greek characters in their posts. This way they can use a different encoding (e.g. ISO-8859) and still have those characters displayed properly (since they are stored as HTML entities).

    If a board uses Greek or Cyrillic as the [b]main language[/b] then THERE IS A PROBLEM! Obviously we do not want ALL our text to be stored as HTML Entities. This is the main language so what's the point doing that?


    [b]SIMPLE SOLUTION:[/b]

    Go to [b]public/js/3rd_party/ckeditor[/b] and add the following line to [b]ips_config.js[/b]

    [CODE]config.entities_greek = false;[/CODE]

    additionally, there is an option to disable entities globally but needs some testing.


    [b]PROPER SOLUTION (maybe via patch or 3.2.4): [/b]

    Switch this option by having a drop down box somewhere under ACP for the languages that have this issue.


    [b]EVEN BETTER SOLUTION:[/b]

    Combine the proper solution above with the option to use the standard editor we all loved those years.

    Regards
  5. Darkpony CS added a comment on a blog entry: IP.Content 1.2.0 on its way   

    Nice step forward, it starts taking shape.
  6. Darkpony CS added a comment on a blog entry: IP.Content 1.2.0 on its way   

    I really like the attachment improvements...
  7. Darkpony CS added a comment on a blog entry: IP.Content 1.1.2   

    [quote name='MindTooth' date='23 November 2009 - 11:55 PM']
    Would care to see some API to retrieve data from the forum. An update to IP.Content is well received.

    Birger :)


    I'm looking forward to such a feature. Creating a database of articles and automatically "Promoting" selected post from the forum to articles... either as straight copies of just references.

    Ideally, the admin or a moderator could see a icon similar to "Blog This" (for those who have IP.Blog installed) like "Article This". This is a must feature in my opinion.

About Me

Status Feed

  1. Darkpony CS

    Where is Blog This???