From jan at wischnat.de Tue Nov 1 08:24:14 2005 From: jan at wischnat.de (Jan Wischnat.de) Date: Tue, 01 Nov 2005 08:24:14 +0100 Subject: [TYPO3-content-rendering] accessible sites In-Reply-To: References: Message-ID: > I'd like to get a list together of accessible websites or websites that > comply to XHTML1.0 strict made with TYPO3. I know greenpeace.de is one > of them. Please let me know the sites you have built and what > (extensions) you used to get it accessible/xhtml compliant. We > definitely need some examples as showcases. Hello Ben, hello list, here's some of "my" sites validating xhtml *trans*: Touristic bavarian Village http://www.schwangau.de (gov_accessibility, css_styled_imgtext) TYPO3 e-Government http://gov.typo3.com (template_t3_2005 - non public [1], css_styled_imgtext) German Red Cross http://mustervorlage.drk-cms.de/index.php?id=dokucms (template_drk - non public [1], css_styled_imgtext) VKIB (people taking care of the handicapped) http://vkib.de (template_drk - non public [1], css_styled_imgtext) My own site http://wischnat.de (template_drk - non public [1], css_styled_imgtext) At the moment i am working on a relaunch of schwangau.de. See a beta preview here: http://www.schwangau.de/1072.html It's based on Ruthsarian's Skidoo Template. I will publish this new template in december in the TER hth Jan [1] Not in TER, send me a mail if you want a copy :-) From jan at wischnat.de Tue Nov 1 09:17:08 2005 From: jan at wischnat.de (Jan Wischnat.de) Date: Tue, 01 Nov 2005 09:17:08 +0100 Subject: [TYPO3-content-rendering] stdWrap for ATagParams In-Reply-To: References:

Message-ID: > Keep an eye on the upcoming TYPO3 4.0, there are lots more stuff being > fixed, and the content rendering group is involved in it! ;) Ernesto, a big R E S P E C T, THANKS and THUMBS UP for your efforts! :-) Jan From ben at netcreators.nl Tue Nov 1 22:03:29 2005 From: ben at netcreators.nl (ben van 't ende [netcreators]) Date: Tue, 01 Nov 2005 22:03:29 +0100 Subject: [TYPO3-content-rendering] UPDATE Re: double rendering of In-Reply-To: References:

Message-ID: Peter Niederlag wrote: > Hi Ben, > > ben van 't ende [netcreators] schrieb: > >>Hi, >> >>So now I have a real content rendering problem I can't fix! Rupert has >>spent an hour on it. Which could mean anything ;-) Well here it is. I >>have two installations on 3.8 that give these results in the source: >> >> >> >>> PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" >> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> >> >> >> >>That's on http://demo2.netcreators.nl >> >>Obviously as you can see is repeated. When I refresh the >>page and get it out of the cache the problem is gone. I tried commenting >>out several config options and some extensions, but there seems no way >>to get rid of it. >> >>Does anyone have an idea how to troubleshoot this? > > > Use the Typoscript-Debugger in the AdminPanel(FE) to see where it is > inserted twice. I never encountered this problem so I would expect some > misconfiguration or a bad extension. Of coure it is also possible I > missed some bug. > > Things like this happen easily if you use a HTML-template with the > TEMPLATE-cObject and forget to use an 'workOnSubpart=###FOO###'. > > Gimme a login (PM) and I'd like to have a look. tHNx to Peter we found out it was a bug in an installed extension. We could not see this because fe_compression was on in the install tool. So if you want to troubleshoot. Turn fe_compression off. gRTz ben -- netcreators::creation and innovation www.netcreators.nl - www.typo3.nl From michael.haugg at memmingen.de Wed Nov 2 09:48:36 2005 From: michael.haugg at memmingen.de (Michael Haugg) Date: Wed, 02 Nov 2005 09:48:36 +0100 Subject: [TYPO3-content-rendering] Integrating Accesskeypad - Hello... In-Reply-To: References:

Message-ID: > Multiple open tabs or not? Yes, Michiel, with multiple tabs open. I tested last weekend also with Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429 Firefox/0.8 multiple tabs an d had no problems at all. But may I ask you if I get you right? I understand, that If you use (any) Firefox and there are e. g. two Tabs open, [Alt+1] and [Alt+2] are then used for switching tabs and no longer availible as Accesskeys. Is it that what you mean? Well, I can't confirm this. Alt+1 and Alt+2 had always worked fine. I have not even found a way to change tabs with shortcuts. Regards, Michael From news at monosock.org Wed Nov 2 17:37:28 2005 From: news at monosock.org (Michiel Roos) Date: Wed, 02 Nov 2005 16:37:28 +0000 Subject: [TYPO3-content-rendering] Integrating Accesskeypad - Hello... References:

Message-ID: On Wed, 02 Nov 2005 09:48:36 +0100, Michael Haugg wrote: > I understand, that If you use (any) Firefox and there are e. g. two Tabs > open, [Alt+1] and [Alt+2] are then used for switching tabs and no longer > availible as Accesskeys. Is it that what you mean? Well, I can't confirm > this. Alt+1 and Alt+2 had always worked fine. I have not even found a > way to change tabs with shortcuts. Yes this is what happens exactly. From info at unlimited-vision.net Wed Nov 2 19:18:58 2005 From: info at unlimited-vision.net (Sacha Vorbeck) Date: Wed, 02 Nov 2005 19:18:58 +0100 Subject: [TYPO3-content-rendering] A statement Message-ID: Hi, I like this: http://help.joomla.org/content/view/805/60/ -- Ciao, Sacha From ao-lists at php4win.de Thu Nov 3 10:05:52 2005 From: ao-lists at php4win.de (Andreas Otto) Date: Thu, 03 Nov 2005 10:05:52 +0100 Subject: [TYPO3-content-rendering] A statement References: Message-ID: +1 -- Let your compiler do the simple optimisations. Don't strain to re-use code; reorganise instead. - The Elements of Programming Style (Kernighan & Plaugher) From michael.haugg at memmingen.de Fri Nov 4 09:01:02 2005 From: michael.haugg at memmingen.de (Michael Haugg) Date: Fri, 04 Nov 2005 09:01:02 +0100 Subject: [TYPO3-content-rendering] Integrating Accesskeypad - Hello... In-Reply-To: References:

