Edgewall Software

Changes between Version 28 and Version 29 of TracL10N/Transifex


Ignore:
Timestamp:
Aug 4, 2018, 9:20:36 AM (8 months ago)
Author:
figaro
Comment:

Added link to referencing page

Legend:

Unmodified
Added
Removed
Modified
  • TracL10N/Transifex

    v28 v29  
    447447Note that you can also do `make diff` for a more up-to-the-point output: `make diff vc=git` if you're working in a git checkout.
    448448
    449 ==== Do something with those changes
    450 
    451 You can do whatever you wish, for example commit the changes to the source with an appropriate log message, **but**, please!, before that:
     449==== Publish your changes
     450
     451You can commit the changes to the source with an appropriate log message, **but**, please!, before that:
    452452 - remember to check your catalog with `make check`, here: `make check-fr`
    453453 - remember to check your catalog by compiling it, here: `make compile-fr`
    454454
    455 Once you're done, make sure you **push back** the changes to Transifex. See the other example below.
     455Once you are done, make sure you **push back** the changes to Transifex. See the other example below.
    456456
    457457=== Pushing local modifications of the catalogs to Transifex #push-example
    458458
    459 After committing changes to the message catalog, it's a good idea to push those changes to Transifex so that other contributors can see these changes.
     459After committing changes to the message catalog, it is a good idea to push those changes to Transifex so that other contributors can see these changes.
    460460
    461461Even if you just pulled changes from Transifex (coming from the other example above), you most certainly did local adaptations like the removal of the spurious metadata changes, or small fixes, then you should also push those changes back to Transifex the same way, as Transifex **won't** pick up the changes made to the translated catalogs from the repository. It will do that for the catalog templates though, so the latter are always up-to-date.
     
    511511
    512512On the other hand, the big benefit is that all the links from t.e.o to Tx won't need to be updated after each minor release. The only updates needed will be when introducing a new major release, for example for Trac 1.2.
     513
     514See also: [wiki:TracL10N]