[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: view-fuzzy beta version ready
From: |
Ali Servet Donmez |
Subject: |
Re: view-fuzzy beta version ready |
Date: |
Mon, 24 May 2010 17:33:32 +0200 |
Is it in www-el repo?
On Thu, 2010-05-20 at 06:12 +0300, George Zarkadas wrote:
> Hi all,
>
> view-fuzzy is more or less complete; the most useful way to use it is
> to run (switches in [...] are optional, use --help to find their
> meaning) this command in a fuzzy po file:
>
> view-fuzzy -m -o <output-file> [-g8] <input-file>
>
> to strip out all but the changed lines and then open the file with an
> editor that shows comments too, such as emacs. <output-file> can be
> same as <input-file> if you want to ovveride the source file in-place.
>
> I am currently working on doing this automatically at the merging of
> repositories. But this is still *experimental* and not for those that
> are not willing to have their repositories restored frequently; my
> first attempt erased all my po files (this has been fixed, btw) and
> had to manually revert to previous revisions. I now tag my cvs with
> status-<iso date> tags before each test run.
>
> The other stuff inside __tools__ is more 'esoteric' and not worth to
> deal with it yet.
>
> best regards
> George Zarkadas
>
> 2010/5/16 Ali Servet Donmez <address@hidden>
> Hi everyone,
>
> first of all please excuse me all for very very late reply on
> this
> subject.
>
> I really would love to get into and discover better what
> various things
> under "www-el/__tools__" does (especially "view-fuzzy"), but
> that's way
> long code that I couldn't possibly afford atm.
>
> Could please somebody sum up what's the current status here?
>
> is there anything new in GnuMakefile.team which is useful for
> translation teams?
>
> Thanks in advance.
>
> Best regards,
>
> On Thu, 2010-03-25 at 01:04 +0200, George Zarkadas wrote:
>
>
> > The script is in beta now, and have already passed all po
> files in
> > philosophy (and gnu) subtrees with reasonable speed and no
> obvious at
> > first sight errors.
> >
> > Available at:
> >
>
> http://cvs.savannah.gnu.org/viewvc/www-el/__tools__/view-fuzzy?revision=1.12&root=www-el&view=markup
> >
> > All wdiff options that make sense are supported as well as
> custom
> > wdiff executables. Common options can be set by env vars;
> see --help
> > for details.
> >
> > As I see it, there are two main uses:
> >
> > 1. View quickly all changes in fuzzy records in a set of
> files in a
> > terminal window; for example:
> >
> > [wdiff style]: view-fuzzy -ap /some-path/www/gnu/po/*.xx.po
> > [with color ]: view-fuzzy -h c
> -a /some-path/www/gnu/po/*.xx.po
> >
> > 2. Merge diff with the initial po file to produce a file
> that can be
> > edited with emacs or any po-editor that can display
> comments; so that
> > highlighted changes are visible while editing the file. For
> example:
> >
> > view-fuzzy -m -o dest-file src-file
> > or even:
> > view-fuzzy -m -o src-file src-file
> >
> > In addition, when we are certain that no spurious errors may
> result in
> > data loss of the original file's msgids and msgstrs, then I
> believe it
> > will be relatively easy to incorporate in the team's
> GNUmakefile a
> > repository update mode that will automatically merge the
> diffs in
> > local team's po files. What's your opinion about this?
> >
> > regards
> > G. Zarkadas
>
> --
>
> Ali Servet Donmez <address@hidden>
>
>
--
Ali Servet Donmez <address@hidden>
signature.asc
Description: This is a digitally signed message part