From poy at 123gen.com Sun Feb 22 16:14:50 2009 Content-Type: multipart/mixed; boundary="===============3998694246263478611==" MIME-Version: 1.0 From: poy To: devel at lists.po4a.org Subject: [Po4a-devel] and in the XHTML module Date: Sun, 22 Feb 2009 17:08:02 +0100 Message-ID: <16FF967AD1F24D04A95C9C4A0065C86B@ZOUZOU> --===============3998694246263478611== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable hi, in the XHTML module, i believe and tags, which are used to = specify clickable sections of images, shouldn't be considered inline tags. = ( is currently in the '_default_inline' list.) thanks, poy = --===============3998694246263478611==-- From nicolas.francois at centraliens.net Sun Feb 22 17:35:45 2009 Content-Type: multipart/mixed; boundary="===============3922940322124706808==" MIME-Version: 1.0 From: =?utf-8?q?Nicolas_Fran=C3=A7ois_=3Cnicolas=2Efrancois_at_centraliens=2Ene?= =?utf-8?q?t=3E?= To: devel at lists.po4a.org Subject: Re: [Po4a-devel] and in the XHTML module Date: Sun, 22 Feb 2009 18:35:27 +0100 Message-ID: <20090222173527.GD6190@nekral.nekral.homelinux.net> In-Reply-To: 16FF967AD1F24D04A95C9C4A0065C86B@ZOUZOU --===============3922940322124706808== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Sun, Feb 22, 2009 at 05:08:02PM +0100, poy(a)123gen.com wrote: > hi, > = > in the XHTML module, i believe and tags, which are used to = > specify clickable sections of images, shouldn't be considered inline tags= . = > ( is currently in the '_default_inline' list.) It's unclear to me what should be the default behavior. Having as inline permits an easy translation of the coordinates. Also, this permits to add areas in the map (image might be translated, and requiring different set of areas) Maybe should be a placeholder (and to be explicitly added to the inline category)? (BTW, I think I did not answer to you regarding the tags used for placeholder. This was fixed a bit differently from your proposal, but the idea of having a valid tag was implemented) Best Regards, -- = Nekral --===============3922940322124706808==-- From poy at 123gen.com Sun Feb 22 21:39:35 2009 Content-Type: multipart/mixed; boundary="===============8818582989653062740==" MIME-Version: 1.0 From: poy To: devel at lists.po4a.org Subject: Re: [Po4a-devel] and in the XHTML module Date: Sun, 22 Feb 2009 22:39:24 +0100 Message-ID: <45E0DD1105CF4835B01A1182914D258B@ZOUZOU> In-Reply-To: 20090222173527.GD6190@nekral.nekral.homelinux.net --===============8818582989653062740== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable > It's unclear to me what should be the default behavior. this was hasty i'll explain a bit more... an example / set of tags looks like this: neither nor specify any text, so i believe they should simply = be kept out of translations; considering them breaking tags solves this. right now, is inlined but is not, so as a result i have the = following texts in the pot file: # type: Content of:

#: help\window_main.html:129 msgid "" msgstr "" # type: Content of:

#: help\window_main.html:146 msgid "" msgstr "" if is to be kept inlined, then so should ; my opinion however i= s = that neither should be inlined since there is no text to translate inside o= f = them. the only translatable text is the "alt" attribute, but that one is already = taken care of in the 'attributes' list of options - see related comment = about and why isn't in that inline list either. my demand basically boils down to: remove from the "inline" list of = tags. > Having as inline permits an easy translation of the coordinates. > Also, this permits to add areas in the map (image might be translated, and > requiring different set of areas) this is a very edge case, and in that case the person will have to add = , and (to change the image url) to inline tags. but for = general use i don't think the default should be to display all those = tags in translations and have translators try to mess with coordinates... the current policy is to already ignore (see comment in Xhtml.pm:215)= , = the same should apply to and . > (BTW, I think I did not answer to you regarding the tags used for > placeholder. This was fixed a bit differently from your proposal, but the > idea of having a valid tag was implemented) (i noticed the changes, they look good but still aren't exactly what i = wanted... thanks for your efforts though.) poy = --===============8818582989653062740==-- From nicolas.francois at centraliens.net Sun Feb 22 22:15:12 2009 Content-Type: multipart/mixed; boundary="===============8642902109347315138==" MIME-Version: 1.0 From: =?utf-8?q?Nicolas_Fran=C3=A7ois_=3Cnicolas=2Efrancois_at_centraliens=2Ene?= =?utf-8?q?t=3E?= To: devel at lists.po4a.org Subject: Re: [Po4a-devel] and in the XHTML module Date: Sun, 22 Feb 2009 23:14:57 +0100 Message-ID: <20090222221457.GE6190@nekral.nekral.homelinux.net> In-Reply-To: 45E0DD1105CF4835B01A1182914D258B@ZOUZOU --===============8642902109347315138== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Sun, Feb 22, 2009 at 10:39:24PM +0100, poy(a)123gen.com wrote: > > if is to be kept inlined, then so should ; my opinion however = > is that neither should be inlined since there is no text to translate = > inside of them. > > the only translatable text is the "alt" attribute, but that one is = > already taken care of in the 'attributes' list of options - see related = > comment about and why isn't in that inline list either. > > my demand basically boils down to: remove from the "inline" list of = > tags. Yes, that's right. It also makes a sensible default with less strings to translate. Most people will probably choose not to translate strings. I removed from _default_inline. >> (BTW, I think I did not answer to you regarding the tags used for >> placeholder. This was fixed a bit differently from your proposal, but the >> idea of having a valid tag was implemented) > > (i noticed the changes, they look good but still aren't exactly what i = > wanted... thanks for your efforts though.) I thought I did. So lets answer to that thread. Best Regards, -- = Nekral --===============8642902109347315138==--