Results 1 to 2 of 2

Thread: [I18N] Internationalising your app...

  1. #1

    Thread Starter
    Frenzied Member zuperman's Avatar
    Join Date
    Dec 2000
    Location
    Portugal
    Posts
    1,033

    [I18N] Internationalising your app...

    will this affect your sales...

    have you made it before...

    do you translate your own applications/help files...how do you handle this...

    some feedback appreciated...thx in advance...
    Help keep this forum clean: Remember to mark your thread as resolved · Search before you post · Remember to rate posts that help

    VS2010: Visual Studio 2010 Keybinding Posters
    · Service Pack 1
    Tools: GhostDoc - automatically generates XML documentation comments
    · NuGet package Manager · PowerCommands IDE extensions
    Source Control: ankhsvn - integration for SVN
    · Windows Shell Extension for Subversion

    Development Laptop: Intel Core i5 430M 2.26 GHz @ 2.53 GHz
    · 4096 MB, DDR3 PC3-8500F (533 MHz), Kingston · ATI Mobility Radeon HD 5470 · 15.6 @ 16:9, 1366x768 pixel, HD LED LCD

    I follow:
    JoelOnSoftware - A weblog by Joel Spolsky, a programmer working in New York City, about software and software companies
    ScottGu's Blog - Scott Guthrie works for Microsoft as the Product Manager of the .NET Framework
    Portugal-a-Programar - Portuguese Developers Community
    .NET Rocks! - is a weekly Internet audio talk show for .NET Developers.

    Programming Languages:
    C#
    · VB.NET · JAVA · PHP · Javascript
    Other:
    XML
    · HTML · CSS · JQuery · SQL



    *** Proudly Portuguese ***

  2. #2
    Lively Member homer13j's Avatar
    Join Date
    Nov 2003
    Location
    Ohio Turnpike Exit 173
    Posts
    80

    Re: [I18N] Internationalising your app...

    I have only done it once, but it wasn't too terribly difficult.

    Every unique string (about 2600 total) displayed in the program was stored in and loaded from a string table. When we were ready to start marketing our product in Quebec we simply sent the string table and help docs out to a translation service who returned them in French.

    Fortunately we had a beta tester who was fluent in French and he pointed out a couple of issues where a direct translation was not quite right and suggested changes for the final release. The only problem after that was finding someone for tech support who spoke the language and could take calls from Quebec.

    And yeah... it affected sales. Opening up a new market for your product certainly can't hurt.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width