Christian Boos wrote: > When you work on the i18n side, you also try to validate your changes to > see how well they work out in a translation. > You have then this work sequence:
I wasn't aware of the complexity of the workflow when doing translations. I thought that the functionality was largely independent of the language, and was therefore completed and tested first, and only then would the translations be updated (possibly combining the translations of several functionalities). Skipping whole changesets only containing translations is easy and quick, but unfortunately not scrolling past translations to find the functionality. Thanks for the clarification. > But the ideal solution would be to have the uninteresting changes (the > line number noise) simply /hidden/ from the display, which will also > solves the problem of the noisy changeset. And that's probably doable by > implementing pluggable diff renderers (#53) and a special .pot/.po > renderer which simply remove the line noise chunks from the diff output... That would be a good option, yes. I was going to suggest per-file folding in the changeset view, and to fold selected files (e.g. those matching a glob) by default. But that wouldn't work when viewing the timeline as an RSS feed in Thunderbird, as JavaScript is disabled there. -- Remy
signature.asc
Description: OpenPGP digital signature
