Adding a backslash before <lang> in the paths for localization and documentation files

Right now there isn't a backslash before the placeholder to show that the language code needs to be a folder. So the user may write, for instance, addon\localees\LC_MESSAGES\nvda.po instead of addon\locale\es\LC_MESSAGES\nvda.po. I actually did that mistake, although I had my doubts.

Hi, I see. Note that some of us use Linux tools to build add-ons, and add-on template is an optional package. We need a traceback if a problem with missing backslashes can be reproduced consistently. Thanks.

No error is generated but when you install the add-on the languages you have localized it for them don't work.

…

On Wed, Dec 23, 2020 at 10:20 PM Joseph Lee ***@***.***> wrote: Hi, I see. Note that some of us use Linux tools to build add-ons, and add-on template is an optional package. We need a traceback if a problem with missing backslashes can be reproduced consistently. Thanks. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHARQ2STLFJI3E7BBPEW37DSWI3VVANCNFSM4VHJKLQA> .

By the way, I'm talking about the readme file. The template itself has no problem. On Thu, Dec 24, 2020 at 1:38 AM Meisam Amini <meisamamini21@gmail.com> wrote:

…

No error is generated but when you install the add-on the languages you have localized it for them don't work. On Wed, Dec 23, 2020 at 10:20 PM Joseph Lee ***@***.***> wrote: > Hi, I see. Note that some of us use Linux tools to build add-ons, and > add-on template is an optional package. We need a traceback if a problem > with missing backslashes can be reproduced consistently. Thanks. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#18 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AHARQ2STLFJI3E7BBPEW37DSWI3VVANCNFSM4VHJKLQA> > . >

Hi, I see multiple possibilities: the add-on in question didn’t call the addonHandler.initTranslation function (required to get the translations to show up and work), file encoding error when converting .po to .mo, among other things. Thanks.

Hi, ah, that clarifies a lot. I’ll look into it, as it could be the workflow issue. Thanks.

Hi,

January 2024 update: any updates? If not, since we haven't heard from the original poster in over three years, I vote to closing this issue.

Thanks.

Hi,

November 2024 update: closing as no update for over four years.

Bump the uv group across 1 directory with 3 updates (nvdaaddons#18)

Navigation Menu

Adding a backslash before <lang> in the paths for localization and documentation files #18

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Adding a backslash before <lang> in the paths for localization and documentation files #18

Description

Activity

josephsl commented on Dec 23, 2020

MeisamAmini commented on Dec 23, 2020

MeisamAmini commented on Dec 23, 2020

josephsl commented on Dec 23, 2020

josephsl commented on Dec 23, 2020

josephsl commented on Jan 1, 2024

josephsl commented on Nov 14, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions