Not signed in (Sign In)

Categories

Vanilla 1.1.1 is a product of Lussumo. More Information: Documentation, Community Support.

UNSTABLE Releases: [0.3.1.734] Unable to open tiny_mce.js

Bottom of Page

1 to 3 of 3

  1.  
    • CommentAuthorTymlis
    • CommentTimeJun 5th 2008 edited
     permalink
    Hello,

    I'm using the Intype Alpha 0.3.1.734 Unstable and I can't open a specific javascript file.

    The file is the main file from the tinyMCE WYSIWYG Javascript editor, it is kind of compressed (anything on the same huge line) and about 150Ko.

    You can find it at http://prdownloads.sourceforge.net/tinymce/tinymce_3_0_9.zip?download
    It is the tinymce/jscripts/tiny_mce/tiny_mce.js.

    Intype just take some time to open the file and then it only display a blank page without any code, just one empty line.

    I do not really need to edit this file as there are development (unpacked) versions of this file available, but I thought I shared this information here.

    HTH
    • CommentAuthormartincohen
    • CommentTimeJun 5th 2008 edited
     permalink

    Tymlis: Well, Intype currently has a limitation in max-line length (max. of 65536 UTF-16 “characters”) that is not handled properly. There are two sourced for the limitation:

    • Unicode Processor using Microsoft standard Uniscribe API to process the text has many bugs (especially with longer strings) that are not covered in the currently available builds. The 0.3.5 has a new version that covers all known bugs to Uniscribe API. We will do tests with long lines respectively.
    • Parser is using 16-bit values for line offsets, and is aggressively limited to not process lines longer than 65535 characters. We have designed the solution (with keeping the same storage efficiency), but because we are going to do some more changes to the parser, we will do it later and altogether; definitely after 0.3.5 is released.

    Of course, with longer lines (especially with > 65536), there will always be some performance or visual issue (for example a text not parsed after the limit), but it actually will not be as surprising as current “behavior” is.

    • CommentAuthorTymlis
    • CommentTimeJun 6th 2008
     permalink
    Thanks for your explanation, Martin.

1 to 3 of 3

  1.