Message-ID: Hello Michiel, I tested again and - shame on me - you're right. I tried again Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Firefox/1.0 (Ubuntu package 1.0.2) and a friend tested for me Firefox on a Fedora System and it happens what you say. BUT: I tested also again on varios Firefoxes on Windows and had no problems at all. (and it was right when I said that on [Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429 Firefox/0.8] there were also no problems, maybe due to the old version) I searched a bit in the internet and have found: http://kb.mozillazine.org/Accessibility.accesskeycausesactivation Curiosly there is nothing mentioned about using accesskeys for tabbed browsing. After all, accesskey is a pretty old attribut of html, so I'm not sure that, if Firefox uses it for handling the browser, this is more a bug then a feature. So as a conclusion the facts seem to be: Firefox on Linux + tabbed Browsing + Accesskeys = no fun for the user! But not a "nono" in General. And at least it doesn't produce an error, just looses a little feature. Accesskeys do also not work in some other Browsers. Seems that Opera uses ctrl+esc but at least with mine it doesn't work... I agree on what a german author (Jan Eric Hellbusch) says on his page: "Presuppose, that users needing the functionality of direct access will use a browser that offers this feature." Thanks for your valuable information. Michael From michael.haugg at memmingen.de Fri Nov 4 09:35:16 2005 From: michael.haugg at memmingen.de (Michael Haugg) Date: Fri, 04 Nov 2005 09:35:16 +0100 Subject: [TYPO3-content-rendering] Integrating Accesskeypad - Hello... In-Reply-To: References:

Message-ID: Might be interesting: http://www.mozilla.org/support/firefox/keyboard From michael.haugg at memmingen.de Fri Nov 4 11:41:56 2005 From: michael.haugg at memmingen.de (Michael Haugg) Date: Fri, 04 Nov 2005 11:41:56 +0100 Subject: [TYPO3-content-rendering] Integrating Accesskeypad - Hello... In-Reply-To: References:

Message-ID: >>> 2. The page contains a lot of external links which are not marked at >>> all - very annoying. >> >> >> You see it when you switch to nocss. They are marked this way: > > > Thats a good piece of TS. I would be usefull to mark the external links > as well - there are still some users out there who dont examine the code > (how stupid) ;-) May I refer to my former thread: Title-Attribute for page type "external url" My intention is exacly what you suggest, the problem is I just don't know how to do it :-( I use dh_linklayout for external Links within the content. But I haven't found any solution to add a title attribute to the pagetype "external url"! What do you think about this - you inspiretad me ;-) var_exturl_img = /typo3conf/ext/dh_linklayout/res/link_ext.gif var_exturl_alt = Symbol f?r externen Link var_exturl_title = 'Externer Link, ?ffnet sich in neuem Browserfenster' temp.exturlspecialwrap { stdWrap.cObject = CASE stdWrap.cObject { key.field = doktype default = TEXT default { field = title } 3 = TEXT 3 { field = title wrap = ${$var_exturl_alt}$ | } } } BUT: Nevertheless I still would be more than happy to know how to add a title tag to this kind of pages in the menu! Or at least to learn that it's not possible...but this would the first time that something isn't possible in Typo3 :-) But lets switsch for this to my former thread! Michael From michael.haugg at memmingen.de Fri Nov 4 11:42:55 2005 From: michael.haugg at memmingen.de (Michael Haugg) Date: Fri, 04 Nov 2005 11:42:55 +0100 Subject: [TYPO3-content-rendering] Title-Attribute for page type "external url" In-Reply-To: References: Message-ID: Not the solution, but probably better then before: var_exturl_img = /typo3conf/ext/dh_linklayout/res/link_ext.gif var_exturl_alt = Symbol f?r externen Link var_exturl_title = 'Externer Link, ?ffnet sich in neuem Browserfenster' temp.exturlspecialwrap { stdWrap.cObject = CASE stdWrap.cObject { key.field = doktype default = TEXT default { field = title } 3 = TEXT 3 { field = title wrap = ${$var_exturl_alt}$ | } } } BUT: Nevertheless I still would be more than happy to know how to add a title tag to this kind of pages in the menu! Or at least to learn that it's not possible... but this would the first time that something isn't possible in Typo3 :-) Michael From sebastian at garbage-group.de Sun Nov 6 10:47:55 2005 From: sebastian at garbage-group.de (Sebastian Kurfuerst) Date: Sun, 06 Nov 2005 10:47:55 +0100 Subject: [TYPO3-content-rendering] Content rendering issues for TYPO3 4.0 In-Reply-To: References: Message-ID: Hi, is it possible for you to provide patches for these unassigned bugs? If yes, this would make the process a lot easier and faster, I will care then for getting them into CVS. Did you already check the patches which are in the bugtracker for the issues if they really solve the problem? That's another step which would speed up everything, as I can concentrate on coding style, compatibility then. Greets from Dresden, Sebastian PS: a question concerning bug 1243 - is it really needed to make it configurable or would it be OK to do it as stucki proposed? PPS: Sorry for not answering to this posting for such a long time... From typo3 at ingo-renner.com Sun Nov 6 11:27:06 2005 From: typo3 at ingo-renner.com (Ingo Renner) Date: Sun, 6 Nov 2005 11:27:06 +0100 Subject: [TYPO3-content-rendering] Content rendering issues for TYPO3 4.0 References:

Message-ID: Am Sun, 06 Nov 2005 10:47:55 +0100 schrieb Sebastian Kurfuerst: Hi Sebastian, > PS: a question concerning bug 1243 - is it really needed to make it > configurable or would it be OK to do it as stucki proposed? I think it's ok to just put an "a" or "content" in front of it, no configuration needed... Ingo -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From sebastian at garbage-group.de Sun Nov 6 11:39:04 2005 From: sebastian at garbage-group.de (Sebastian Kurfuerst) Date: Sun, 06 Nov 2005 11:39:04 +0100 Subject: [TYPO3-content-rendering] Content rendering issues for TYPO3 4.0 In-Reply-To: References:

