Textpattern Forum

You are not logged in. Register | Login | Help

#61 2007-06-28 18:11:06

Mary
Sock Enthusiast
From: Canada
Registered: 2004-06-27
Posts: 6,235

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

…those on-line help pop-ups?

That’s the realm of the translators.


My email address has changed recently. If you need to contact me, use the forum contact form.

Offline

#62 2007-06-28 19:28:23

zero
Member
From: Lancashire
Registered: 2004-04-19
Posts: 1,034
Website

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

FWIW, I haven’t been able to find anything wrong with 4.0.5. I tend to run across problems all the time with anything related to computers or software so I am seeing this as a very good sign that 4.0.5 is very sound and solid.


TXPQ Examples and discussion of Textpattern CMS quality.

Offline

#63 2007-06-28 19:41:03

Els
Admin
From: The Netherlands
Registered: 2004-06-06
Posts: 7,383
Website

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

Sorry I can’t do any testing, I’m leaving for a three weeks holiday tomorrow… But thanks everyone for the good work and I’ll have something to look forward to when I return :) (and a bunch of sites to upgrade…)


<txp:Els /> ;)
Tag Reference | Unexpected behaviour? Check the tag trace | Still no clue? Check the names of your custom fields

Offline

#64 2007-06-29 04:32:20

wet
Developer
From: Lenzing, Austria
Registered: 2005-06-06
Posts: 3,099
Website

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

ruud wrote:

Could this be related to the preference “Textile link descriptions by default?” that is set to “yes”? […] but looking at tpt_link, I wonder whether it should be escaped at all when textiled, because then all the markup would be escaped as well. So I think it should not be escaped when textiled and escaped using escape_output when not textiled.

What if we added the same escape attribute to txp:link and txp:linkdesctitle we already use for txp:link_name and txp:link_description and leave it up to the site designer, as you are never safe whether the current prefs state also affected the data when the link was created?

Offline

#65 2007-06-29 11:05:04

ruud
Developer emeritus
From: a galaxy far far away
Registered: 2006-06-04
Posts: 4,501
Website

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

I think we have to assume that the prefs state is correct. If the site designer changes the pref along the way then it’s his/her responsibility to make sure the linknames are correct as well (save them again after changing the pref). If the old linknames aren’t corrected (by the site designer), setting the escape method manualy won’t help either, because either the old link names are incorrectly escaped or the new ones (after the pref change) are incorrectly escaped.
I’d definitely go for automatic escaping depending on the prefs state, because the escape method has to match the prefs state. And because prefs state and escape method have to match, doing it automatically is more user friendly (less risk of mistakes).

Last edited by ruud (2007-06-29 11:07:50)

Offline

#66 2007-06-30 00:10:45

Jeremie
Member
From: Provence, France
Registered: 2004-08-11
Posts: 1,578
Website

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

anoke wrote:

Btw, who/where/how one updates those on-line help pop-ups? Some are empty.

The dev for the English ones, the translators for the non English ones.

But the help system is fubar, and has been for quite some time (I believe my first documentation of that bug was in summer ’05). I know for example a lot of French help item are empty (while French documentation was the first non English written), because the help server don’t save them for some reason.

Offline

#67 2007-06-30 00:37:58

Neko
Member
Registered: 2004-03-18
Posts: 458

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

There’s a minor issue with “Files”, in Italian, entries such as file_name, file_status_ok, file_category appear as raw entries, ie not translated. I’ve checked the Translators interface and I can’t see them either (there’s no “File” section to translate).

Last edited by Neko (2007-06-30 00:39:08)

Offline

#68 2007-06-30 02:27:09

Mary
Sock Enthusiast
From: Canada
Registered: 2004-06-27
Posts: 6,235

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

There is, but it looks like you’ve found (another… *sigh*) bug in the lang server. Here’s the link.


My email address has changed recently. If you need to contact me, use the forum contact form.

Offline

#69 2007-06-30 08:07:26

Neko
Member
Registered: 2004-03-18
Posts: 458

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

Thanks, Mary. It says “Restricted area”, tho.

Offline

#70 2007-06-30 11:16:09

Mary
Sock Enthusiast
From: Canada
Registered: 2004-06-27
Posts: 6,235

Re: Feedback to: Help us test the release candidate for the upcoming 4.0.5

Ok, that’s very odd. I’ll have to try and figure it out. (The good thing is this not a Txp-specific issue, but a plugin issue.)


My email address has changed recently. If you need to contact me, use the forum contact form.

Offline

Board footer

Powered by FluxBB