Early this morning, Axiom launched the new International Web site. For our international shoppers the new International Web site will take all the headaches out of calculating the import duties, freight and special taxes on any Axiom purchases, and will do so in the currency of the customer’s country of residence. The new International Web site also has a dynamic feature that links the costs of Axiom products in non-US currencies back to the price of each item in US dollars.

For those of you in the US and Canada, the website will look much the same. However, the drop down country bar now includes a long list of countries and there are a number of currency choices in a drop down menu at the bottom of each page.

At Axiom we value the input of our faithful board members. Please take a moment to check out the changes to the website and give us some feedback as to what you think.

I don't speak any other languages...so other than that it looks great!

One thing though on the bottom where the two drop down boxes are for currency and country, they are not lined up correctly. The currency box is higher to the left than the country box. Just looks a little sloppy since the rest of the site is so well-aligned.

I noticed the same thing and poked around the html to look for a cause of the misalignment -- which incidentally only occurs in Firefox for me. There are some tags in the footer section which violate the "all tags should open and close within the same parent tag" rule and are probably causing the rendering glitch:

• The form tag with name "footer" opens in one td but closes in another.
  
• The div tag that opens immediately after the currency menu but before the country menu doesn't close until after the copyright statement.
  

Yea...most web developers know that Firefox interprets HTML code the correct way. Internet Explorer kinda goes "Well...I think you mean this, so I'll just do it"

I've had some websites where internet explorer ignored all div tags for justifying text. All the clients in on the website used Firefox, and none of us thought to check in IE.

It's fixed.