Mult-language dialogs.

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Dave Harris

    #1

    Mult-language dialogs.

    Need some advice on how I can selectively access values from a resource. If
    I have a dialog and I turn "Localizati on" to true, nearly every value set in
    InitializeCompo nents() is gathered as a value from a resource and casted to
    the correct type.

    For the most part, I need only the "text" property, sometimes the size
    property and occasionally the location property. It is a waste of time and
    space to run the rest of the values through the lookup. The overhead is
    pretty immense. Best I can tell the compile size of InitiaizeCompon ents() +
    default resouce is approximately 5 times larger with than without
    localization.

    I took a 1.8 meg UI intensive DLL, turned all these flags on which resulted
    in a DLL that was 5.4 megs.

    Any advice appreciated. Thanks.
  • Marius Groenendijk

    #2
    Re: Mult-language dialogs.

    Dave,

    Been there too. Furthermore the framework doesn't allow making
    CultureInfos for some of the language-country combinations that
    we require so we rolled our own resource management.

    Source file, Xml easy to process with XmlReader :
    <Xlation>
    <Mnemonic>Hello World</Mnemonic>
    <Text>Bonjour Monde</GuiText>
    </Xlation>

    This we store in our own ResourceManager (e.g. a HashTable)
    Subclass the System.Windows. Forms.Form. In OnLoad or in the
    constructure you recursively loop through the controls.
    In our approach the *original* (design time) Text of a control
    is taken as the Mnemonic for its translation. So a button text
    "HelloWorld " would be translated into "Bonjour Monde".

    In fact our approach is more sophisticated than that but I hope
    you get the gist of it.

    In our app, the code that loops through the controls also takes
    care of translated tooltips configuring the help provider and has
    an intelligent look at the control (e.g. you wouldn't want to
    'translate' a text box or a datagrid for ex).
    As for sizing controls, this is done automatically (if necessary)
    using MeasureString after having translated the controls
    (e.g. length of "Bye" vs. "Hasta la Vista"). Using Docking you
    shouldn't have to worry too much about positioning but if this can be
    a problem in complex screens (we have rolled our own positioning stuff
    for multi-lingual data entry forms).

    Size of the app doesn't grow and InitializeCompo nents remains unchanged
    No satellite DLLs, maintaining the texts is easy; just edit the Xml.
    So far we're quite happy with what we did.

    HTH & Greetings,
    Marius.

    "Dave Harris" <Dave Harris@discussi ons.microsoft.c om> wrote in message
    news:528A70CF-5FDE-4B15-A475-CF26DD7E785E@mi crosoft.com...[color=blue]
    > Need some advice on how I can selectively access values from a resource.
    > If
    > I have a dialog and I turn "Localizati on" to true, nearly every value set
    > in
    > InitializeCompo nents() is gathered as a value from a resource and casted
    > to
    > the correct type.
    >
    > For the most part, I need only the "text" property, sometimes the size
    > property and occasionally the location property. It is a waste of time
    > and
    > space to run the rest of the values through the lookup. The overhead is
    > pretty immense. Best I can tell the compile size of InitiaizeCompon ents()
    > +
    > default resouce is approximately 5 times larger with than without
    > localization.
    >
    > I took a 1.8 meg UI intensive DLL, turned all these flags on which
    > resulted
    > in a DLL that was 5.4 megs.
    >
    > Any advice appreciated. Thanks.[/color]


    Comment

    • Marius Groenendijk

      #3
      Re: Mult-language dialogs.

      Dave,

      Been there too. Furthermore the framework doesn't allow making
      CultureInfos for some of the language-country combinations that
      we require so we rolled our own resource management.

      Source file, Xml easy to process with XmlReader :
      <Xlation>
      <Mnemonic>Hello World</Mnemonic>
      <Text>Bonjour Monde</GuiText>
      </Xlation>

      This we store in our own ResourceManager (e.g. a HashTable)
      Subclass the System.Windows. Forms.Form. In OnLoad or in the
      constructure you recursively loop through the controls.
      In our approach the *original* (design time) Text of a control
      is taken as the Mnemonic for its translation. So a button text
      "HelloWorld " would be translated into "Bonjour Monde".

      In fact our approach is more sophisticated than that but I hope
      you get the gist of it.

      In our app, the code that loops through the controls also takes
      care of translated tooltips configuring the help provider and has
      an intelligent look at the control (e.g. you wouldn't want to
      'translate' a text box or a datagrid for ex).
      As for sizing controls, this is done automatically (if necessary)
      using MeasureString after having translated the controls
      (e.g. length of "Bye" vs. "Hasta la Vista"). Using Docking you
      shouldn't have to worry too much about positioning but if this can be
      a problem in complex screens (we have rolled our own positioning stuff
      for multi-lingual data entry forms).

      Size of the app doesn't grow and InitializeCompo nents remains unchanged
      No satellite DLLs, maintaining the texts is easy; just edit the Xml.
      So far we're quite happy with what we did.

      HTH & Greetings,
      Marius.

      "Dave Harris" <Dave Harris@discussi ons.microsoft.c om> wrote in message
      news:528A70CF-5FDE-4B15-A475-CF26DD7E785E@mi crosoft.com...[color=blue]
      > Need some advice on how I can selectively access values from a resource.
      > If
      > I have a dialog and I turn "Localizati on" to true, nearly every value set
      > in
      > InitializeCompo nents() is gathered as a value from a resource and casted
      > to
      > the correct type.
      >
      > For the most part, I need only the "text" property, sometimes the size
      > property and occasionally the location property. It is a waste of time
      > and
      > space to run the rest of the values through the lookup. The overhead is
      > pretty immense. Best I can tell the compile size of InitiaizeCompon ents()
      > +
      > default resouce is approximately 5 times larger with than without
      > localization.
      >
      > I took a 1.8 meg UI intensive DLL, turned all these flags on which
      > resulted
      > in a DLL that was 5.4 megs.
      >
      > Any advice appreciated. Thanks.[/color]


      Comment

      Working...