Message-ID: Hi, ok... So we just change it everywhere and that's it. If nobody provides a patch, I'll do it later. Greets, Sebastian Am Sonntag, den 06.11.2005, 11:27 +0100 schrieb Ingo Renner: > Am Sun, 06 Nov 2005 10:47:55 +0100 schrieb Sebastian Kurfuerst: > > Hi Sebastian, > > > PS: a question concerning bug 1243 - is it really needed to make it > > configurable or would it be OK to do it as stucki proposed? > > I think it's ok to just put an "a" or "content" in front of it, no > configuration needed... > > Ingo > From ernst at cron-it.de Mon Nov 7 13:35:55 2005 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Mon, 07 Nov 2005 13:35:55 +0100 Subject: [TYPO3-content-rendering] Content rendering issues for TYPO3 4.0 In-Reply-To: References:

Message-ID: Sebastian Kurfuerst schrieb am 06.11.2005 10:47: > is it possible for you to provide patches for these unassigned bugs? If > yes, this would make the process a lot easier and faster, I will care > then for getting them into CVS. > > Did you already check the patches which are in the bugtracker for the > issues if they really solve the problem? That's another step which would > speed up everything, as I can concentrate on coding style, compatibility > then. Other than my patches I have none. I am not sure if I will have the time to provide more patches. What exactly is the 4.0 deadline for patches to be included? > PS: a question concerning bug 1243 - is it really needed to make it > configurable or would it be OK to do it as stucki proposed? I would say you have to make it configurable (at least as a boolean!), because it might break existing "hard-coded" links that point to the specific sections. E.g someone published a link in a magazine: http:///path/blabla/#232 this should still work if one upgrades to 4.0, thus it should be optional to prefix the local anchors with another string. This prefix should be added on typoLink(), regardless of the stdWrap, as far as I can see, this way no change to TypoScript is needed (e.g. tt_content.menu.20.3.renderObj.typolink.section and other places). Cheers, Ernesto From michael at typo3.org Mon Nov 7 19:19:43 2005 From: michael at typo3.org (Michael Stucki) Date: Mon, 07 Nov 2005 19:19:43 +0100 Subject: [TYPO3-content-rendering] Content rendering issues for TYPO3 4.0 References:

Message-ID: Hi Ernesto, > Other than my patches I have none. I am not sure if I will have the time > to provide more patches. What exactly is the 4.0 deadline for patches to > be included? Beginning of December. > I would say you have to make it configurable (at least as a boolean!), > because it might break existing "hard-coded" links that point to the > specific sections. E.g someone published a link in a magazine: > > http:///path/blabla/#232 > > this should still work if one upgrades to 4.0, thus it should be > optional to prefix the local anchors with another string. No! The link does still work, the user will arrive at the right page, even not at the right section. No I don't think it is needed to add a new property for this. There are enough already, don't you think? Regards, michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From typo3 at ingo-renner.com Mon Nov 7 20:34:52 2005 From: typo3 at ingo-renner.com (Ingo Renner) Date: Mon, 7 Nov 2005 20:34:52 +0100 Subject: [TYPO3-content-rendering] Content rendering issues for TYPO3 4.0 References:

Message-ID: Am Mon, 07 Nov 2005 19:19:43 +0100 schrieb Michael Stucki: Hi, > No! The link does still work, the user will arrive at the right page, even > not at the right section. No I don't think it is needed to add a new > property for this. There are enough already, don't you think? I fully agree with you Michael Ingo -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From ernst at cron-it.de Tue Nov 8 10:13:03 2005 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Tue, 08 Nov 2005 10:13:03 +0100 Subject: [TYPO3-content-rendering] Content rendering issues for TYPO3 4.0 In-Reply-To: References:

Message-ID: Michael Stucki schrieb am 07.11.2005 19:19: >>I would say you have to make it configurable (at least as a boolean!), >>because it might break existing "hard-coded" links that point to the >>specific sections. E.g someone published a link in a magazine: >> >> http:///path/blabla/#232 >> >>this should still work if one upgrades to 4.0, thus it should be >>optional to prefix the local anchors with another string. > No! The link does still work, the user will arrive at the right page, even > not at the right section. Sometimes things like that *are* important (to reach the right section). If this wasn't the case, we wouldn't need anchors and could just get rid of them. > No I don't think it is needed to add a new > property for this. There are enough already, don't you think? I still think this breaks backwards compatibility, but ok. At least we'll be XHMTL-compliant on new sites. Cheers, Ernesto From michael at typo3.org Tue Nov 8 20:48:55 2005 From: michael at typo3.org (Michael Stucki) Date: Tue, 08 Nov 2005 20:48:55 +0100 Subject: [TYPO3-content-rendering] Proposed fix for image alignment and Firefox/Mozilla References: Message-ID: There was no feedback on this! Please test the attached patch _now_ and give feedback ASAP, otherwise I will not be able to add this fix to 3.8.1. Please notice the attached patch. (Martin, I've slightly changed your patch to make sure that $table_align does not contain an empty value if $align was not set.) - michael Martin Kutschker wrote: > Hi! > > I guess that few on this list use the default css_styled_content > implementation of image ot text w/image, but anyway here comes a fix > for it. > > The problem is that the image alignment above or below text is broken in > Firefox/Mozilla. The reason is that > >

...

> > won't work. To make it work you have to set margins on the table > > ...

