From poy at 123gen.com Sun Feb 22 21:39:35 2009 Content-Type: multipart/mixed; boundary="===============4385904965050748116==" 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 --===============4385904965050748116== 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 = --===============4385904965050748116==--