OmegaT - multiplatform CAT tool / Documentation / #441 Update L10N wiki page

The free computer aided translation (CAT) tool for professionals

#441 Update L10N wiki page

Milestone: dev-docs

Status: closed-fixed

Owner: DiGro

Labels: None

Priority: 5

Updated: 2025-02-25

Created: 2025-02-22

Creator: Jean-Christophe Helary

Private: No

@digro, thank you for your work on the l10n page. I noticed a few very outdated things. Would you mind taking the time to fix them?

As of 6.0, the figures are different.

there are 42 Bundle.properties files (including EN)
there are 29 manuals, of which 6 are at v6, 7 are at v4, 5 at v3, 11 at v2.
there are 31 different languages for the web site

OmegaT’s l10n can eventually be done outside OmegaT but

it is not a good idea to do it that way because
any l10n related file must be delivered from within the l10n projects.

So we need to rephrase that part a bit.

We do not provide l10n packages anymore. The link points are obsolete files and we should remove it (we should also remove that repository from SF).

The sentence “The preferred way to localize...” looks like a link. But it is (at least partially) not a link. The link should point at this page:
https://github.com/orgs/OmegaT-L10N/repositories

The prerequisite is not to use “OmegaT Latest” any more. That version does not exist. It should be pointing at “OmegaT Standard”. “Account at GitHub.com (registration is free)” should also add “and an access token” with the appropriate link to create one.

“ therefore pull requests for translated materials may not be the best way to contribute.” → we do not accept PRs for l10n updates.

“Enter your GitHub.com username and password” should be “access token”.

Discussion

Jean-Christophe Helary - 2025-02-22

Group: 5.8-6.0 - user manual --> dev-docs
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jean-Christophe Helary - 2025-02-22

I’m putting the issue in "dev-docs" even if it is not in the dev-docs manual. @miurahr9, can you confirm that this part is valuable in the dev-docs manual ?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -1,25 +1,24 @@
-@digro, thank you for your work on the l10n page. I noticed a few very outdate things. Would you mind taking the time to fix them?
+@digro, thank you for your work on the l10n page. I noticed a few very outdated things. Would you mind taking the time to fix them?

-(Also

-As of 6.0, there are a number of things that need to be updated.
+As of 6.0, the figures are different.

 - there are 42 Bundle.properties files (including EN)
 - there are 29 manuals, of which 6 are at v6, 7 are at v4, 5 at v3, 11 at v2. 
 - there are 31 different languages for the web site

 OmegaT’s l10n can eventually be done outside OmegaT but
-- it is not a good idea to do that that way because
+- it is not a good idea to do it that way because

 - any l10n related file *must* be delivered from within the l10n projects.

 So we need to rephrase that part a bit.

 We do *not* provide l10n packages anymore. The link points are obsolete files and we should remove it (we should also remove that repository from SF).

-The sentence &#34;The prefered way to localize...&#34; looks like a link. But it is (at least partially) not a link. The link should point at this page:
+The sentence “The preferred way to localize...” looks like a link. But it is (at least partially) not a link. The link should point at this page:
 https://github.com/orgs/OmegaT-L10N/repositories

-The prerequisite is not to use &#34;OmegaT Latest&#34; any more. That version does not exist. It should be pointing at &#34;OmegaT Standard&#34;. &#34;Account at GitHub.com (registration is free)&#34; should also add &#34;and an access token&#34; with the appropriate link to create one.
+The prerequisite is not to use “OmegaT Latest” any more. That version does not exist. It should be pointing at “OmegaT Standard”. “Account at GitHub.com (registration is free)” should also add “and an access token” with the appropriate link to create one.

-&#34; therefore pull requests for translated materials may not be the best way to contribute.&#34; → we do not accept PRs for l10n updates.
+“ therefore pull requests for translated materials may not be the best way to contribute.” → we do not accept PRs for l10n updates.

-&#34;Enter your GitHub.com username and password&#34; should be &#34;access token&#34;.
+“Enter your GitHub.com username and password” should be “access token”.

Jean-Christophe Helary - 2025-02-22

Thank you !

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

DiGro - 2025-02-22

You're welcome.
Fixed and updated now.
Please let me know if anything should be changed

Don't know how to close this issue, would you mind...

Last edit: DiGro 2025-02-22

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jean-Christophe Helary - 2025-02-25

status: open --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Update L10N wiki page

The free computer aided translation (CAT) tool for professionals

Group

Searches

Help

#441 Update L10N wiki page

Discussion