1
0
mirror of https://github.com/rkd77/elinks.git synced 2024-12-04 14:46:47 -05:00

Renamed check-accelerator-contexts.pl to check-accelerator-conflicts.pl.

This commit is contained in:
Kalle Olavi Niemitalo 2006-01-14 16:50:45 +02:00 committed by Kalle Olavi Niemitalo
parent 71bf9716c8
commit 6f44394dfa
4 changed files with 16 additions and 16 deletions

View File

@ -94,7 +94,7 @@ check-po:
@-$(foreach lang,$(basename $(if $(strip $(PO)),$(PO),$(GMOFILES))), \ @-$(foreach lang,$(basename $(if $(strip $(PO)),$(PO),$(GMOFILES))), \
echo -n "$(lang): "; \ echo -n "$(lang): "; \
$(GMSGFMT) --check --check-accelerators="~" --verbose --statistics -o /dev/null $(srcdir)$(lang).po; \ $(GMSGFMT) --check --check-accelerators="~" --verbose --statistics -o /dev/null $(srcdir)$(lang).po; \
$(PERL) -I"$(srcdir)perl" $(srcdir)perl/check-accelerator-contexts.pl $(srcdir)$(lang).po; \ $(PERL) -I"$(srcdir)perl" $(srcdir)perl/check-accelerator-conflicts.pl $(srcdir)$(lang).po; \
) )
### Installation and distribution ### Installation and distribution

View File

@ -33,9 +33,9 @@ When a translator edits a *.po file, she does not alter the
"accelerator_context" comments. "accelerator_context" comments.
When a translator runs "make check-po" in the elinks/po directory, When a translator runs "make check-po" in the elinks/po directory,
check-accelerator-contexts.pl reads the "accelerator_context" comments check-accelerator-conflicts.pl reads the "accelerator_context"
in the *.po file, checks the accelerators in the translations, and comments in the *.po file, checks the accelerators in the
displays any conflicts it finds. translations, and displays any conflicts it finds.
FILES FILES
@ -47,7 +47,7 @@ gather-accelerator-contexts.pl reads elinks.pot and the source files
to which it refers, and writes a new elinks.pot with information from to which it refers, and writes a new elinks.pot with information from
"gettext_accelerator_context" comments. "gettext_accelerator_context" comments.
check-accelerator-contexts.pl reads just one *.po file and scans it check-accelerator-conflicts.pl reads just one *.po file and scans it
for conflicts. It does not access the C source files. for conflicts. It does not access the C source files.
Locale/PO.pm was originally imported from Locale-PO-0.16 on CPAN, and Locale/PO.pm was originally imported from Locale-PO-0.16 on CPAN, and

View File

@ -11,7 +11,7 @@ my $VERSION = "1.0";
sub show_version sub show_version
{ {
print "check-accelerator-contexts.pl $VERSION\n"; print "check-accelerator-conflicts.pl $VERSION\n";
pod2usage({-verbose => 99, -sections => "COPYRIGHT AND LICENSE", pod2usage({-verbose => 99, -sections => "COPYRIGHT AND LICENSE",
-exitval => 0}); -exitval => 0});
} }
@ -71,12 +71,12 @@ __END__
=head1 NAME =head1 NAME
check-accelerator-contexts.pl - Scan a PO file for conflicting check-accelerator-conflicts.pl - Scan a PO file for conflicting
accelerator keys. accelerator keys.
=head1 SYNOPSIS =head1 SYNOPSIS
B<check-accelerator-contexts.pl> F<I<language>.po> [...] B<check-accelerator-conflicts.pl> F<I<language>.po> [...]
=head1 ARGUMENTS =head1 ARGUMENTS
@ -92,21 +92,21 @@ If the special comments are missing, no conflicts will be found.
=head1 DESCRIPTION =head1 DESCRIPTION
B<check-accelerator-contexts.pl> is part of a framework that detects B<check-accelerator-conflicts.pl> is part of a framework that detects
conflicting accelerator keys in Gettext PO files. A conflict is when conflicting accelerator keys in Gettext PO files. A conflict is when
two items in the same menu or two buttons in the same dialog box use two items in the same menu or two buttons in the same dialog box use
the same accelerator key. the same accelerator key.
The PO file format does not normally include any information on which The PO file format does not normally include any information on which
strings will be used in the same menu or dialog box. strings will be used in the same menu or dialog box.
B<check-accelerator-contexts.pl> can only be used on PO files to which B<check-accelerator-conflicts.pl> can only be used on PO files to which
this information has been added with B<gather-accelerator-contexts.pl> this information has been added with B<gather-accelerator-contexts.pl>
or merged with B<msgmerge>. or merged with B<msgmerge>.
B<check-accelerator-contexts.pl> reads the F<I<language>.po> file B<check-accelerator-conflicts.pl> reads the F<I<language>.po> file
named on the command line and reports any conflicts to standard error. named on the command line and reports any conflicts to standard error.
B<check-accelerator-contexts.pl> does not access the source files to B<check-accelerator-conflicts.pl> does not access the source files to
which F<I<language>.po> refers. Thus, it does not matter if the line which F<I<language>.po> refers. Thus, it does not matter if the line
numbers in "#:" lines are out of date. numbers in "#:" lines are out of date.
@ -120,7 +120,7 @@ numbers in "#:" lines are out of date.
=head1 BUGS =head1 BUGS
B<check-accelerator-contexts.pl> reports the same conflict multiple B<check-accelerator-conflicts.pl> reports the same conflict multiple
times if it occurs in multiple contexts. times if it occurs in multiple contexts.
Jonas Fonseca suggested the script could propose accelerators that are Jonas Fonseca suggested the script could propose accelerators that are
@ -135,7 +135,7 @@ The warning messages should include line numbers, so that users of
Emacs could conveniently edit the conflicting part of the PO file. Emacs could conveniently edit the conflicting part of the PO file.
This is not feasible with the current version of Locale::PO. This is not feasible with the current version of Locale::PO.
When B<check-accelerator-contexts.pl> includes C<msgstr> strings in When B<check-accelerator-conflicts.pl> includes C<msgstr> strings in
warnings, it should transcode them from the charset of the PO file to warnings, it should transcode them from the charset of the PO file to
the one specified by the user's locale. the one specified by the user's locale.

View File

@ -175,7 +175,7 @@ the same accelerator key.
The PO file format does not normally include any information on which The PO file format does not normally include any information on which
strings will be used in the same menu or dialog box. strings will be used in the same menu or dialog box.
B<gather-accelerator-contexts.pl> adds this information in the form of B<gather-accelerator-contexts.pl> adds this information in the form of
"accelerator_context" comments, which B<check-accelerator-contexts.pl> "accelerator_context" comments, which B<check-accelerator-conflicts.pl>
then parses in order to detect the conflicts. then parses in order to detect the conflicts.
B<gather-accelerator-contexts.pl> first reads the F<I<program>.pot> B<gather-accelerator-contexts.pl> first reads the F<I<program>.pot>
@ -323,4 +323,4 @@ DEALINGS IN THE SOFTWARE.
=head1 SEE ALSO =head1 SEE ALSO
L<check-accelerator-contexts.pl>, C<xgettext(1)>, C<msgmerge(1)> L<check-accelerator-conflicts.pl>, C<xgettext(1)>, C<msgmerge(1)>