Git Product home page Git Product logo

mrconfig's People

Contributors

cary-rowen avatar cleversn avatar cyrilleb79 avatar feerrenrut avatar florianionascu7 avatar jcsteh avatar josephsl avatar k-kolev1985 avatar lukaszgo1 avatar mhameed avatar mjsprojects avatar nardol avatar nvdaes avatar seanbudd avatar tiago-casal avatar zstanecic avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mrconfig's Issues

Replace addresses script with mailing list and tags

Consider whether we can replace the addresses script with a mailing list and tags.

When a language group needs to be notified, rather than directly emailing the translators, an email could be sent to a translations mailing list with a tag for the language. The benefit of this is that translators can more easily add / remove / update their email addresses.

SRT repo has become large

The SRT repo has become very large. Checkouts / updates take a long time, converting to Git (and retaining commits) would take days if done on my machine (I assume GitHub could do this import much faster).

There are many transient files, such as the diffs for t2t files that seem to build up.

Update the documentation

I have asked to have Speech History add-on included in translation framework (cf. jscholes/nvda-speech-history#23).

I realize that the add-ons need to be based on the add-on template to be compatible with the translation system. But it is not documented in the readme of this repo. More specifically:

  • The files sconstruct and buildVars.py are required since they are checked in 01_common.sh.
  • The command scons pot mergePot should be runable and successful (run in 01_addon2svn.sh)
  • Is there a need/a check that scons generate a .nvda-addon file?

Also the readme does not indicate which file is used to generate the work for translators. There is the .po file generated by scons pot mergepot. But there is also the English webpage file: srt/website/addons/addonname.mdwn.

@jscholes, if you agree to work on jscholes/nvda-speech-history#23, you may write your feedback here if something else is not documented.

Cc @nvdaes, @feerrenrut

Create issue template to request add-ons registration

This may make easy to request add-ons registration, which can be a repeatitive process and requires standardized fields.
Issue forms (for now in beta stage) maybe easier that the markdown template.
I have created a sample for testing on my .github repo, used to store issue templates and other guidelines for all my projects on GitHub by default. Let me know if I should create a PR.

Improve update of webpages on add-ons website

Currently, every person with access to Assembla repo can make changes to the add-ons website. This means that add-ons can be posted using link skipping addonFiles repo. Also, when an add-on is updated on the website, documentation needs to be updated separately, with an elapsed time since addonFile pull request are merged by @nvaccess until someone, probably add-on authors, can update the documentation on the website to be translated into different languages.
I think that we may provide a link to documentation, and Assembla repo shouldn't be touched to send it to avoid changing links skipping addonFiles.

Issue with Turkish translation

@feerrenrut, @seanbudd, could you please have a look at this issue before the end of translation freeze?

Context

Issue reported by Turkish translator in this thread.

Issue

Turkish nvda.po file does not seem to be updated in SVN to NVDA direction.

In SVN repo, tr\nvda.po has been fully translated in Turkish (2667 / 2667 messages translated) since the following revision:

Revision: 69532
Author: umutkorkmaz
Date: samedi 27 août 2022 14:07:55
Message:
TR: Updated.nvda.po. Added Three new strings translated.

However, in NVDA's beta branch, the last commit for source\locale\tr\LC_MESSAGES\nvda.po is:

commit b3410e60f87b6db586c92676aa8fd283f63f4375
Author: NVDA translation automation <[email protected]>
Date:   Fri May 6 00:01:56 2022 +0000
    L10n updates for: tr
    From translation svn revision: 67469

Notifications from SRT repo not received anymore

I do not receive any notification regarding activities on the screenreadertranslations repo anymore.
This has been so for 3-4 weeks.

I have asked on the translators mailing list and the issue seems the same for at least another person.

I used to receive notifications for modifications in the 'fr' folder (French) as well as in the 'website' folder.

@feerrenrut, could you have a look at it?
Many thanks!

Fix the translations system for add-ons

Exbi server is sending notifications about mr commands or folders that cannot be created.
This should be fixed so people can manage translations for add-ons. Alternatively, request people to manage them independently without using a central system.
Thanks.

Access8Math translations are not updated in nvdaaddons repo

In the nvdaaddons/Access8Math repo, the last commit of the stable branch is:

commit d4562e9b5fbee671a2b250b2687fae587c8acbdb (tag: v3.1)
Author: Tseng Woody <[email protected]>
Date:   Tue Sep 21 17:38:24 2021 +0800

    *       In the general settings, user can select Math Player as the speech/braille/interact source only if user`s system have Math Player installed.

However, on SVN SRT repo, there are more recent translations, e.g.:

Revision: 65209
Author: CyrilleB79
Date: mardi 9 novembre 2021 12:14:32
Message:
fr: Access8Math interface - Translation finished; some checks still to be done.

----
Modified : /fr/add-ons/Access8Math/nvda.po

The stable branch should have been updated with new translations (usually every week).

@feerrenrut could you have a look at it?

Cc @tsengwoody, author of the add-on.

Missing documentation in two of my add-ons

Hi,
After updating translations for Proxy and UpdateChannel, I see that the doc folder doesn't exist on the stable branch. I am receiving only interface po files. I'd like to include all translated documentation before releasing versions compatible with NVDA 2022.1.
I'm not sure wether this problem is caused by mrconfig or something not properly configured on these repositories, so I decided to open an issue here.
Thanks in advance.
Regards.

Use data-driven approach to addon translations

Currently the tasks for translating addons comes from crontab.automatic. They are the same for every addon. To make it easier to update the list of addons that require translations, use a data driven script to do the same action for a list of addons.

Synchronization issue for Outlook Extended, Windows Magnifier and maybe other add-ons

Hello

I have an issue regarding Outlook Extended add-on in the translation workflow.
The add-on is already part of the workflow for a long time. And SVN seems to be updated regularly when something is pushed in the stable branch of nvdaaddons/outlookExtended repo.

However, in the other direction, the work of translators in SVN is not merged back in the stable branch of nvdaaddons/outlookExtended repo.

A concrete example is the following commit:

Revision: 61945
Author: CyrilleB79
Date: vendredi 4 juin 2021 17:15:03
Message:
fr: Updated Outlook extended translation.
----
Modified : /fr/add-ons/outlookExtended/nvda.po

This SVN commit dates from the 4th of June but its content does not yet appear in the stable branch of nvdaaddons/outlookExtended.

The last commit coming from SVN in the stable branch of nvdaaddons/outlookExtended is the following:

commit 1ea892c0c734fde41f88abcb736adb54e501987a
Author: NVDA translation automation <[email protected]>
Date:   Fri May 14 15:06:08 2021 +0000
    l10n updates

Separate settings files from the SRT repo

Currently settings files can be updated by any translator without the agreement of others.

Consider whether part or all of these settings files should be kept in a separate repository and updated via a PR.

We will need to fix scripts that use them, eg path updates.

Last commits in SRT are not shown on the website

Since yesterday at least, new commits in the SRT repo do not trigger the corresponding update on the add-on community website.

Here is a precise example for Access8Math add-on documentation on the website:

The last SRT commit for the French translation of this documentation is:

Revision: 62371
Author: michelsuch
Date: mercredi 23 juin 2021 11:24:39
Message:
fr - website - addons/access8math.fr.po - access8math updated
----
Modified : /website/addons/access8math.fr.po

Making an SVN diff on this commit with the previous wone, we can clearly see that the initial description of the add-on (after download link / compatibility statement) has been translated in French.

However, on the website, the initial description (among other) is still in English. Here is the French page:
https://addons.nvda-project.org/addons/access8math.fr.html

There are other pages (if not all) that have not been updated recently on the website.

Cc @MichelSuch who is the person who has updated specifically this documentation.

Register pcKbBrl add-on

Please, register this add-on to be translated with the translations system.

Documentation about adding new add-ons to the old system, when I had access to NV Access server, is available at

https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/MakeAddonsTranslatable

Thanks

Add-on files: changes to add-on files repo isn't syncing with add-ons website

Hi all,

Perhaps due to changes made to where scripts are stored:

Background

One minute past every hour, automatic.crontab found in add-on files repo will attempt to synchronize changes from the repo to community add-ons website. This is essential for add-on releases to happen and is a vital lifeline for Add-on Updater as it will check a Json-formatted list of add-ons to check for version differences.

Problem:

Perhaps due to changes made to script locations, synchronization is not happening. This means if the member of the add-ons community releases an add-on and the add-on files repo (specifically, get.php) is modified to update the download links, changes will not be applied. For example, if an add-on author releases a development version of an add-on and a change is made to add-on files repo, the new version will not even show up on community add-ons website - users trying to download the development version of this add-on will download old releases instead.

Impact

This issue impacts overlal community add-ons release pipeline. People wishing to (or needing to) release new add-on versions (especially stable versions with critical bug fixes or localization updates) will not be able to tell users that the new version is indeed the version they have just released. It also breaks Add-on Updater in that it becomes impossible to compare what's out there versus what's currently installed on a system.

Solutions

In the short-term, NVDA add-ons community can be notified to hold off on releasing new add-on releases. The near-term (and ideal) solution is resolving it from scripts side so the add-on release pipeline can be reestablished. In the long-term, a complete overhaul of add-on release pipeline will be needed, one that doesn't use repo synchronization as currently employed.

Thanks.

Update `SRT/global.t2tconf` automatically

In the screenreader translations SVN repo, the global.t2tconf file is updated for each release with the new release version and updated copyright years if needed. The part of the file which is updated are the following lines:

% Language neutral defines
% We need to do this one as PostProc so it gets converted for the title.
%!PostProc: NVDA_VERSION 2022.1-dev
%!PreProc: NVDA_URL https://github.com/nvaccess/nvda/
%!PreProc: NVDA_COPYRIGHT_YEARS 2006-2021

Today it seems that this updates are done manually by @josephsl (a.k.a. nvdakor in SVN) for each release. Moreover, I do not know if it is documented somewhere; @josephsl is it?

It would be interesting to have it automated. In this repo, it could by handled in the nvda2svn processing:

  • update last copyright year as soon as current year does not match anymore
  • update NVDA version as per NVDA version file

There are many ways to solve this issue:

  1. Implement automatic update and document it
  2. Only document the current process but do not automate anything in mrconfig; automation may be implemented in the add-on store when it becomes a reality
  3. Do nothing if documentation of the current process already exists

Use master branch instead of stable to receive add-on translations

Hello, in case add-on authors need to send pull request to a repo to submit translations, please consider to use just master branch instead of stable, which maybe an extra step not needed.
I'd like to mention @abdel792, since yesterday he created a PR requesting an add-on (pre-release) on the add-ons website, and perhaps he's interested in provide feedback about this proposal. I think that the review process for add-ons is not in place for now, but for example if the created PR was reviewed and merged into master, in the current system we need to create an extra branch named stable to receive translations.
For reference, his PR is at

nvdaaddons/mp3DirectCut#1

Thanks

Use pot or xliff format for userguide

For the user guide and other long form content translators are expected to maintain a translated version of the file, keeping the structure compatible and using diff files to guide where changes must be made.

Instead, if we can adjust the system to use pot or xliff format for the userguide, then translators can work entirely withing poedit.

This will likely help to improve the repository size issue (#7) going forward.

Register Character Information in translation system

Could you please register Character Information in the translation system? This add-on is already present on the official add-on community website.

GitHub repo URL:
https://github.com/CyrilleB79/charInfo

The files to be synchronized are the interface file (.po) as well as the documentation (.md), as for other add-ons.

Note: The translation of localized files specific to this add-on (found in addon/globalPlugins/charinfo/locale/xx) should not be localized via this automatic translation framework. Instead, localization of these files should be done directly via PR's in the charInfo add-on's repo or contacting the add-on author (me).

Not all add-ons get updated by crontab

@seanbudd

I was looking at the mrconfig file automatic.crontab.
There are many entries like:

#x  3 for addons starting with c
00  3 * * fri $AddonTranslationUpdate clipContentsDesigner

...

#x  4 for addons starting with d

...

04  4 * * fri $AddonTranslationUpdate dropbox
08  4 * * fri $AddonTranslationUpdate directLink

However, there are no entries for my add-ons speechLogger and numpadNavMode.

There is also no entry for soundSplitter, but that one may not be registered, as I only took it over recently, and don't know its full status yet.

Is this file not used any more? If it is used, why are some registered add-ons missing?
If some of mine are missing, what other ones might be missing?

Some files not generated by the translation system for Georgian language (ka)

Issue

The translation framework scripts do not create any file in the following folders of the SVN screenreadertranslations (SRT) repo:

  • ka\changes-newRevisions
  • ka\symbols-newRevisions
  • ka\userGuide-newRevisions

Context

Issue discussed initially on the translation mailing-list, where Georgian translators need the symbol revisions.

For now the Georgian translators want to translate/update the interface (nvda.po) and the symbols.dic file. The character description is already translated. In the future, they may translate the user guide and maybe the change log.

Thus for now, the updates in the symbols-newRevisions folder are needed.

Additional questions

  • Can the translation framework scripts work correctly even if changes.t2t and userGuide.t2t are not present in SVN? If not, this should be documented in the translation wikis.
  • When the translators want to translate the userGuide, it would be better if the userGuide-newRevisions folder already contains files; this way they can take the file from the last revision and just translate it.

Note

I could have given a try at looking to the scripts and adding the missing files (newRevisions, t2t) as well as modifying the settings file to see if it solves the problem. But I have to wait for a week before the scripts are triggered again.

So I prefer NVAccess to do it, since they can check the logs of the scripts and trigger them to check immediately the result.

@feerrenrut, could you have a look please?

Access8Math - Documentation update broken in svn2addon direction

For Access8Math, the website documentation has been updated for French and Spanish (maybe also other languages).
However it has not been updated in the stable branch of nvdaaddons/Access8Math repo.
I have not looked at other add-ons to see if they suffer from the same issue.

@feerrenrut could you have a look at it please when you're back? Thanks.

Cc @tsengwoody, author of Access8Math add-on.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.