[yast-devel] Use check_ycp
Please, use check_ycp to find strings that are not marked ("_(...)) for translation and mark them accordingly. This is causing quite some bug entries... I'd also appreciate if you'd create a list of false positives. Otherwise you will see the same reports with every release... -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Nov 28 11:00 Karl Eichwalder wrote (shortened):
Please, use check_ycp to find strings that are not marked ("_(...)) for translation and mark them accordingly.
I use it all the time but it does not detect all cases where a string should be marked for translation, e.g. see https://bugzilla.novell.com/show_bug.cgi?id=448589#c4 Here check_ycp reports the source file to be o.k.: /usr/share/YaST2/data/devtools/bin/check_ycp src/driveradd.ycp OK. This is not meant as a complaint regarding check_ycp. It is only meant as information that a tool like check_ycp usually is not the ultimate final solution for such issues. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Freitag, 5. Dezember 2008, Johannes Meixner wrote:
I use it all the time but it does not detect all cases where a string should be marked for translation
Right. check_ycp is far from fool proof. That's what the documentation clearly says: file://usr/share/doc/packages/yast2-devtools/check_ycp/check_ycp_why.html "Even though using check_ycp is pretty straightforward, some background information is useful in order to understand what it does, its output and the limitations of this tool - in short, what you can expect it to do and why not to blindly rely on it. check_ycp is far from fool proof. In fact, it is pretty dumb. It just tries to parse YCP code ("try" is the operative word here!) and applies various checks for obvious programming errors. Some errors it will catch and report, many it will not. But we (i.e. the YaST2 core development team) decided we'd rather have a tool with limited capabilities than none at all." But then, it's much better than not having anything at all. The old rule holds true again: "Engage brain. Use tools. Check if what they do makes sense." ;-) CU -- Stefan Hundhammer <sh@suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Dienstag, 9. Dezember 2008, Stefan Hundhammer wrote:
That's what the documentation clearly says
BTW you did read the docs, didn't you? ;-} CU -- Stefan Hundhammer <sh@suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Johannes Meixner -
Karl Eichwalder -
Stefan Hundhammer