|
| Conference |
|
Adam has been working with a team of distinguished internationalization
experts in our industry to create the new Worldware
Conference.
The conference was created to provide technical management information
to help you make internationalization a regular part of your
software development. Have a look over the program and you’ll
see it’s quite full of both technical and process oriented
curriculum.
|
|
What
we are up to |
|
Assess, fix and monitor internationalization
issues in code
March 12, 2009
Noon to 1:15 PM Mountain Time
(GMT-7)
Can’t make it to Worldware?
Attend
this webinar and learn as we go through issues to look for and
examine a few hundred thousand lines of code and step you through
the issues. As you might guess, we’ll be using
Globalyzer 3.0 to do it, but rather than make this about a product
demo, we’ll be working through internationalization coding
issues and fixing them. This webinar will feature interactive
technical discussions with our architectural team. Our past seminars
have always filled up quickly, so sign up soon by emailing webinar@lingoport.com with
your name, company and contact information.
Click
here to find out what you'll learn... |
|
|
If you prefer to read
this online go to: http://www.lingoport.com/company/newsletter/0209/
Welcome to Lingoport’s February 2009 WorldReady
Newsletter
We have some great product development work and events to tell you about in this newsletter. Here’s the short list version with links:
- Globalyzer
3.0 release is going beta in March – learn
why this is cool and how you can get involved
- Free Webinar – How to assess and work through
internationalization issues in your code
- Worldware
Conference – learn from leaders, meet yours truly
- Latest
Multilingual computing article, including a tool to fix character
corruption in your database through an encoding error
While there are plenty of process tools to help developers with
bug tracking and performance issues, there’s very little
available to support development teams in building and maintaining
world-ready code. Globalyzer has always had the promise of supporting
entire development teams in their internationalization efforts,
and the 3.0 release represents a major milestone in making that
promise far easier to implement. We’re going to beta on
Globalyzer 3.0 in March and if you think it’s important
to support your developer and QA teams in creating world-ready
code, we invite you to get
involved.
Best regards,
Adam Asnes
Lingoport, Inc.
P.S. Internationalizing code is clearly connected
to competing globally for software revenue. Remember that while
the economic news is gloomy here, elsewhere markets are likely
to bounce back faster, demanding world-ready products. Talk to
us about making your globalization efforts faster, better and
cheaper. You really can have all three. |
|
|
 We’re getting ready for a major release of Globalyzer. We will be going beta in March. Globalyzer 3.0 features a major rewrite of much of Globalyzer’s code base. The emphasis of this release is on making Globalyzer far more powerful in supporting enterprise-wide internationalization, both during initial refactoring efforts, and over time as new development occurs. Here’s a list of ten, no eleven, leading new features and benefits:
1) Database enabling of Globalyzer reporting – Globalyzer
3.0 comes with its own database, or the option to connect to
your current database. You can compare Globalyzer results over
time, track individual internationalization issues from scan
to scan and share scan results and fixes with your fellow developers.
2) Command-Line integration with ANT and automated
processes – Command Line, though less exciting to look
at, offers tremendous power in supporting entire teams of developers
in monitoring and measuring internationalization. With Command
Line, Globalyzer can now become the benchmark for localization
readiness. We’ve included a wizard to help teams get
Globalyzer up and included in automated processes, like a nightly
build.
Click
here to read all 11 new features and benefits... |
|
|
 Chances
are you’ve seen corrupted data, but perhaps didn’t
think too much about it unless you’re a localization
engineer. Most people see it first in their spam, coming with
promises of Euro-Lottery millions or other nefarious offers.
The corruption evidence is in the square boxes or random nonsensical
characters that fill the subject heading or email body, if
you haven’t deleted it already. What’s happening
is that somewhere along the way, or in your mail client, the
character encoding the message is written in is not being supported.
Obviously you wouldn’t feel very confident using a product,
site or system that suffers this same issue, so it’s
a clear defect. Sometimes you even see it when everything is
still all English, most notoriously when somewhere along the
way the software system you are using can’t process a
simple apostrophe.
Click
Here to read the complete article... |
|