> > For centering you need to set both margins to auto, for left alignment > the left margin is 0 and the right auto. > > Fortunatley you can mix both settings. So I have come up with a solution > that works for me in IE 6 and Firefox. > > function IMGTEXT($conf) { > ... > > if ($c) { > // Table-tag is inserted > > // OLD CODE > // $i=$contentPosition; > // $table_align = (($i==16) ? 'align="'.$align.'"' : ''); > > switch ($contentPosition) { > case '0': // above > case '8': // below > // these settings are needed for Firefox > switch ($align) { > case 'left': > $table_align = 'margin-left: 0px; margin-right: auto'; > break; > > case 'center': > $table_align = 'margin-left: auto; margin-right: auto'; > break; > > case 'right': > $table_align = 'margin-left: auto; margin-right: 0px'; > } > $table_align = 'style="'.$table_align.'"'; > break; > > case '16': // in text > $table_align = 'align="'.$align.'"'; > break; > > default: > $table_align = ''; > } > ... > } > > I'm not sure if it's needed to set the margins to 0px (if not auto). The > default values may be enough. And without it yo still can set the a > (default) margin with CSS. > > What do you think of that solution? > > Masi -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ -------------- next part -------------- A non-text attachment was scrubbed... Name: image_align_fix.diff Type: text/x-diff Size: 1571 bytes Desc: not available Url : http://lists.netfielders.de/pipermail/typo3-project-content-rendering/attachments/20051108/38bfcaae/attachment.bin From ben at netcreators.nl Tue Nov 8 23:07:41 2005 From: ben at netcreators.nl (ben van 't ende [netcreators]) Date: Tue, 08 Nov 2005 23:07:41 +0100 Subject: [TYPO3-content-rendering] Content rendering issues for TYPO3 4.0 In-Reply-To: References:

Message-ID: Ernesto Baschny [cron IT] wrote: > Michael Stucki schrieb am 07.11.2005 19:19: > > >>>I would say you have to make it configurable (at least as a boolean!), >>>because it might break existing "hard-coded" links that point to the >>>specific sections. E.g someone published a link in a magazine: >>> >>>http:///path/blabla/#232 >>> >>>this should still work if one upgrades to 4.0, thus it should be >>>optional to prefix the local anchors with another string. > > >>No! The link does still work, the user will arrive at the right page, even >>not at the right section. > > > Sometimes things like that *are* important (to reach the right section). > If this wasn't the case, we wouldn't need anchors and could just get rid > of them. > > >>No I don't think it is needed to add a new >>property for this. There are enough already, don't you think? > > > I still think this breaks backwards compatibility, but ok. At least > we'll be XHMTL-compliant on new sites. +1 gRTz ben -- netcreators::creation and innovation www.netcreators.nl - www.typo3.nl From typo3 at laborenz.de Thu Nov 10 08:10:41 2005 From: typo3 at laborenz.de (Kai Laborenz) Date: Thu, 10 Nov 2005 08:10:41 +0100 Subject: [TYPO3-content-rendering] Proposed fix for image alignment and Firefox/Mozilla In-Reply-To: References:

Message-ID: Michael Stucki schrieb: > There was no feedback on this! Please test the attached patch _now_ and give > feedback ASAP, otherwise I will not be able to add this fix to 3.8.1. As far as I know you stil have to include "text-align:.." for older IEs. Greetings, Kai From ernst at cron-it.de Thu Nov 10 17:10:54 2005 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Thu, 10 Nov 2005 17:10:54 +0100 Subject: [TYPO3-content-rendering] Ampersants in URLs, XHTML-compliancy Message-ID: Hi people, one of the content bugs we are trying to solve for XHTML-compliancy is: http://bugs.typo3.org/view.php?id=772 But I don't see the problem yet (see my last comment). Can someone please tell me if I miss something? For me, TYPO3 is already generating all links correctly (with "&" encoded as "& amp;"), this has been this way at least since 3.7. qcom_htmlcleaner also does some "cleanup" on itself, and I don't see the reason for it. But maybe I am just not seeing the obvious. :) So if someone can provide me a setup where TYPO3 (core!) generates an A-Tag where the "HREF" attribute contains "&" that are not translated to "&", please tell me exacly how he got it. Cheers, Ernesto From ernst at cron-it.de Thu Nov 10 19:05:52 2005 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Thu, 10 Nov 2005 19:05:52 +0100 Subject: [TYPO3-content-rendering] Indexed Search templating In-Reply-To: References:

Message-ID: Michael Stucki schrieb am 15.09.2005 10:55: >>>...that Stucki is working on the template-able indexed search... >> >>huh... >>reinventing the wheel? ;) >>maybe someone should tell Michael that this already exists...I think >>looking at the code would be quicker than writing a new one... > > > No I won't reinvent it. Actually I didn't do that by myself but got a pretty > patch from Udo von Eynern who did this even before this extension was out. > > I think the patch by Udo is very good and thus I won't compare it with the > extension code. > > I'm going to submit the patch for proof-reading later this week. I see that the templating was added to indexed_search in CVS, which is pretty cool! What I miss, thou, is a XHTML-compliant template. The template_css.tmpl is a great start, but it just isn't XHTML-compliant. If we want TYPO3 4.0 to be XHTML-compliant, we should provide a XHTML-based indexed_search template, right? :) So I did that, and reported in http://bugs.typo3.org/view.php?id=1830. Michael, could you take a look at it and integrate, so that it can get included for TYPO3 4.0? Cheers, Ernesto From info at unlimited-vision.net Thu Nov 10 19:31:27 2005 From: info at unlimited-vision.net (Sacha Vorbeck) Date: Thu, 10 Nov 2005 19:31:27 +0100 Subject: [TYPO3-content-rendering] accessible popup-image In-Reply-To: References:

Message-ID: Hi, > [globalVar = JSenabled = 1] > [else] > tt_content.image.20.1.imageLinkWrap.JSwindow = 0 > tt_content.image.20.1.imageLinkWrap.wrap > > [global] > > Not tested but should be working interesting, thanks for the suggestion. Recently I had to show some copyright information inside of the zoom-pop-up (not inside the image itself) and found it a bit difficult to realize. The resulting source-code of the showpic-popup looks like this:

copyright; Info

I think it would be nice if imageLinkWrap.wrap would have stdWrap properties. Then you could create a special page type (typenum=x) for the popup-windows and more easily realize things like custom doctype, stylesheets and additional information inside of the popup. Any other ideas? Shall I add it to the bugtracker? -- Ciao, Sacha From martin.kutschker-n0spam at no5pam-blackbox.net Thu Nov 10 23:28:39 2005 From: martin.kutschker-n0spam at no5pam-blackbox.net (Martin Kutschker) Date: Thu, 10 Nov 2005 23:28:39 +0100 Subject: [TYPO3-content-rendering] Ampersants in URLs, XHTML-compliancy In-Reply-To: References: Message-ID: Ernesto Baschny [cron IT] schrieb: > Hi people, > > one of the content bugs we are trying to solve for XHTML-compliancy is: > > http://bugs.typo3.org/view.php?id=772 > > But I don't see the problem yet (see my last comment). Can someone > please tell me if I miss something? For me, TYPO3 is already generating > all links correctly (with "&" encoded as "& amp;"), this has been this > way at least since 3.7. I read your comments, and they are interesting. But in real life this isn't what happen. TYPO3 site break xhmtl validity because links use & and not &. Definitely not in 3.7. But maybe we're not talking about typolinks but links in menus etc. In 3.7 I ended up calling stdWrap.hsc for menus to be xhtml compliant. * If your comment tells me anythign than that we have to revalidate the patch. I doubt that your conclusion, that everything is fine already, is correct. Masi * I'm sure I did much more. Perhaps too much like your comment suggests, but there are places where it's needed. From erik at linnearad.no Fri Nov 11 01:53:22 2005 From: erik at linnearad.no (Erik Svendsen) Date: Fri, 11 Nov 2005 00:53:22 +0000 (UTC) Subject: [TYPO3-content-rendering] accessible sites References: Message-ID: Hello ben van 't ende [netcreators], > Hi Guys, > > We have the CRG list, but no real examples of sites that are > accessible and comply to different standards. Today I received a > question from an Italian student that wants to use TYPO3 for his > university website, but was a little amazed by the fact that TYPO3.org > is HTML 4.0 only and does not validate at all. > > I'd like to get a list together of accessible websites or websites > that comply to XHTML1.0 strict made with TYPO3. I know greenpeace.de > is one of them. Please let me know the sites you have built and what > (extensions) you used to get it accessible/xhtml compliant. We > definitely need some examples as showcases. > > tHNx > > ben > http://www.linnearad.no/ CSS Styled ImgText (cron...), AcronymManager, Enhanced HTML Cleaner, gov_textmenu. Also made new templates for most of the extensions. Templating with TV. Okay - it break XHTML 1.0 Strict some places and I haven't finished the full clean up. Frontpage and about half the other pages are also WCAG AAA compliant. Even if this is a smaller site, it shows that even persons without webdevelopment as their main trade can make TYPO3 XHTML. WBR, Erik Svendsen www.linnearad.no From info at cybercraft.de Fri Nov 11 02:31:36 2005 From: info at cybercraft.de (JoH) Date: Fri, 11 Nov 2005 02:31:36 +0100 Subject: [TYPO3-content-rendering] accessible popup-image References:

Message-ID: > I think it would be nice if imageLinkWrap.wrap would have stdWrap > properties. Then you could create a special page type (typenum=x) for > the popup-windows and more easily realize things like custom doctype, > stylesheets and additional information inside of the popup. > > Any other ideas? Shall I add it to the bugtracker? 1.Yes 2. No - simply use this one: JSwindow.altUrl string/stdWrap If this returns anything, the URL shown in the JS-window is NOT showpic.php but the url given here! JSwindow.altUrl.cObject = TEXT JSwindow.altUrl.cObject { field = images current = 1 dataWrap = index.php?id={TSFE:id}&type=123&imageFileName=| } Now you can setup another pagetype 123 that can handle the imageFileName. Not tested but should be working. Joey -- Wenn man keine Ahnung hat: Einfach mal Fresse halten! (If you have no clues: simply shut your knob sometimes!) Dieter Nuhr, German comedian openBC: http://www.openbc.com/go/invuid/Jo_Hasenau From michael at typo3.org Fri Nov 11 08:40:51 2005 From: michael at typo3.org (Michael Stucki) Date: Fri, 11 Nov 2005 08:40:51 +0100 Subject: [TYPO3-content-rendering] Ampersants in URLs, XHTML-compliancy References: Message-ID: Hi Ernesto, > one of the content bugs we are trying to solve for XHTML-compliancy is: > > http://bugs.typo3.org/view.php?id=772 > > But I don't see the problem yet (see my last comment). Can someone > please tell me if I miss something? For me, TYPO3 is already generating > all links correctly (with "&" encoded as "& amp;"), this has been this > way at least since 3.7. > > qcom_htmlcleaner also does some "cleanup" on itself, and I don't see the > reason for it. But maybe I am just not seeing the obvious. :) > > So if someone can provide me a setup where TYPO3 (core!) generates an > A-Tag where the "HREF" attribute contains "&" that are not translated to > "&", please tell me exacly how he got it. I didn't check but don't think that this has been solved yet. But could it be that you check the source code with Firefox? As far as I remember, it does automatically fix this when printing the HTML code. Stupid guess? Don't know... - michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From michael at typo3.org Fri Nov 11 08:57:55 2005 From: michael at typo3.org (Michael Stucki) Date: Fri, 11 Nov 2005 08:57:55 +0100 Subject: [TYPO3-content-rendering] Indexed Search templating References:

Message-ID: Hi Ernesto, > What I miss, thou, is a XHTML-compliant template. The template_css.tmpl > is a great start, but it just isn't XHTML-compliant. If we want TYPO3 > 4.0 to be XHTML-compliant, we should provide a XHTML-based > indexed_search template, right? :) > > So I did that, and reported in http://bugs.typo3.org/view.php?id=1830. > > Michael, could you take a look at it and integrate, so that it can get > included for TYPO3 4.0? Yes I will. Your patch looks great and chances are good to change this _now_ because the CSS based template is not in productive use so far. So we can still fix this without caring about the holy backwards compatibility ;-) - michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From ernst at cron-it.de Fri Nov 11 10:08:12 2005 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Fri, 11 Nov 2005 10:08:12 +0100 Subject: [TYPO3-content-rendering] Ampersants in URLs, XHTML-compliancy In-Reply-To: References:

Message-ID: Martin Kutschker schrieb am 10.11.2005 23:28: >> one of the content bugs we are trying to solve for XHTML-compliancy is: >> >> http://bugs.typo3.org/view.php?id=772 >> >> But I don't see the problem yet (see my last comment). Can someone >> please tell me if I miss something? For me, TYPO3 is already generating >> all links correctly (with "&" encoded as "& amp;"), this has been this >> way at least since 3.7. > I read your comments, and they are interesting. But in real life this > isn't what happen. TYPO3 site break xhmtl validity because links use & > and not &. Definitely not in 3.7. But maybe we're not talking about > typolinks but links in menus etc. In 3.7 I ended up calling stdWrap.hsc > for menus to be xhtml compliant. * I have never called hsc for menu links (just for the content itself, so that the "&" in the title gets "&" in the output) and have always gotten compliant output on that part. So maybe you could provide a working example where this is the case (in 3.8)? > If your comment tells me anythign than that we have to revalidate the > patch. I doubt that your conclusion, that everything is fine already, is > correct. Surely not everything is fine, but all situations that are being handled by the patch (which includes MENUs and much more, not just typolinks!) were fine already. That's what my "challenge" here to the group was about: to give me a concrete situation where we end up generating a link without "&" in the core! I know that many extentions do that, but that's not the issue here. And also if one creates the A-Tag in the TypoScript "manually", he should be using &. Doing a quick search for "href=" in the source of the core shows me that almost every one go through htmlspecialchars, so at first I fail to see where this could happen. Cheers, Ernesto From ernst at cron-it.de Fri Nov 11 10:14:11 2005 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Fri, 11 Nov 2005 10:14:11 +0100 Subject: [TYPO3-content-rendering] Ampersants in URLs, XHTML-compliancy In-Reply-To: References:

Message-ID: Michael Stucki schrieb am 11.11.2005 08:40: >>one of the content bugs we are trying to solve for XHTML-compliancy is: >> >>http://bugs.typo3.org/view.php?id=772 >> >>But I don't see the problem yet (see my last comment). Can someone >>please tell me if I miss something? For me, TYPO3 is already generating >>all links correctly (with "&" encoded as "& amp;"), this has been this >>way at least since 3.7. > I didn't check but don't think that this has been solved yet. But could it > be that you check the source code with Firefox? As far as I remember, it > does automatically fix this when printing the HTML code. > > Stupid guess? Don't know... Hehe, could be, but no. I have checked it with IE, source-code being viewed in Notepad. Do you have a working setup where some links that come from the core are not handled correctly? Cheers, Ernesto From info at unlimited-vision.net Fri Nov 11 10:24:41 2005 From: info at unlimited-vision.net (Sacha Vorbeck) Date: Fri, 11 Nov 2005 10:24:41 +0100 Subject: [TYPO3-content-rendering] accessible popup-image In-Reply-To: References:

Message-ID: Hi, > JSwindow.altUrl.cObject = TEXT > JSwindow.altUrl.cObject { > field = images > current = 1 > dataWrap = index.php?id={TSFE:id}&type=123&imageFileName=| > } > > Now you can setup another pagetype 123 that can handle the imageFileName. > Not tested but should be working. grandmaster TS strikes again. Brilliant, thank you. -- Ciao, Sacha From erik at linnearad.no Fri Nov 11 13:54:46 2005 From: erik at linnearad.no (Erik Svendsen) Date: Fri, 11 Nov 2005 12:54:46 +0000 (UTC) Subject: [TYPO3-content-rendering] A statement References: Message-ID: Hello Another +1 I think the new typo3.org and typo3.com and TYPO3 4.0 should beat this. Make it happen. I know it's possible - why not say we have done it. OT! I manage to get my own site WCAG 1.0 Priority 3 for frontpage and about 40 % of the site last night. But not completly XHTML 1.0 Strict. It is possible even with 3.8.0. But not with all extensions. WBR, Erik Svendsen www.linnearad.no > +1 > From erik at linnearad.no Fri Nov 11 14:17:38 2005 From: erik at linnearad.no (Erik Svendsen) Date: Fri, 11 Nov 2005 13:17:38 +0000 (UTC) Subject: [TYPO3-content-rendering] Extension templates - XHTML and WCAG 1.0. Idea for example code in wiki. Message-ID: I have worked some time getting my own companys website up to date with XHTML 1.0 Strict and WCAG 1.0 Priority 3. (Also other sites). I'm not finished yet, but I'm going to make it. But a lot of recoding of HTML in extension templates has been necessary. And I think I'm not the only one. Could there be an idea to make a section in the wiki about how to get TYPO3 XHTML 1.0 Strict, with example code for different extensions. And other helpful "trick". WBR, Erik Svendsen www.linnearad.no From michael at typo3.org Fri Nov 11 18:05:19 2005 From: michael at typo3.org (Michael Stucki) Date: Fri, 11 Nov 2005 18:05:19 +0100 Subject: [TYPO3-content-rendering] Proposed fix for image alignment and Firefox/Mozilla References:

Message-ID: Kai Laborenz wrote: > Michael Stucki schrieb: >> There was no feedback on this! Please test the attached patch _now_ and >> give feedback ASAP, otherwise I will not be able to add this fix to >> 3.8.1. > > As far as I know you stil have to include "text-align:.." for older IEs. Can anybody confirm this, please? Martin...? - michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From cf at cf-webservice.de Fri Nov 11 22:12:04 2005 From: cf at cf-webservice.de (Carla Froitzheim) Date: Fri, 11 Nov 2005 22:12:04 +0100 Subject: [TYPO3-content-rendering] Proposed fix for image alignment and Firefox/Mozilla In-Reply-To: References:

Message-ID: Michael Stucki wrote: >Kai Laborenz wrote: > > > >>Michael Stucki schrieb: >> >> >>>There was no feedback on this! Please test the attached patch _now_ and >>>give feedback ASAP, otherwise I will not be able to add this fix to >>>3.8.1. >>> >>> >>As far as I know you stil have to include "text-align:.." for older IEs. >> >> > >Can anybody confirm this, please? Martin...? > > I am not Martin but margin: auto doesn?t even work in IE 6 to center something. So for IE you still need text-align: ... and for Firefox the margin: ... works. I didn?t install the patch but this is the way I center the images by external css for the FF when using the default css_styled_content implementation. Does this help? Carla From martin.kutschker-n0spam at no5pam-blackbox.net Sat Nov 12 11:58:47 2005 From: martin.kutschker-n0spam at no5pam-blackbox.net (Martin Kutschker) Date: Sat, 12 Nov 2005 11:58:47 +0100 Subject: [TYPO3-content-rendering] Proposed fix for image alignment and Firefox/Mozilla In-Reply-To: References:

Message-ID: Michael Stucki schrieb: > Kai Laborenz wrote: > > >>Michael Stucki schrieb: >> >>>There was no feedback on this! Please test the attached patch _now_ and >>>give feedback ASAP, otherwise I will not be able to add this fix to >>>3.8.1. >> >>As far as I know you stil have to include "text-align:.." for older IEs. Yes, but the patch doesn't remove this. TYPO3 sets text-align in a DIV surrounding the TABLE. My patch only adds the margin settings to the table itself. I'll try and add the code to a public site (this evening), so everybody can test it with all the browers available. Masi From michael at typo3.org Sat Nov 12 12:13:04 2005 From: michael at typo3.org (Michael Stucki) Date: Sat, 12 Nov 2005 12:13:04 +0100 Subject: [TYPO3-content-rendering] Proposed fix for image alignment and Firefox/Mozilla References:

Message-ID: Hi Carla, > I am not Martin but margin: auto doesn?t even work in IE 6 to center > something. So for IE you still need text-align: ... and for Firefox the > margin: ... works. I didn?t install the patch but this is the way I > center the images by external css for the FF when using the default > css_styled_content implementation. So what are you doing if you want the images aligned correctly? Do you need to change any code for this? > Does this help? Not if I still need to test it by myself :-( - michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From cf at cf-webservice.de Sat Nov 12 13:58:35 2005 From: cf at cf-webservice.de (Carla Froitzheim) Date: Sat, 12 Nov 2005 13:58:35 +0100 Subject: [TYPO3-content-rendering] Proposed fix for image alignment and Firefox/Mozilla In-Reply-To: References:

Message-ID: Michael Stucki wrote: >Hi Carla, > > > >>I am not Martin but margin: auto doesn?t even work in IE 6 to center >>something. So for IE you still need text-align: ... and for Firefox the >>margin: ... works. I didn?t install the patch but this is the way I >>center the images by external css for the FF when using the default >>css_styled_content implementation. >> >> > >So what are you doing if you want the images aligned correctly? Do you need >to change any code for this? > > No code changes necessary, the text-align: .... aligns it in IE and the imgtext-table class gets margin: .... for correct alignment in FF. Carla From martin.kutschker-n0spam at no5pam-blackbox.net Sat Nov 12 18:39:54 2005 From: martin.kutschker-n0spam at no5pam-blackbox.net (Martin Kutschker) Date: Sat, 12 Nov 2005 18:39:54 +0100 Subject: [TYPO3-content-rendering] Proposed fix for image alignment and Firefox/Mozilla In-Reply-To: References:

Message-ID: Carla Froitzheim schrieb: > Michael Stucki wrote: > >> Hi Carla, >> >> >> >>> I am not Martin but margin: auto doesn?t even work in IE 6 to center >>> something. So for IE you still need text-align: ... and for Firefox the >>> margin: ... works. I didn?t install the patch but this is the way I >>> center the images by external css for the FF when using the default >>> css_styled_content implementation. >> >> So what are you doing if you want the images aligned correctly? Do you >> need >> to change any code for this? >> > No code changes necessary, the text-align: .... aligns it in IE and the > imgtext-table class gets margin: .... for correct alignment in FF. Right. The origanl code takes care of IE, my patch of FF. Masi From martin.kutschker-n0spam at no5pam-blackbox.net Sat Nov 12 19:04:19 2005 From: martin.kutschker-n0spam at no5pam-blackbox.net (Martin Kutschker) Date: Sat, 12 Nov 2005 19:04:19 +0100 Subject: [TYPO3-content-rendering] Indexed Search templating In-Reply-To: References:

Message-ID: Michael Stucki schrieb: > Hi Ernesto, > > >>What I miss, thou, is a XHTML-compliant template. The template_css.tmpl >>is a great start, but it just isn't XHTML-compliant. If we want TYPO3 >>4.0 to be XHTML-compliant, we should provide a XHTML-based >>indexed_search template, right? :) >> >>So I did that, and reported in http://bugs.typo3.org/view.php?id=1830. >> >>Michael, could you take a look at it and integrate, so that it can get >>included for TYPO3 4.0? > > Yes I will. Your patch looks great and chances are good to change this _now_ > because the CSS based template is not in productive use so far. So we can > still fix this without caring about the holy backwards compatibility ;-) Don't forget that the section header needs two separate classes (or three if you implement one base class: one for the section name and another one for the page count. And can the colon at the end of the section head be moved from the PHP code to the template? Not every language uses colons (and some screen designers don't like them). Masi From stanislas.rolland at fructifor.ca Thu Nov 17 23:18:02 2005 From: stanislas.rolland at fructifor.ca (Stanislas Rolland) Date: Thu, 17 Nov 2005 17:18:02 -0500 Subject: [TYPO3-content-rendering] title attribute and typolink In-Reply-To: References: Message-ID: > > So please vote for the gremlin here: > > http://typo3.org/development/projects/zap-the-gremlins/gremlin-overview/?tx_gremlincollector_pi1%5BshowUid%5D=1660&cHash=babf44d58a > Your vote was listened to. I tested this week a patch that Jan-Erik sent me for Gremlin 1660. The patch enables title attribute on typolinks and works fine with htmlArea RTE. This is going into CVS and I assume it will be included in TYPO3 4.0 Thanks to Jan-Erik! Stanislas From laborenz at css-praxis.de Tue Nov 29 17:21:10 2005 From: laborenz at css-praxis.de (Kai Laborenz) Date: Tue, 29 Nov 2005 17:21:10 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE Message-ID: Hi folks, maybe I missed it. The COA IMAGE assigns the alt value also to the title attribute - this is not good practice. Is there a way around it? Greetings, Kai From Martin.Kutschker at n0spam-blackbox.net Tue Nov 29 17:29:30 2005 From: Martin.Kutschker at n0spam-blackbox.net (Martin Kutschker) Date: Tue, 29 Nov 2005 17:29:30 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE In-Reply-To: References: Message-ID: Kai Laborenz schrieb: > Hi folks, > > maybe I missed it. The COA IMAGE assigns the alt value also to the title > attribute - this is not good practice. Well, it's the x-browser way to get those tooltips. Masi From laborenz at css-praxis.de Tue Nov 29 17:55:00 2005 From: laborenz at css-praxis.de (Kai Laborenz) Date: Tue, 29 Nov 2005 17:55:00 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE In-Reply-To: References:

Message-ID: Martin Kutschker schrieb: >> maybe I missed it. The COA IMAGE assigns the alt value also to the >> title attribute - this is not good practice. > > Well, it's the x-browser way to get those tooltips. I dont think so. The x-browser way to get tooltips is supplying a title text. Alt text is for replacing an image, not for additional information. It is very anoying for a blind person to get all the text read twice. And it is semantically incorrect as well. It would be the right behavior if there is no title text there should be no title at all or (that is the x-browser way of having no tooltips) an empty title attribute. Greetings, Kai From Martin.Kutschker at n0spam-blackbox.net Tue Nov 29 18:12:47 2005 From: Martin.Kutschker at n0spam-blackbox.net (Martin Kutschker) Date: Tue, 29 Nov 2005 18:12:47 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE In-Reply-To: References:

Message-ID: Kai Laborenz schrieb: > Martin Kutschker schrieb: > >>> maybe I missed it. The COA IMAGE assigns the alt value also to the >>> title attribute - this is not good practice. >> >> Well, it's the x-browser way to get those tooltips. > > I dont think so. The x-browser way to get tooltips is supplying a title > text. Alt text is for replacing an image, not for additional information. I know. But there used to be a difference between IE/Netscape/Mozilla. I recall that older IEs ignored the title attribute and that Mozilla used (IMHO correctly) only title as tooltip. So the usual workaround was to abuse alt for title and setting both. Which is of course dull. I'd remove this auto-title thingy completely, but if folks like it, it should be able to turn ot off by eg setting title to - (hyphen). This would be consistent with the placeholders in RTE typolinks. Masi From laborenz at css-praxis.de Tue Nov 29 18:16:24 2005 From: laborenz at css-praxis.de (Kai Laborenz) Date: Tue, 29 Nov 2005 18:16:24 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE In-Reply-To: References:

Message-ID: Martin Kutschker schrieb: > I know. But there used to be a difference between IE/Netscape/Mozilla. I > recall that older IEs ignored the title attribute and that Mozilla used > (IMHO correctly) only title as tooltip. As far as I know the Mozilla way is the correct one. > I'd remove this auto-title thingy completely, but if folks like it, it > should be able to turn ot off by eg setting title to - (hyphen). This > would be consistent with the placeholders in RTE typolinks. This would be fine. Or just include a typoscript constant like accessibility=1 or alt2titledullmode=0 to change to modern way. Regards, Kai From elmar.DOT.hinz at team.MINUS.red.DOT.net Tue Nov 29 18:48:06 2005 From: elmar.DOT.hinz at team.MINUS.red.DOT.net (Elmar Hinz) Date: Tue, 29 Nov 2005 18:48:06 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE In-Reply-To: References:

Message-ID: > > > This would be fine. Or just include a typoscript constant like > accessibility=1 or alt2titledullmode=0 to change to modern way. > > Regards, Kai Hi Kai, you, or somebody else, could feed this as a request into the bug tracking tool. So it won't get lost, even if implementation takes time. Unfortunatly it comes to late for the gremlins hunt. You may also provide a patch for it. http://bugs.typo3.org Regards Elmar -- Climate change 2005: Mexico, Guatemala, New Orleans, Sahel, Bangladesh, Spain, Portugal, Austria, Swiss, France, ... Production of CO2 is killing people. Production of CO2 just for fun is killing people just for fun. From info at meinsystem.de Tue Nov 29 19:14:18 2005 From: info at meinsystem.de (Andreas Schwarzkopf) Date: Tue, 29 Nov 2005 19:14:18 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE In-Reply-To: References: Message-ID: Hi Kai, AFAIK Ernesto has implemented a configuration to the imgtxt-Extension. May be it goes to the core - I heared somthing about.. grtx Andreas Kai Laborenz schrieb: > Hi folks, > > maybe I missed it. The COA IMAGE assigns the alt value also to the title > attribute - this is not good practice. > > Is there a way around it? > > Greetings, Kai > From michael at typo3.org Tue Nov 29 21:05:00 2005 From: michael at typo3.org (Michael Stucki) Date: Tue, 29 Nov 2005 21:05:00 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE References:

Message-ID: Elmar Hinz wrote: >> This would be fine. Or just include a typoscript constant like >> accessibility=1 or alt2titledullmode=0 to change to modern way. > > you, or somebody else, could feed this as a request into the bug > tracking tool. So it won't get lost, even if implementation takes time. > Unfortunatly it comes to late for the gremlins hunt. You may also > provide a patch for it. > > http://bugs.typo3.org I've recently made some changes to that class, but didn't commit them yet. Whoever submits the bug, please assign it to me, so I'll take care of it. - michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From ernst at cron-it.de Wed Nov 30 00:24:37 2005 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Wed, 30 Nov 2005 00:24:37 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE In-Reply-To: References: Message-ID: On 29.11.2005 17:21, Kai Laborenz wrote: > maybe I missed it. The COA IMAGE assigns the alt value also to the title > attribute - this is not good practice. > > Is there a way around it? The cron_cssstyledimgtext, which provides rendering for IMGTEXT and IMAGE cObjects provides some options to configure the alt and title tags. See: http://typo3.org/documentation/document-library/cron_cssstyledimgtext/IMAGE-3/ There are some recommended settings for "accessibility", and others for "browser-compatibility". This EXT will hopefully get merged into css-styled-content in TYPO3 4.0, so that in future we will have this (or very similar) options out-of-the-box. If you have other suggestions to improve this part of the extention, you are welcome to provide feedback on that! Cheers, Ernesto From typo3 at laborenz.de Wed Nov 30 07:33:07 2005 From: typo3 at laborenz.de (Kai Laborenz) Date: Wed, 30 Nov 2005 07:33:07 +0100 Subject: [TYPO3-content-rendering] ALT and TITLE In-Reply-To: References:

Message-ID: Ernesto Baschny [cron IT] schrieb: > The cron_cssstyledimgtext, which provides rendering for IMGTEXT and > IMAGE cObjects provides some options to configure the alt and title > tags. See: > > http://typo3.org/documentation/document-library/cron_cssstyledimgtext/IMAGE-3/ > > There are some recommended settings for "accessibility", and others for > "browser-compatibility". Ah - this is what I am looking for! This should definitely go into the core. Regards, Kai