[nvda-addons] Fwd: [nvda-translations] Attempt to minimize translation for addon pages

  • From: Bernd Dorer <bernd_dorer@xxxxxxxx>
  • To: nvda-addons@xxxxxxxxxxxxx
  • Date: Sun, 18 Jan 2015 14:56:27 +0100

Hi Addon authors and reviewers

for all of you not reading on translators list I think you should read
the following mail. from mesar. At the moment we have some addons with a
newer release and an older dev release on the addons page. For example
there is focusHighlight-2.1 and focusHighlight-1.1dev. We should handle
this somehow with reducing translators time for translating dev messages.

Thanks
Bernd

-------- Weitergeleitete Nachricht --------
Betreff:        [nvda-translations] Attempt to minimize translation for addon
pages
Datum:  Sun, 18 Jan 2015 13:04:22 +0000
Von:    Mesar Hameed <mesar.hameed@xxxxxxxxx>
Antwort an:     nvda-translations@xxxxxxxxxxxxx
An:     nvda-translations@xxxxxxxxxxxxx



Hi Team,

Bernd and I have been thinking about how to minimize the amount of
changed strings that a translator has to deal with for the addons
website as an addon goes through development.
At the moment as a new dev version is made available/documented, you
will get changed/new messages, even if those strings are not final, so
this is unnecessary effort for translators.

The possible workable solution is to have 1 page with the addon name,
description and stable features, all translatable.
Then include a non-translatable page, which has the development and
download sections.
The advantage is:
* Minimal changes between the readme in the addon repo and in the
  website. The differences can be scripted.
* addons will stop having download stable/development links in the
* documentation that you get when the addon is installed.
* translators only get new strings when they have been reviewed/spell
  checked, so hopefully will not require retranslation too often.
* each addon only has 1 location, instead of sometimes finding it under
  both development and stable sections of the addon website.

Disadvantages:
* Users might ask why is the latest development strings not translated.
* Download section and links are in English.


I have recycled the clip contents designer addon messages to show you
how it would look like.

the contents are in:
website/test/ccd.mdwn (english original)
website/test/ccd.langCode.po (your translation)
website/test/ccd_dev.mdwn (contains development/unchecked english
strings and download section)

You can see the matching page at:
http://addons.nvda-project.org/test/ccd

Please let us know if you have any conserns or objections.

thanks,
----------------------------------------------------------------
NVDA translations:

Team documentation: http://community.nvda-project.org/wiki/Translate
To send a message to the list: nvda-translations@xxxxxxxxxxxxx
list archive: //www.freelists.org/archive/nvda-translations/
To change your list settings/unsubscribe: 
//www.freelists.org/list/nvda-translations
To contact list moderators: nvda-translations-moderators@xxxxxxxxxxxxx



Attachment: signature.asc
Description: OpenPGP digital signature

Other related posts:

  • » [nvda-addons] Fwd: [nvda-translations] Attempt to minimize translation for addon pages - Bernd Dorer