the l10n packages on GitHub use /trunk/ to refer to the source files

The free computer aided translation (CAT) tool for professionals

Brought to you by: alex73, amake, brandelune, briac_pilpre, and 10 others

#370 the l10n packages on GitHub use /trunk/ to refer to the source files

Milestone: 6.1

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2025-01-23

Created: 2021-03-29

Creator: Jean-Christophe Helary

Private: No

It seems that OmegaT l10n projects use the
https://github.com/omegat-org/omegat.git/trunk/doc_src/en
url to refer to the documentation sources.

That creates an error when loading the project locally with a ["https://github.com/omegat-org/omegat.git/trunk/doc_src/en" does not exist] error.

It looks like the /trunk/ path does not exist anymore.

Discussion

Kos Ivantsov - 2021-03-30

Docs are fetched using svn protocol from the OmegaT GitHub repository. It's done in order to fetch only /doc_src/en from the source tree instead of the whole hierarchy. Git doesn't allow that (or maybe it's only my level of git knowledge), but GitHub provides an svn emulation which makes it possible. I think this is where /trunk/ part comes from.
The error on the user's side is caused by GitHub timing out during its svn operation. Usually it's possible to eventually get the files after several attempts.
To try to work around the situation, I created a separate doc_src repository which is a copy of https://github.com/omegat-org/omegat/tree/master/doc_src/en, but this new repository isn't updated automatically. I enabled it as a source of documentation files to be translated in UK and PL OmegaT L10N repos, and there no such errors occur. But before this is applied to the rest of the L10N repos, it would be great to find a way to automate the update of https://github.com/OmegaT-L10N/doc_src from https://github.com/omegat-org/omegat/tree/master/doc_src/en. Any help in this regard will be most welcome.

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

Kos Ivantsov - 2021-03-30

I don't know if this bug belongs to this tracker, or should we have a separate tracker for localisation related issues, or what would be the best way to track such things?

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

Jean-Christophe Helary - 2021-03-30

You're right, maybe move it to the documentation tracker ?

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

Kos Ivantsov - 2021-03-30

Ticket moved from /p/omegat/bugs/1042/

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

Jean-Christophe Helary - 2021-03-30

It looks like Github Actions could be helpful.
It looks possible to generate a workflow where an update on the main doc_src branch triggers an update on the new doc_src repository that you created.
I don't have much time right now to investigate that at the moment though. Sorry for that.

https://docs.github.com/en/actions/learn-github-actions/introduction-to-github-actions

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

Jean-Christophe Helary - 2022-09-22

Is there any progress on this item?

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

Jean-Christophe Helary - 2022-10-13

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

Jean-Christophe Helary - 2022-10-13

If the workaround works now, let's fix that alter.

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

Jean-Christophe Helary - 2025-01-23

@kosivantsov do we still have the issue?

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

Log in to post a comment.