Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. C#
  4. localization

localization

Scheduled Pinned Locked Moved C#
csharpwinformsvisual-studiodesignhelp
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    brain2cpu
    wrote on last edited by
    #1

    After years of development I get to my first multilanguage application, and I have a problem. The windows forms part is almost ok: create the form with localize true, design it for default, after that load the form for every language, edit every text of every component - quite annoying.... but it works. The problem is with strings (messages to the user). My first idea was to store them as resource strings, but resource does not have a language so a winforms-like approach not works. Now I store strings in external text files but this way is plain ugly. Please, please shed some light - what would be the good way... (using Visual Studio 2005)

    L 1 Reply Last reply
    0
    • B brain2cpu

      After years of development I get to my first multilanguage application, and I have a problem. The windows forms part is almost ok: create the form with localize true, design it for default, after that load the form for every language, edit every text of every component - quite annoying.... but it works. The problem is with strings (messages to the user). My first idea was to store them as resource strings, but resource does not have a language so a winforms-like approach not works. Now I store strings in external text files but this way is plain ugly. Please, please shed some light - what would be the good way... (using Visual Studio 2005)

      L Offline
      L Offline
      lmoelleb
      wrote on last edited by
      #2

      Have you tried creating a resx file for each language using the appropriate name (see the name of the resx files created by Visual Studio for the dialogs to determine the name)? Sorry I can't say anything for sure, I have only been doing enterprise level localization which involved a home build localization tool compiling the resx files. If you are going to do a reasonable size project, or more than one or two languages, consider buying a localization tool - they work MUCH better than VS (even though the tools you an buy are actually pretty bad they do have basic functionality missing in VS).

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups