[FairfieldLife] Re: FFL Rich Text Editor Encoding Test quot; quot; #8220; #8221; â â
--- In FairfieldLife@yahoogroups.com, turquoiseb no_reply@... wrote: It has also started being picky about how many graphics you can paste in. In the past I was able to add 2-3 graphics to the same post, no problem. Now when I do that it allows me to send the post, but displays Truncated at ??K at the bottom, and shows only the first one. It's 64K, FYI. And it doesn't limit you to only one graphic. Posts not composed in the Rich Text Editor have always been truncated if they were beyond a certain length. They probably decided to apply a limit to Rich Text Editor posts too because people were abusing the ability to include graphics. If you want to put in lots of graphics, try making them smaller; you may be able to fit more in. What the Rich Text Editor *should* do is show you a notice before you post if you've gone over the limit.
[FairfieldLife] Re: FFL Rich Text Editor Encoding Test quot; quot; #8220; #8221; â â
Also, you might try using standard HTML in the rich-text editor. Xenophaneros Anartaxius: This is a test of Fairfield Life's Yahoo Groups Rich Text Editor, to see how it supports standardised character encoding. 1. Straight Double Quotes (HTML): 2. Straight Double Quotes (XHTML) 3. Curly Double Quotes (Unicode UTF-8 / Mac OS X): â â 4. Curly Double Quotes (Windows): â â [not legal in UTF-8] 5. Em-Dash (Unicode UTF-8 / Mac OS X): â 6. Em-Dash: â (Windows) This editor seems to change some content, and certain characters do not seem to display properly, especially when cut and pasted into the subject line which is why some of us might see strange symbols in certain posts. The result also depends on how a web browser is set to display characters, or how an email reader interprets characters. The changes made by this editor look OK in preview mode, but once posted the result might be different. This happened to me in a post where a sequence of Greek letters was used, and it looked fine -- until I sent it in.
[FairfieldLife] Re: FFL Rich Text Editor Encoding Test quot; quot; #8220; #8221; â â
I had not thought of using an entire HTML page, as these posts will display in an HTML page, which already has the basic HTML layout and multiple tags are not good. But a test shows that many HTML tags get stripped out after leaving the HTML source view, and character encodings change, not only between preview and editing mode, but between preview, editing, and actually posting. The yahoo groups page is in HTML 4.01 (but the code seems to be XHTML which is not right) and the character set is not defined, so browsers in which the page is viewed will display these odd characters differently depending on their settings. A certain lack of consistency. --- In FairfieldLife@yahoogroups.com, WillyTex willytex@... wrote: Also, you might try using standard HTML in the rich-text editor. Xenophaneros Anartaxius: This is a test of Fairfield Life's Yahoo Groups Rich Text Editor, to see how it supports standardised character encoding. 1. Straight Double Quotes (HTML): 2. Straight Double Quotes (XHTML) 3. Curly Double Quotes (Unicode UTF-8 / Mac OS X): â â 4. Curly Double Quotes (Windows): â â [not legal in UTF-8] 5. Em-Dash (Unicode UTF-8 / Mac OS X): � 6. Em-Dash: � (Windows) This editor seems to change some content, and certain characters do not seem to display properly, especially when cut and pasted into the subject line which is why some of us might see strange symbols in certain posts. The result also depends on how a web browser is set to display characters, or how an email reader interprets characters. The changes made by this editor look OK in preview mode, but once posted the result might be different. This happened to me in a post where a sequence of Greek letters was used, and it looked fine -- until I sent it in.
[FairfieldLife] Re: FFL Rich Text Editor Encoding Test quot; quot; #8220; #8221; â â
It has also started being picky about how many graphics you can paste in. In the past I was able to add 2-3 graphics to the same post, no problem. Now when I do that it allows me to send the post, but displays Truncated at ??K at the bottom, and shows only the first one. Also, as you'll notice if you try to view this post in a browser using the Yahoo reader, it does not support extended characters in Subject lines. The same characters that work fine in the body of a post turn into ASCIIcrap in Subject lines. --- In FairfieldLife@yahoogroups.com, Xenophaneros Anartaxius anartaxius@... wrote: This is a test of Fairfield Life's Yahoo Groups Rich Text Editor, to see how it supports standardised character encoding. 1. Straight Double Quotes (HTML): 2. Straight Double Quotes (XHTML) 3. Curly Double Quotes (Unicode UTF-8 / Mac OS X): â â 4. Curly Double Quotes (Windows): â â [not legal in UTF-8] 5. Em-Dash (Unicode UTF-8 / Mac OS X): â 6. Em-Dash: â (Windows) This editor seems to change some content, and certain characters do not seem to display properly, especially when cut and pasted into the subject line which is why some of us might see strange symbols in certain posts. The result also depends on how a web browser is set to display characters, or how an email reader interprets characters. The changes made by this editor look OK in preview mode, but once posted the result might be different. This happened to me in a post where a sequence of Greek letters was used, and it looked fine -- until I sent it in.
