Messages

1

HTML & templates / Re: next default template

« on: June 27, 2010, 12:31:18 PM »

As I mentioned, this is not a problem for Spanish, I was only concerned about localization for other languages.
AFAIK, it's generally accepted by programmers that hardcoding strings makes localization more difficult, so it's not a good practice.

This is constructive criticism, I do appreciate the time and effort spent in this useful application, that's why I posted.

2

HTML & templates / Re: next default template

« on: June 27, 2010, 12:15:16 PM »

I see. However IMHO having the B hardcoded should be avoided. Notice it doesn't even appear with the variable unlike what SilentPliz has reported about the french version.

I only noticed it because I was trying to translate the latest template into Spanish, and when searching for any ".!" string, I found this odd thing at the end of the line, and when trying to "fix it", I got the double B.
Not that it matters for Spanish (since for sizes we use the same english words), but it might be source of problems for other languages.

IMHO if full localization is in the ToDo list, this should be addressed with a more general approach than hardcoding the strings.

3

HTML & templates / Re: next default template

« on: June 27, 2010, 04:30:47 AM »

I am not sure if this is the proper thread to post this, but I believe there's an error in the default template of HFS 2.3.260, around #381:

      <div id='folder-stats'>%number-folders% {.!folders.},  %number-files% {.!files.}, %total-size%ytes

At the end of the line, shouldn't it rather say : "%total-size% {.!Bytes.}" ?

4

Beta / Re: Testing build #260

« on: June 27, 2010, 04:24:35 AM »

I was testing HFS 2.3.260 (on Windows XP SP3 with Firefox 3.6.3), and noticed a couple of bugs:

Regarding the login function:
If you click on login and then cancel, it should leave you in the same page you were at, not take you to the unauthorized page.

If you click on login and enter a random user name and password, a number of odd things happen:
-The browser does not take you to the unauthorized page like it should, but keeps asking for the login info, endlessly.
-The login info gets cached (yes, even when wrong). This happens even if you have disabled in the browser the option to remember passwords.
-If you cancel to break the loop, you cannot return to the previous page either by pressing the browser's back button or typing the address.
-If you don't enter the info again and instead simply press OK after the first failed logon, the browser returns to the page you were at rather than asking for the info again or taking you to the unauthorized page, like it should. If you click on login a second time, the browser enters an endless loop (apparently it keeps reading the wrong info, that's how I figured it was being cached). You have to clean the browser's active sessions for the login function to work again.