Rendered Text Selection in JEditorPane's

Hello,
I am having trouble figuring out how the select(int, int) and its various other equivalents (i.e. sequential calls to setCaretPosition(int) and moveCaretPosition(int)) are used in JEditorPane's. Supposedly, if you call select(int, int),it does a setCaretPosition(int) and moveCaretPosition(int), but what is going on if my calls seem to fail without any exceptions (i.e. they seem to be executed but with no visible results rendered onto the component). In fact, the String that should be selected and returned by getSelectedText() is returned as null. However, when my calls are placed inside any listener in a nonconditonal context such that they are always called, then the selection happens. Is there something equivalent to update() or repaint() for JEditorPane's that I should be calling that is either undocumented or just obscure???
-J

I'm not sure whether this will help, seeing as you just upgraded, but worth a try:
If Dreamweaver is behaving in an odd way, it frequently means you have a corrupt personal configuration folder.
Close Dreamweaver, locate the personal configuration folder, and rename it.
When you restart Dreamweaver, it should create a new configuration folder with all the program defaults.   
For details of how to find the configuration folder, see this page in the Dreamweaver FAQ.
Nadia
Adobe® Community Expert : Dreamweaver
http://www.perrelink.com.au
Unique CSS Templates | Tutorials | SEO Articles
http://www.DreamweaverResources.com
http://twitter.com/nadiap

