Skip to content

How to localize the new Open-Shell #1551

Open

Description

@wmjordan

Is your feature request related to a problem? Please describe.

Currently Open-Shell is using old ClassicShell language files and some newly added option strings are not included there.

Describe the solution you'd like

Can you update the language template dll file?
So we can update the translation.

Area of issue

Installation/Other

Alternatives you've considered

No response

Additional context

No response

Activity

  1. ge0rdi commented on May 28, 2023

    @ge0rdi
    Member

    @wmjordan

    Can you update the language template dll file?

    Can you point out to the file you mean?
    I'm not sure where to find it.

    Note that we don't provide any localizations for Open-Shell currently.
    We are still waiting for some volunteer that will help with the localization system.

  2. wmjordan commented on May 29, 2023

    @wmjordan
    Author

    I meant the language DLL file.

    I am using the Chinese version and some newly added text are not in the language zh-CN.DLL file.
    image

    I previously localized that file and gave the file to ClassicShell.net.
    I hope that you can distill the resource strings into a new DLL file so I can keep on the localization work for Open-Shell.

  3. wmjordan commented on May 29, 2023

    @wmjordan
    Author

    The original localization template resource DLL file is mentioned in this page.

  4. ge0rdi commented on Jun 10, 2023

    @ge0rdi
    Member

    @wmjordan
    Sorry for the delay.

    Here is localization package that is created by the build process:
    OpenShellLoc.zip

    It should contain all files required for localization. Including the DLL you mentioned (en-US.dll).

    Hope this will help you.

  5. wmjordan commented on Jun 11, 2023

    @wmjordan
    Author

    Well, thank you for updating the file.
    I have finished the translation.

    Please update the web site and include my recent translation for Simplified Chinese.
    Just update the file will do. No need to change the author name of localization.

    image
  6. zedd-0 commented on Jul 25, 2023

    @zedd-0

    it would be nice if the language files changing from DLL to text/INI (unicode) files.
    so even people without programming knowledge can adapt the language files.

  7. wmjordan commented on Jul 25, 2023

    @wmjordan
    Author

    The DLL has its good side. With a localization tool, I can preview how labels line up in the interface and get feedback immediately whether a localized label is too long and truncated. When the size of a label is too small, I can enlarge it to fit the localized text.

    image

    Of course, the preview is only helpful when localizing dialogs or menus. The localization process of string resources has almost no difference than textual localization files, and the latter are always easier to edit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions