A 2014-10-10 21:26, Adrian Chaves Fernandez escrigué: > “The first thing you should do if you want to get more involved is to > introduce yourself on the mailing list […]” — > http://wiki.apertium.org/wiki/Contributing > > > My name is Adrián Chaves Fernández, although in free software projects > I > usually go by the nickname Gallaecio, and I’m going to start looking > into > using Apertium for a little project, which might lead me to contribute > to the > en-gl pair or to Apertium itself.
Great! :D > That’s it, now I’m going to explain what my project consists on and why > I > started. You might want to stop reading at this point. > > > So, last weekend I attended the first “Iberian Meeting of Translators > of Free > Software into Minoritized Languages”¹, where translators of free > software into > Aragonese, Asturian, Basque, Catalan, and Galician met to discuss our > common > problems and join forces towards solving them. We discussed several > topics, > and during one of those discussions, someone suggested the idea of > using > Apertium to translate documentation. We would encourage anyone using Apertium to get in contact with us if they need any help. :) > Using automated translation software to translate a product is regarded > as a > sin by every single translator that I have had the pleasure to meet, > including > myself, however everyone agrees as well that translating documentation > is a > real PITA. Using Apertium to translate documentation and manually > reviewing > the resulting translation would: > * Make translating documentation easier, as we would no longer need to > translate the documentation, but only review the automated translation. > * Allow us to detect issues in Apertium, giving us the opportunities to > fix > them, thus contributing to a great free software project. > > Hence, I’ve started working on using the following stack to translate > the KDE > documentation into Galician: > > * apertium-po-l10n (https://github.com/rory/apertium-po-l10n) > * Apertium > * en-gl pair > > As I find issues, I will fix them on either of those three layers, and > I might > add a new layer with some custom Python scripts if I need something for > this > project that does not fit in either of the previous layers. This is a fantastic idea. Would you like commit access so you can commit directly to the repository ? If so, let us know your SourceForge username. Fran ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