Similar Messages

  • Trying to OCR pdf, pdf says it can't perform bc it already contains renderable text-but does not.

    I work for a large agency, and we receive PDF's all the time. 98% of the time I am able to OCR a document with no issues. Just recently I have come across this issue several times, and was wondering if anyone can solve this irritating problem!
    *Acrobat 8.1 - When going to OCR the document, I receive the following message " Acrobat could not perform recognition (OCR) on this page because this page already contains renderable text. However, it does not. When you go to select text or search for anything the whole page is selected (like it's still in a "picture" format, not a document format that you can search, ect.)
    I am not sure if it is how the document is uploaded originally by the other party that causes this, but the only thing I can do as a work-around - is to print out the entire document, scan and then I can OCR the document just fine! The problem is, if the document is 400 pages or so, this can be a huge waste of time, and money just to be able to search the PDF.
    *I have also checked the pdf properties to see if this is some sort of permissions issue, and there are not permissions/security settings in place.*
    PLEASE HELP! Any assistance in this matter would save me a lot of time, and of course (my sanity!).
    Thank you in advance!

    While the alert speaks to "renderable text" that is a simplification. The issue is that you've PDF page content consisting of at least one renderable "character".
    Look at font families - you will observe that there are many characters that are not "text" characters (i.e., linguistic characters).
    So, there's a "renderable character" present. It may be an alpha numeric that has a font color the same as the page background. It may be under the image and thus not visible to the eye.
    You might be able to determine just what is present.
    You could export the page of interest to a text file then view that file.
    You could deplay the page of interest in Acrobat Pro then select the "Content panel" to view the content tree.
    Locate and click on the page number for the page of interest.
    From the Content panel's Options menu select "Highlight Content".
    Walk down the tree. Select the content containers in turn and observe what is highlighted on the PDF page.
    Where might the renderable character come from ? Typically that'd be associated with something in the work flow.
    Not always easy to find so don't take anything in the work flow for granted.
    Be well...

  • BUG - in flash pro CC, 'bold' and 'italic' properties of TextFormat have no effect on rendered text

    Concise problem statement:
    If you compile with flash pro CC, and use the 'setTextFormat' method of a TextField, the 'bold' and 'italic' properties of the TextFormat argument have no effect on the rendered text. If you compile with flash pro CS6, the 'bold' and 'italic' properties work as expected.
    Apparently, with flash pro CC, the only way to make the text render correctly is to change the font name (add the suffix ' Bold', ' Italic', or ' Bold Italic'.) This means code which dynamically changes font styles only works in CS6 or CC, but not both. For example, if you use the 'bold' property the text renders bold in CS6 and regular in CC, whereas if you change the font name to add the suffix ' Bold', the text renders bold in CC and DOES NOT RENDER at all in CS6. This makes it difficult to transition a team from CS6 to CC.
    Steps to reproduce bug:
    1. Create an xfl with 2 TextFields on the stage, both with font "Trebuchet MS" and style "regular", one named boldTrueText containing the String "bold = true", one named fontNameText containing the String "fontName = Trebuchet MS Bold". Create 2 more TextFields on the stage for visual reference, both with font "Trebuchet MS", one with style "regular", one with style "bold".
    2. Add the following code to the Actions panel on frame 1:
    import flash.text.TextFormat;
    import flash.text.Font;
    var format:TextFormat = boldTrueText.getTextFormat();
    format.bold = true;
    boldTrueText.setTextFormat(format);
    format = fontNameText.getTextFormat();
    format.font = "Trebuchet MS Bold";
    fontNameText.setTextFormat(format);
    var fonts:Array = Font.enumerateFonts(), count:int = fonts.length;
    for (var i:int = 0; i < count; i++) {
        var font:Font = fonts[i];
        trace("fontName: " + font.fontName + ", fontStyle: " + font.fontStyle);
    3. Save, and compile with flash pro CS6 and flash pro CC.
    Results:
    With flash pro CS6, "bold = true" renders bold, and "fontName = Trebuchet MS Bold" DOES NOT RENDER.
    With flash pro CS6, the following is traced:
    fontName: Trebuchet MS, fontStyle: bold
    fontName: Trebuchet MS, fontStyle: regular
    With flash pro CC, "bold = true" renders regular, and "fontName = Trebuchet MS Bold" renders bold.
    With flash pro CC, the following is traced:
    fontName: Trebuchet MS, fontStyle: regular
    fontName: Trebuchet MS Bold, fontStyle: bold
    Expected results:
    The same text is rendered in both flash pro CS6 and CC. I don't know why this behavior was changed in flash pro CC - it causes silent failures in code which dynamically changes font styles. I expected the flash pro CS6 behavior to remain the same in CC, like so:
    With flash pro CC, "bold = true" renders bold, and "fontName = Trebuchet MS Bold" DOES NOT RENDER.
    With flash pro CC, the following is traced:
    fontName: Trebuchet MS, fontStyle: bold
    fontName: Trebuchet MS, fontStyle: regular
    If you don't want to break backward compatibility (any further), you could make both the behaviors work in flash pro CC, like so:
    With flash pro CC, "bold = true" renders bold (font is still "Trebuchet MS"), and "fontName = Trebuchet MS Bold" renders bold also.
    With flash pro CC, the following is traced:
    fontName: Trebuchet MS, fontStyle: bold
    fontName: Trebuchet MS, fontStyle: regular
    fontName: Trebuchet MS Bold, fontStyle: bold
    I submitted this bug with the bug form, and also with adobe bugbase (in case it isn't obsolete) - I'm just trying to maximize my chances of getting a fix.  Has anyone else encountered this bug?

    I just can't believe how there is ZERO documenation for any of this.  Flash's stylesheets have fontStyle and fontWeight properties, but they only recognize regular/italic and regular/bold respectively.
    This change in Flash CC completely breaks systems built in Flash CS6, and the font naming is actually arbitrary and is not a consistant combination of font name and style (e.g. "Eras ITC" family's bold font name is "Eras Bold ITC", but the bold version of Times New Roman is "Times New Roman Bold" (with Bold at the end, rather than the middle), and what's absolutely appaling is that the font name used at runtime is not exposed anywhere in the Flash IDE!!!  In the IDE you select a font family and font style independently, which is absolutely not what's used at runtime, because it actually uses a separate, arbitrarily named field in the font file for the font name. So we can't even know from within Flash what the proper runtime name is, unless we trace it out or open the font properties details tab in Windows explorer.
    It seems that Flash CC is always using the font "Title" that can be found in the properties of the font, NOT the font name displayed in Windows Font Preview or in Flash CC.  For example, the font name for Times New Roman Bold in Windows Font Preview is just "Times New Roman", but the font title in the properties/details tab is "Times New Roman Bold".  If they made the change to allow for specific fonts to be selected, that's fine, but it completely breaks HTML support in TextFields if it's not respecting bold and italic tags.
    This may actually be a trend on the web now, if you read this: http://www.smashingmagazine.com/2013/02/14/setting-weights-and-styles-at-font-face-declara tion/ , it says: "If you’ve used one of FontSquirrel’s amazing @font-face kits, then you’re familiar with this approach to setting weights and styles. The CSS provided in every kit uses a unique font-family name for each weight and style, and sets the weight and style in the @font-face declaration to normal. [...] Notice that the font-family names are unique, with each font-family name accessing the appropriate Web font files."
    But there's just no mention of this in any documentation I can find.  What the hell.
    It's also helpful to realize that font and u tags have been deprecated in HTML5, while b and i tags have been repurposed since they still retain semantic meaning apart from style: https://www.w3.org/International/questions/qa-b-and-i-tags

  • Invoke-WebRequest - Unable to get rendered text

    Hi
    This issue exists in powershell but I suspect this issue will exist no matter what language is used.
    The problem is the rendered web page has chat text.
    However no matter what I do in powershell I can't get to this text.
    If I do a "view source" in IE or Chrome the text is missing, if I pipe the parsedhtml to a file, it is missing,
    So below you can see the original screen and F12 debug says the text lives inside "rooms-view-right-pane"
    Visibly you can see it, programmatically you cant see it
    >> So what is the magic that is missing , stopping me from capturing the rendered text ?
    Thanks in advance
    <div class="rooms-view-right-pane">
    </div>
    </div>
    </div>
    </div>
    </div>
    </div>

    Well for what it's worth, you can have what is below. I ain't proud of it - it's pretty dodgy, but in this example it retrieves points for a profile. The number of points does not appear in the source, only in the generated source. 
    It would be easy to keep it checking the page and comparing the new value for the points with the old...
    Like I said, there has to be a better way.
    GenSource.hta
    <html>
    <head>
    <title>GenSource HTA</title>
    <HTA:APPLICATION ID="oHTA"
    APPLICATIONNAME="GeneratedSource"
    SHOWINTASKBAR="no"
    ICON=""
    CONTEXTMENU="no"
    SCROLL="no"
    SCROLLFLAT="no"
    SELECTION="no"
    SINGLEINSTANCE="yes"
    SYSMENU="no">
    <meta http-equiv="x-ua-compatible" content="ie=9">
    <style type="text/css">
    <!--
    html {font:100%;}
    body {text-align:center;font-family:Arial,sans-serif;margin:0;padding:0 0 30px;filter:progid:DXImageTransform.Microsoft.Gradient(GradientType=0, StartColorStr='#0099ff', EndColorStr='#000000');}
    #wClose {width:15px;height:16px;float:right;margin:0 10px 0 0;padding:0;color:#ddd;background:transparent;border:1px solid #ddd;}
    #wClose:hover {color:#f00;}
    -->
    </style>
    <script type="text/jscript">
    window.onload=function(){
    window.resizeTo(500,350);
    window.moveTo ((screen.width/2-204),(screen.height/2-200))
    wClose.onclick=function(){close();};
    document.all.frame1.src="https://social.msdn.microsoft.com/profile/greg%20b%20roberts/?ws=usercard-mini";
    function frameloaded(){
    var frameEl=document.frames["frame1"].document.getElementById("points");
    if(!frameEl||frameEl.innerHTML=="-"){setTimeout(frameloaded,500);}
    else{
    el.innerHTML=document.frames["frame1"].document.getElementById("displayName").innerHTML;
    el2.innerHTML=frameEl.innerHTML+" points";
    </script>
    </head>
    <body>
    <div id="wClose">X</div>
    <iframe width="500" height="200" id="frame1" onload="frameloaded();">Test Page</iframe>
    <div id="el" style="font-size:20px;color:#fff;width:500px;height:30px;margin-top:20px;"></div>
    <div id="el2" style="font-size:20px;color:#fff;width:500px;height:30px;margin-top:20px;">Loading...</div>
    </body>
    </html>

  • Highlight Text PROGRAMMATICALLY in JEditorPane

    Hi,
    I am printing some text on a JEditorPane. I want to highlight some words in a diffferent color. I want to do that programmatically. I have tried select(), setSelectionStart, setCaretPosition and everything. But in vain.
    Can someone please help?
    Thanks in advance
    sjl

    You need to play with attributes. This thread should get you started:
    http://forum.java.sun.com/thread.jsp?forum=57&thread=342068

  • Text select tool not working properly

    When I use the text select tool, it selects columns, not words in a row, which is what I want. It used to work correctly. I am using Acrobat Pro, version 9.0.0.
    I tried adding the ALT key, with no good result.

    Is it with this specific document o any pdf you work on?
    If it was earlier working fine for you, try repairing Acrobat  by going to 'Help' menu > Repair Acrobat.
    Also make sure you have updated it to the latest patch.
    Regards,
    Ravi.

  • Rendered text problems in 5.1.2

    I am working on a film project that has a lot of subtitles. (The dalies are digitized at HD DVC-Pro 720p) I was editing on a station running Final Cut Pro 5.1.1 (g5) with no real problems. I recently took the project with me on a trip to work on using my macbook pro (intel) running 5.1.2. I have discovered that all of my rendered text in my timelines is now uneditable. I can't move the text, I can't change the text, I can't even delete the text. I also can't change any of the footage running underneath the rendered text. It has become an immutable part of my film. This is obviously a huge problem. Has anyone else run accross this problem? Is it something that Apple is aware of? Any fixes? If not I may have to move to Avid and start all over again.

    Not that strange, really. Several different NLEs can sometimes lock onto a render file and not update the output until that render file is deleted.
    Rather simple fix, just a little time consuming.
    Next time don't be so quick to threaten to jump ship. First problem and you were ready to move to Avid. I've had more problems working on Avids than I have on FCP. MANY more problems. FCP problems are usually due to user error or third party hardware. Avid problems shut you down for a couple weeks while you ship out your hardware.

  • How can I change a the dropdown menu background according to the text selected?

    How can I change a the dropdown menu background according to the text selected?

    Read here about how to use the color object correctly:
    http://livedocs.adobe.com/acrobat_sdk/9.1/Acrobat9_1_HTMLHelp/wwhelp/wwhimpl/common/html/w whelp.htm?context=Acrobat9_HTMLHelp&file=JS_API_AcroJS.88.260.html
    http://livedocs.adobe.com/acrobat_sdk/9.1/Acrobat9_1_HTMLHelp/wwhelp/wwhimpl/common/html/w whelp.htm?context=Acrobat9_HTMLHelp&file=JS_API_AcroJS.88.261.html

  • "resolving alias to" message using aliases on 10.6.8 plus slow text-selection behavior

    Recently after no particular change to my Mac Pro3,2 running 10.6.8 other than some routine software updates, whenever I open an alias on my desktop to standard folders or files, a message shows up "Resolving alias to" whatever the alias name and there's a 2-3 second delay before the folder/file opens. I've found discussion of this issue in some archived discussions but never found a comfirmed solution described, so I'm raising this again. As in others' encounter with this behavior, the slow opening of aliases happens (1) only in my own user account, not in a guest account I set up for test purposes [I have no other user accounts than these], and (2) only happens the FIRST time I open an alias. Subsequent uses of the alias work normally.
    Another strange but possibly related behavior that began at the same time as this alias delay is harder to describe but involves a problem when selecting text using mouse clicks or even highlighting with the mouse for editing. For example, to edit the name of a file or folder on my desktop, I would normally click on the file/folder name, pause a moment and click again: this puts me in edit mode with the current file/folder name highlighted/selected. Now when I attempt this procedure, the second time I click immediately opens the file/folder, as though I had double-clicked rather than clicked+paused+clicked. The only way I can select the name of the file/folder to edit it is to click+long pause (like 3 seconds)+click. Then the text is selected as desired. It's as though the clicks are being recognized (by whatever in the OS recognizes clicks) as much faster than actually made.  There is a similar problem in any program I use that permits text editing, whether Word (Office 2011 for Mac), TextEdit, etc. I have to consciously slow down my cursor/click behavior when selecting text. If not, my actions are misinterpreted as double clicks. This text selection behavior also disappears when using a "Guest" user account, only appearing in my own user account. I Using a different mouse has no effect.
    Steps taken so far. I've Repaired Disk Permissions and Verified Disk using Disk Utility, have Safe Booted, and have turned off all login items in my user account,and recently installed the 10.6.8 supplemental update, all to no avail. Any suggestions or has anyone had and solved this/these problems?

    I think my problem has been that in Sytem Preferences>Mouse, my "Double-Click Speed" was set to the SLOWEST setting. After some experimentation, I now have the that setting two notches from the "Fast" end of the scale. In case it's important, the "Primary mouse button" in my Preferences is set to "Left".
    This not only solves the text selection issues described, but also seems to eliminate the strange "resolving alias to" problem.
    [For the curious, I have a Logitech Performance MX wireless mouse which can be configured with "Logitech Control Center". But the LCC software doesn't control double-click speed; this setting can only be made in the Mouse System Preference pane.]

  • Text Selection Hangs Since iOS 5.1.1 Update

    I have an iPhone 4 32GB on the AT&T network.
    Updated it to iOS 5.1.1 about two weeks ago.
    Since the update multiple applications (Apple and 3rd Party) have been showing this behavior:
    1) Click in a text entry or text area form field,
    2) Begin typing text,
    3) Touch anywhere in the field to bring up the monicle selection caret,
    4) The monical selection caret is shown and I can move the monical/caret around the screen,
    5) Un-touch the screen,
    6) ERROR - The monicle and the selection caret don't respond to user touch input and the app/OS hang for anywhere from 5 to 15 seconds,
    7) The standard "Select | Select All | ..." context pop-up window is shown, after that the app/system are responsive again. 
    Regarding the ERROR at step 6) above: Clicking Home does nothing, turning on/off with top-button does nothing, force shutdown responds only after the monicle/caret selector un-hangs.
    Once this has happened in a given text field/text area, it doesn't happen again on a subsequent text selection touch event... UNLESS I sleep the device, wake the device on the same app/field and try to select again... then it hangs again.
    To note, while it's hanging the loading-spinner is displayed in the title bar next to the AT&T 3G/Wifi Antenna icons, suggesting something in the background is doing a network search that's locking then entire foreground process.
    I've attempted to:
    1) hard reset the device,
    2) restore from a backup of 5.1 (doesn't have the aforementioned problem) and reinstall the 5.1.1 update (has the problem)
    3) swear at it and curse Steve Job's mock-turtleneck for allowing such a peice of **** bug to exist (even if it's not his fault ex post homine)
    Any further help would be great... I may end up downgrading to 5.1 just to not have to deal with this perpetual headache.
    Thanks,
    Etienne

    I'm having the same issue.  Phone started to degrade after update to 5.1.1  I have restarted, reset and restored from backup. I haven't tried to restore as new, as I'm not sure what the impact will be in my need to reset my corporate exchange e-mail, etc. 
    I see from many posts on other boards this is not isolated and is impacting many users. I'm using verizon as a the cell carrier. 
    My phone is warm and eating battery at a rate of 10% per half an hour in standby mode. No new apps or anything else of that nature.
    Tinus Barnard wrote:
    Will they fix this?

  • Reading text file to JEditorPane

    Hi,
    I'm trying to read text file to JEditorPane and it works but first line is always missing. Here is the code for reading:
    try {
       in = new BufferedReader(new FileReader(filePathIn));
       while ((lineIn = in.readLine()) != null) {
            editorPane.read(in, new Object());
    } catch (IOException ie)...Any suggestions?

    in.readLine is changing the input stream position.
    Do this instead:
    FileInputStream in = new FileInputStream(filePathIn);
    while (in.available() != 0)
        editorPane.read(in, new Object());

  • Preview's PDF text select ignores columns and misses word spaces

    I have a number of scanned pdf newspaper articles that I was attempting to copy the text from. Preview appears to register the existence of columns, as there is a pale blue background between the columns.
    However when I use the text select tool, it completely ignores the column - and just selects across all columns. And when I paste the text into my text editor, it's missing all the spaces between the words, and the font size is always huge.
    Conversely, Adobe reader in XP has no problem selecting by column, and the pasted text is also an exact replication of the original content. I don't know why Preview performs so badly in this regard? Anyone else experience any issues with pdf text select?

    Anyone else experience any issues with pdf text select?
    Yes, and not just recently.
    There is a reason Preview is named, well, preview. It is not an authoring environment and PDFs are not meant to serve in that context either...unless maybe you understand all of inherent the font traps, tricks & tips and how to tune your scanning/OCR software to keep rework to a minimum.
    Scanning PDFs is always tricky, and without the occasional heavy metal to bring to the task, it just seems to be that more problematic.
    Keep trying, but I'd really suggest to look to other tools at this time.

  • How to recognize text in XI Pro when files returns "renderable text" error.

    This same file will recognize text & provide searchable document in Adobe 9.
    I saw workaround to convert each page to TIFF, do OCR on each page, convert each back to pdf & combine. That is ridiculous. Will there be a new version of XI Pro that will work correctly for OCR?

    Varinder.Saini wrote:
    David,
    That is how it is. If you run Searchable Image or Searchable Image (Exact), Acrobat will throw error only for pages that contains renderable text. It also gives an option to ignore these error for any further pages containing renderable text.
    If you check this option it will run OCR for rest of the pages and won't show the error again for that PDF.
    This option is not available when OCR'ing using Adobe ClearScan -- ClearScan being the ONLY reason anyway why I own Acrobat Pro AT ALL -- for it's otherwise ridiculous slowness compared to its competitors. Sorry having to tell you that, from the point of view of having worked in a paperless law office for 15 years, therein 4-9 hrs a day with PDF documents usually in the 600 to 1.800 page range.
    CtDave wrote:
    Precluding the entry of anything 'renderable' assures OCR will be accomplished for each page.
    David Peters wrote:
    Just stop bullshitting users about "you better follow well defined protocols" niminy-piminy-finicky.
    There is zillions of cases where one does not have ANY control neither access to the (external) creation of one's PDF files, even if people like you seem to be unable to imagine, and therefore repeat the same pointless sermon over and over that does not add ANYTHING to the case.
    The solution to this problem by the way is not a question of more (lost) decades of rocket science Adobe bloatware engineering, but simply:
    If there is "Renderable Text" somewhere on some fuⅽʞing page:
    then just SKIP IT and continue OCR with the next fuⅽʞing bitmap
    gosh darn it.
    Not that I would hope that any of this would change anything with the course of the megaton tanker Adobe which I usually avoid like the plague -- with the only two exceptions of ClearScan and of course, Acrobat 7 Pro, the last Acrobat version that was not only fairly usable but actually is a pretty amazing piece of software.

  • Keyboard shortcuts for text selection not working in Flash CC

    In the new Code Editor in Flash CC running on Mac OS X, most standard Keyboard Shortcuts for traversing through the text work as expected (as the Operating System works globally) but there is one that doesn't and it's I think the most important one.
    Hitting "OPTION + SHIFT + [right or left arrow keys]" to select words doesn't work. Hitting "OPTION + [right or left arrow keys]" works as expected, moving the cursor to the next word or break point, but adding shift doesn't do the selection.
    I don't understand why this changed since it's a basic OS global shortcuts, and every other program behaves the way it should. Flash CS6 running on the same system behaves fine, but Flash CC doesn't. If you have ever written code, you know that any second that a programmers hand doesn't have to leave the keyboard to search for the mouse is invaluable, and this has forced me to stop using Flash CC and use Flash CS6 to edit my Action Script classes becuase it's unusable otherwise.
    These shortcuts are also not listed in the keyboard shortcuts for the program, so I can't change the default behavior. Does anybody know if there's a way to set it back to the way it was before, or just disable special text shortcuts so that selecting text behaves like any other application in the operating system?
    System Configuration:
    Flash CC
    Mac OSX 10.8.5

    Amy~ Yep the lasso tool was what I verified with another user. 'L' seems to be bound indefinitely to loop through different types of lasso tools and it was annoying them because they just wanted L to be the regular freehand lasso. I removed 'L' from being an option on the polygon lasso and even set it explicitly to SHIFT+L as well as set the lasso tool to a completely different keyboard combo. 'L' still cycled through lassos haha. It needs some fixes.
    fertolg~ At least you have a workaround for now. I'd go nuts if I couldn't use keyboard text selection writing code, oy! You're welcome and if you're all set please mark correct so we can filter unanswered. Good luck!

  • Which event dispatched after text selection done on spark text area in Apple iPad using Adobe Flex 4

    I need to know which event triggered after text selection done in Apple iPad. This way i have done in desktop air app code (mouse events)
    protected function txtEditor_mouseUpHandler(event:MouseEvent):void
                if(txtEditor.selectionAnchorPosition != txtEditor.selectionActivePosition){
                    showNoteToolBar(event);
                    txtEditor.focusEnabled = true;
                    txtEditor.setFocus();
    But in Apple iPad how to achieve through "Touch Event" ? And also i need how to hide all context menu on Spaek TextArea?. Why Touch.End event is not fired after place cursor on text area ?
    Please help me !

    Ok, so I finally got it working but this is not ideal at all. Adobe really needs to give us some direction on how to properly deal with font embedding and TLF now that the release build breaks all functionality with loading runtime fonts and TLF.
    Problem:
    I am embedding collections of fonts (faces) into single family classes. Each individual face is registered with Font.registerFont(). I need to do this because I have to have mixed fonts within text flows - at least according to Alex H's recent blog post.
    Fonts do not display in TLF without doing the following:
    1. GlobalSettings.resolveFontLookupFunction = null;
    2. editor.textFlow.flowComposer.swfContext = ISWFContext(this.getFontContext("AnyFamilyNameFromAnyFontEmbedded", false, false, FontLookup.EMBEDDED_CFF));
    3. Instead of #2, use editor.textFlow.invalidateAllFormats();
    Either #2 or #3 need to be performed. If I have a spark richEditableText control in MXML with defined familes from the loaded fonts. I even tried placing the control into a separate state so it wasn't created until after the fonts were loaded... I still needed to invalidate the formats or set the context.
    The "AnyFamilyNameFromAnyFontEmbedded" does not need to be all of the embedded family names. It only needs to be one of them. Once one is used, all embedded fonts work. Also, I have to use the internal namespace to even get access to getFontContext, another oddity that, in my humble opinion, should never be necessary to create mixed style TLF content.
    My questions are then:
    1. Why am I required to use ISWFContext if I am using Font.registerFont()?
    2. Why is GlobalSettings.resolveFontLookupFunction = null; also required for this to work?
    3. What is the recommended workflow to embed fonts from multiple SWF files into the release build and have it work without having to jump through all these hoops?

Maybe you are looking for