Text in Lectora 12

I noticed that this thing happened in IE8 and Lectora V11 too when you used fade or float transition in text objects. Could this be the reason?

Just tried it and it's not correcting the problem.

is your text box set to convert to image? if it is try unchecking it

Hi Marco,

Can you also let our support team know please? We rely on that reporting to catch these issues. Here is the link:

http://lectora.com/contact-support/

Yours

Simon

Hello ummakumma,

thanks for that - but the posted example is a text box without any transitions effects. Just a clean Lectora-Project with only this simple textbox...

For the moment I've found a workaround: I have changed the line 175 of the file trivantis-text.js from this:

if(is.ie8)[/CODE] to this [CODE] if(!is.ie8)[/CODE]. This works fine as a temporary solution, but I'm not sure if there are any sideeffects.

So I'm still looking for a 'real' solution for this problem.

Cheers,

Marco[CODE] if(is.ie8)[/CODE] to this if(!is.ie8)[/CODE]. This works fine as a temporary solution, but I'm not sure if there are any sideeffects.

So I'm still looking for a 'real' solution for this problem.

Cheers,

Marco[CODE] if(!is.ie8)[/CODE]. This works fine as a temporary solution, but I'm not sure if there are any sideeffects.

So I'm still looking for a 'real' solution for this problem.

Cheers,

Marco

I'm using notebook to edit the file. Is there an easy way to find line 175, besides counting?

@jgraunke 62893 wrote:

I'm using notebook to edit the file. Is there an easy way to find line 175, besides counting?

Hello jgraunke - I'm using notepad++ and here I can use CTRL undefined this shortcut also works in dreamweaver and notepad - maybe also in your favorite text-editor.

@simonbirt 62905 wrote:

Hi Marco,

Can you also let our support team know please? We rely on that reporting to catch these issues. Here is the link:

http://lectora.com/contact-support/

Yours

Simon

Thanks Simon - I just sent a message to the support team.

@felipe 62906 wrote:

is your text box set to convert to image? if it is try unchecking it

No - the 'convert to image' flag isn't checked.

@marco.meissner 62889 wrote:

Hello ummakumma,

thanks for that - but the posted example is a text box without any transitions effects. Just a clean Lectora-Project with only this simple textbox...

For the moment I've found a workaround: I have changed the line 175 of the file trivantis-text.js from this:

if(is.ie8)[/CODE] to this [CODE] if(!is.ie8)[/CODE]. This works fine as a temporary solution, but I'm not sure if there are any sideeffects.

So I'm still looking for a 'real' solution for this problem.

Cheers,

Marco

Thank you. I remember doing this with Lectora X.11 when it first came out as well. This worked perfectly. I made this change in the main file in the support files folder this way it goes into all publishes.

If anyone does this, back up the file first so you can replace it before a patch. I have seen patches fail because of a single file mismatch.[CODE] if(is.ie8)[/CODE] to this if(!is.ie8)[/CODE]. This works fine as a temporary solution, but I'm not sure if there are any sideeffects.

So I'm still looking for a 'real' solution for this problem.

Cheers,

Marco

Thank you. I remember doing this with Lectora X.11 when it first came out as well. This worked perfectly. I made this change in the main file in the support files folder this way it goes into all publishes.

If anyone does this, back up the file first so you can replace it before a patch. I have seen patches fail because of a single file mismatch.[CODE] if(!is.ie8)[/CODE]. This works fine as a temporary solution, but I'm not sure if there are any sideeffects.

So I'm still looking for a 'real' solution for this problem.

Cheers,

Marco

Thank you. I remember doing this with Lectora X.11 when it first came out as well. This worked perfectly. I made this change in the main file in the support files folder this way it goes into all publishes.

If anyone does this, back up the file first so you can replace it before a patch. I have seen patches fail because of a single file mismatch.

Same issue here at my company.

Text looks awful in IE8. Looks fine in Chrome for us. Possible issue with the CSS files?

Hello - here is the answer I received from the Trivantis support:

It is due to the Microsoft CSS filter they had to add to support rotation and opacity set to anything other than 100. IE8 is not able to handle this and causes issues with the text display. In an upcoming service pack, they are going to not include this filter for standard text blocks that are not using rotation or opacity. For text blocks that do, this will still be an issue, as there is no way around it, as this Microsoft CSS filter is required. For those text blocks, you can try a workaround or adding a background color to the text block to see if that helps at all.

So it looks like it will be fixed in the next update.

Regards,

Marco