Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Cosmetic issues in OSC


Dj-Viper

Recommended Posts

Hi, 

 

I have a few cosmetics problems in 2.3.3.3 version of osc..

 

see http://www.fotomeinema.nl/oscommerce1.jpg

 

First you see that the euro sign is not there but a few strange characters.

 

Second the product image is very large, this different each time want to have there a fixed size.

 

Third, the text is un readable, the font size or font type is not good where can i change that.

 

Greetings, Anne

 

Link to comment
Share on other sites

solution: use database conversion on oscommerce admin site for utf8 characters as this was mentioned in upgrade documents.

:blink:
osCommerce based shop owner with minimal design and focused on background works. When the less is more.
Email managment with tracking pixel, package managment for shipping, stock management, warehouse managment with bar code reader, parcel shops management on 3000 pickup points without local store.

Link to comment
Share on other sites

The text is in UTF-8 (multibyte), but the page is being displayed in Latin-1 encoding. The page display should be UTF-8, so that problem needs to be solved first. Are you using an old language definition (e.g., nederlands.php) that still defines the page encoding as Latin-1 (ISO-8859-1)?

Link to comment
Share on other sites

Hi, Was using the newest version of the dutch.php that i could find here on site at the addons..

 

Fixed the lettertype and size in stylesheet.css was a little puzzeling..

 

Fixed the image site with a empty products_images table and sql query : INSERT INTO `products_images` (`products_id`, `image`) SELECT `products_id`, `products_image` FROM `products`

 

Greetings, Anne

Link to comment
Share on other sites

"Newest" is meaningless if it hasn't been updated for the osC version you're using. Does it set the locale and encoding to use latin1/iso-8859-1 or utf-8? The Euro symbol was defined somewhere as a UTF-8 character, and the page is displaying in Latin-1. You changed it to x80 (128), which is Latin-1 (actually, Windows-125x) encoding.

Link to comment
Share on other sites

"nl_NL.ISO_8859-1" would be Latin-1 (ISO-8859-1). If the rest of the site's language files and the database are all in UTF-8, you should be able to change this entry to "nl_NL.UTF-8" (I think... better check first for the exact format). If the language files are all Latin-1, they will need to be converted to UTF-8. If they're a mixture of Latin-1 and UTF-8, you have a mess on your hands. Same goes for the database.

 

If this version of osC is supposed to be UTF-8 right out of the box (I believe it is), it sounds like the Dutch language pack you are using is incorrect (for an earlier, Latin-1 version). I wouldn't try using it until it has been checked. You would compare all the entries between the 2.3.3.3 English default and the Dutch pack, and add/modify to bring the Dutch version up to date. All accented (non-ASCII) characters, including the Euro, would have to be translated to UTF-8. Needless to say, you shouldn't try any of this unless you know exactly what you're doing!

Link to comment
Share on other sites

ended up with this But MrPhil  is the expert so may be not quite correct!!


   @setlocale(LC_TIME, 'nl_NL.ISO_8859-1' , 'Dutch');
   
define('DATE_FORMAT_SHORT', '%d.%m.%Y');        // this is used for strftime()
define('DATE_FORMAT_LONG', '%A, %d %B %Y');     // this is used for strftime()
define('DATE_FORMAT', 'd/m/Y');                 // this is used for date()
define('DATE_TIME_FORMAT', DATE_FORMAT_SHORT . ' %H:%M:%S');
define('JQUERY_DATEPICKER_I18N_CODE', 'nl'); // leave empty for en_US; see http://jqueryui.com/demos/datepicker/#localization
define('JQUERY_DATEPICKER_FORMAT', 'mm/dd/yy'); // see http://docs.jquery.com/UI/Datepicker/formatDate
////
// Return date in raw format
// $date should be in format mm/dd/yyyy
// raw date is in format YYYYMMDD, or DDMMYYYY        // Nederlandse notering
function tep_date_raw($date, $reverse = false) {
  if ($reverse) {
    return substr($date, 0, 2) . substr($date, 3, 2) . substr($date, 6, 4);
  } else {
    return substr($date, 6, 4) . substr($date, 3, 2) . substr($date, 0, 2);
  }
}

// if USE_DEFAULT_LANGUAGE_CURRENCY is true, use the following currency, instead of the applications default currency (used when changing language)
define('LANGUAGE_CURRENCY', 'EUR');

// Global entries for the <html> tag
define('HTML_PARAMS', 'dir="ltr" lang="nl"');

// charset for web pages and emails
define('CHARSET', 'utf-8');
To improve is to change; to be perfect is to change often.

 

Link to comment
Share on other sites

Hi,

The Dutch language pack downloaded from the addons for 2.3

 

In the dutch.php 

 

stands above in file : @setlocale(LC_TIME, 'nl_NL.ISO_8859-1' , 'Dutch');

 

and in the middle // charset for web pages and emails

define('CHARSET', 'utf-8');
 
Greetings, Anne
Link to comment
Share on other sites

Did the convert to utf-8 on the database.. everything looks good as far..

 

 

Still a few little problems that i have to fix..

 

1. Administration, menu etc is not showing up correctly, the menu is in de middle en de information is underneath.

2. Only two options of payment is showing up in admin 3 is under install modules activated.

 

Greetings, Anne

Link to comment
Share on other sites

Hi,

 

Looks like everthing is fixed...

 

Payment - apperantly for the contri that i use for ideal had to install 2 modules (was not in the setup file of the contri)

 

Menu admin - was messed up because was installing and editing offline with xampp, apperently the jquery css file was not working in offline mode.

 

Greetings, Anne

Link to comment
Share on other sites

stands above in file : @setlocale(LC_TIME, 'nl_NL.ISO_8859-1' , 'Dutch');

 

and in the middle // charset for web pages and emails

define('CHARSET', 'utf-8');

OK, it initially sets the locale to use Latin-1 (ISO_8859-1), and then it overrides it by defining the CHARSET to UTF-8 (what the pages are set to). I would call it a minor bug in the 2.3 Dutch language pack (unless it was intended to be Latin-1, and the CHARSET is the bug), but if you've got it working now, fine. You had to convert to UTF-8 yourself? I thought 2.3 was supposed to be UTF-8 from the start. Or was that 2.3.3?

Link to comment
Share on other sites

Hi,

 

It was 2.3.3.3 version of osc.. Converted the database tables to the UTF-8 format and everything looks good..

 

In time after setting everything up and everything runs good, will upgrade again to higher versions of osc.

 

Greetings, Anne

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...