Thank you for feedback.

06-05-04, Mikolaj Machowski <[EMAIL PROTECTED]> napisał(a):
Dnia czwartek, 4 maja 2006 01:16, Wojciech Pilorz napisał:
> I have just finished a perl script to test menu translation
> completeness; It reads menu.vim, attempts to extract menu definitions
> and compare with menu definitions in specified files from runtime/lang.
>
> synmenu.vim is not read, so for the languages for which syntax menu
> entries are translated there will be a lot of false 'Extra
> translation' messages;
>
> Please be aware that the script is a quick hack; it does NOT
> understand vim scripts syntax and semantics; Just a couple of regexes
> and hashed thrown together.
> So treat the messages with a good grain of salt.
> Anyway, I hope translation maintainers might find it useful - it
> detects a number of not translated menu entries, as well as some
> spelling problems

You could rule out false positives as menu -separators-.
Actually I tried to do that; there should be no messages about
translated files compared to menu.vim.
The message from reading menu.vim ('WARN: ignored duplicated key')
still is there - it should be safely ignored.


Also format of messages is strange, info is split in two parts. How to
write compiler for that? I've wrote that one:
I tried to keep line length reasonable, and did not think at all about
automatic processing of the output; shame on me!

I can of course modify the script to use requested message format by default;
Any proposals?



if exists("current_compiler")
  finish
endif
let current_compiler = "menutrans"

let s:cpo_save = &cpo
set cpo-=C

setlocal mp=chk_menu_tran.pl\ %
setlocal errorformat=
                        \%-GINFO%.%#,
                        \%m\ at\ %f:%l%.%#,
                        \%m\ in\ file\ %f:%l,
                        \%m\ in\ %f:%l

let &cpo = s:cpo_save
unlet s:cpo_save

m.


Best regards,

Wojtek

Reply via email to