Translation User eXperience Next Generation (TUX ng)
Перейти к файлу
Christoph Wille 8b0e5650be Optional indexes 2015-03-02 17:02:51 +01:00
setup Optional indexes 2015-03-02 17:02:51 +01:00
src Fixes #7 2014-08-17 21:29:43 +02:00
.gitignore Initial commit 2014-05-19 00:40:56 -07:00
LICENSE Initial commit 2014-05-19 00:40:56 -07:00
README.md YouTube videos 2014-07-29 11:23:09 +02:00

README.md

Resource-First Translations

RFT is the next generation Translation User eXperience built upon the insights of the SharpDevelop project. It has the following goals:

  • Code-First: Developers live in the IDE and work directly with resource files. Source control is the source of truth for resources.
  • Multi-Branch: Translations come and go with features being added, modified or removed. Translators should never duplicate work.
  • Multi-File: Complex software doesn't ship with a single resource file only. Slice your application into modules and still get the benefits of translating only once.
  • Sync: Automatically get the latest resource file checkins to the translators, and the finished translations to the developers or the build servers.

Live demo: http://rftdemo.azurewebsites.net/

Translator credentials: translator, translator
Administrator credentials: admin, administrator

Certain operations are disallowed in the demo (eg creating new users, resetting a password)

Videos / Screencasts

Administration Area Translators demo

Documentation

Please see the wiki

License

MIT

Written by Andreas Lillich (frontend) and Christoph Wille (backend). The specification was co-written by Daniel Grunwald, Siegfried Pammer and Christoph Wille.

Changelog

July 28th, 2014

  • RFT is in production use for SharpDevelop

May 19th, go-live on Github

  • A first non-production test version of RFT

April 6th, 2014

Andreas joins in to create the SPA frontend applications

Feb 25th, 2014

Start coding as a proof of concept to see if this can be pulled off

SharpDevelop Developer Days 2013

Daniel, Siegfried and Christoph sat down and created a specification

Years ago...

We had been talking about replacing the existing application for ages.