English Localization and Text Representation

[anatawa12]

This is discussion for English Localization and text representation.

Please feel free to suggest better localization / representation here.

The maintainer of English localization is @anatawa12 and @Sayamame-beans.

[lu-na-r]

I found that key: projects:dialog:warn remove project in Japanese has its unique message: "If you remove the directory, you cannot undo this action."（ファイルを削除した場合は復元出来ません）although other supported language only says "Are you sure?".

I wonder if this message should be standard. I you are for, I will add this in the value.

[lu-na-r]

@anatawa12 @Sayamame-beans

[anatawa12]

I think "are you sure" is enough but sayamame added that in jp localization.

In addition, in current version of ALCOM moves the folder to trash folder instead of removing permanently so It's incorrect statement now.

[Sayamame-beans]

moves the folder to trash folder instead of removing permanently

Certainly! I forgot about that change. Hmm...

[lu-na-r]

Got it, thank you. We may as well discuss it in Japanese localisation channel instead.

[lu-na-r]

@anatawa12 @Sayamame-beans

These three keys: projects:manage:dialog:uninstall package as requested, projects:manage:dialog:uninstall package as legacy and projects:manage:dialog:uninstall package as unused have a little bit different values between English and Japanese.

English:

    "projects:manage:dialog:uninstall package as requested": "Remove <b>{{name}}</b> as you requested",
    "projects:manage:dialog:uninstall package as legacy": "Remove <b>{{name}}</b> since it's a legacy package",
    "projects:manage:dialog:uninstall package as unused": "Remove <b>{{name}}</b> since it's not used",

which means

    "projects:manage:dialog:uninstall package as requested": "リクエストの通り、<b>{{name}}</b>を削除します。",
    "projects:manage:dialog:uninstall package as legacy": "レガシーパッケージなので、{{name}}</b>を削除します",
    "projects:manage:dialog:uninstall package as unused": "使われていないので、<b>{{name}}</b>を削除します。",

Japanese:

    "projects:manage:dialog:uninstall package as requested": "<b>{{name}}</b> をアンインストール",
    "projects:manage:dialog:uninstall package as legacy": "レガシーパッケージとして <b>{{name}}</b> をアンインストール",
    "projects:manage:dialog:uninstall package as unused": "使用されていない <b>{{name}}</b> をアンインストール",

I doubt that you ought to say "as you requested" or "since......". Based on Japanese localisation, we can simply say like below. What do you say to this?

    "projects:manage:dialog:uninstall package as requested": "Remove <b>{{name}}</b>.",
    "projects:manage:dialog:uninstall package as legacy": "Remove <b>{{name}}</b> as a legacy package.",
    "projects:manage:dialog:uninstall package as unused": "Remove <b>{{name}}</b> which is unused.",

[anatawa12]

Almost all parts of ALCOM is developed for English and then localized to Japanese by Sayamame so difference in "As requested" is problem or decision of Japanese localization.

I think difference between "since It's not used" and "使用されてない~" is not major problem, just a minor expression difference so it's not a problem.

[lu-na-r]

Absolutely, the minor difference is not a problem, but the expression of my proposal is more recognisable, isn't it? That's why I ask you. What do you think about that?

[anatawa12]

I think removing reason should be expressed so I don't like removing "as you requested” entirely.
I feel "as a legacy package" and "レガシーパッケージとして" is a little incorrect so I don't like to change it to "as a legacy package".
I think "which is unused" is good.

[lu-na-r]

Got it, thank you! I'll make a pull request about this later.

[Sayamame-beans]

projects:tooltip:no directory is the string that is displayed if the project was not found in the directory specified in the project information.
Currently, it indicates that the project directory does not exist, but this can be a bit confusing if the project path has simply changed. (e.g. parent directory is renamed)

How do you think about replacing it with something like, "The project was not found at this location"(this sample text is not well-considered) instead?

[lu-na-r]

Here're some ideas...

• ALCOM cannot find this project at the registered directory.
• There is no project in the directory.
• The directory which you provided before is no longer a valid path.

[anatawa12]

Project does not exist at the location.

[Sayamame-beans]

I feel Project does not exist at the location. represents the situation in a nutshell.

[anatawa12]

The term Resolve in VPM system

In #930, I implemented detecting missing packages and ALCOM recommends the user to Resolve packages.
I want to discuss about the term "Resolve"

The "Resolve" means install all packages defined in vpm-manifest.json and it has several use cases.

• To install missing locked packages - When we cloned some package from VCS such as git, vpm packages (except for resolver) are missing in the project. Resolving packages will installs missing packages
• To install missing dependencies - The template only includes dependencies section. When we created project, the ALCOM will copy the template and resolve the new project to install packages.
• To fix broken package - When we modified files in the package, the package become broken. we can fix with resolving packages.

I want to use similar notation for all languages including english.
Therefore, I want to discuss about how translate it.

I have several idea:

• Use direct word translation for "Resolve". I already see "パッケージを解決する" for package-manager-generic verb so it might be possible however, it's not easy for users to understand.
• Say "there are problems" and "fix problem" button. This is easy to implement but it does not describe what to do.
• Say "recommend to install packages" and "install package" button. This is also easy to implement and it describe what to do.

Is there any ideas?

For information, in ALCOM 0.1.0, resolving packages was implemented as "reinstall packages" button for the third use case.

[lonelyicer]

Say "there are problems" and "fix problem" button. Then list the problems that have arisen

[anatawa12]

If you reuse that string for those three use cases

I'll use the text added in #930 only for the first or possibly second use case of Resolve. so "The project requires packages which currently are not installed. This should be corrected." looks fine.

Say "there are problems" and "fix problem" button. Then list the problems that have arisen

I'm not for adding dialog to show problems.
I saied 'Say "there are problems"' but I mean describe the problem. Sorry for confusing.

[anatawa12]

After thinking a while, I feel this is good. How do you think that?

[lu-na-r]

"this project" rather than "the project"?

[anatawa12]

"this project" rather than "the project"?

That's better. thank you

[JustBuddy]

@anatawa12 @Sayamame-beans Not a fan of projects:type:custom being "Custom", it is not immediately clear that this is for templates and confused me while translating this dialog. I propose something among the lines of "Custom Template" to make this association clear.

What do you think?

[anatawa12]

Using "Custom Template" looks good!

[lu-na-r]

Done in #973

[Sayamame-beans]

• chore(i18n): add unity version info for unity not found toast #1002
  I'd like to add unity version information in projects:toast:match version unity not found as follows

- "No matching Unity version found. Please install Unity in your computer or add a Unity version in the ALCOM settings."
+ "Unity {{unity}} is not found. Please install Unity in your computer or add a Unity version in the ALCOM settings."

[Sayamame-beans]

This PR has been merged.

[JustBuddy]

I'd love to see the "Search for Updates" key split up a bit, this menu item looks a bit awkward right now, since caption and button text is the same.
"settings:check update"

I would like to see it more like:
"settings:check update" : "ALCOM Updates",
"settings:check update:button" : "Check for updates",

What do you think?

[Sayamame-beans]

Sounds good?
Also there's space to add an option to receive beta updates of ALCOM or not in the future... maybe?

[anatawa12]

I think it's good.