[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#514755: po4a: enhance --previous with wdiff script


On Wed, Feb 11, 2009 at 12:43:10AM +0100, Nicolas François wrote:
> Hello,
> On Wed, Feb 11, 2009 at 01:04:50AM +0900, Osamu Aoki wrote:
> [talking about Javier's script which allows to see differences based on
> the strings added by --previous]
> > I think this should be inclided as an example helper script or even integrated
> > into additional --previous functionality.  wdiff makes good sense in many
> > cases!  
> I would prefer this feature to be included in PO editors.
> I also know that editors are working on supporting the previous string
> (lokalize does it, it is planned for virtaal, see also
> http://techbase.kde.org/Localization/Tools/Pology/PO_Embedded_Diffing)

That is certainly clean and nice approach but old furt like me are stack
with using vim to edit po files :-)  Please do not forget us.

> Also, it is not directly related to po4a.

Well it is directly related to data generated and used by po4a.

> On the other hand, if this script is useful for others, I can package it
> (either in po4a, po-debconf, or translate-toolkit)

This is not po-debconf specific.  

This may be part of translate-toolkit if this can be integrated into it.
(but I think this is not something you ship as normal Debian command and
more appropriate as user script)

This is po4a specific and appropriate as example script for user. 
> Other opinions from debian-i18n?

If any of you have some vim MACRO or emacs mode script, that is
something as good to have in example.  Having example script for
po4a like package is quite common and Debian Policy defines as follows:

Debian Policy: http://www.debian.org/doc/debian-policy/ch-docs.html#s12.6
12.6 Examples

Any examples (configurations, source files, whatever), should be
installed in a directory /usr/share/doc/package/examples. These files
should not be referenced by any program: they're there for the benefit
of the system administrator and users as documentation only.
Architecture-specific example files should be installed in a directory
/usr/lib/package/examples with symbolic links to them from
/usr/share/doc/package/examples, or the latter directory itself may be a
symbolic link to the former.

If the purpose of a package is to provide examples, then the example
files may be installed into /usr/share/doc/package. 

Reply to: