|
Bugzilla – Full Text Bug Listing |
| Summary: | Wrong translation in YasT scanner module | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Johannes Meixner <jsmeix> |
| Component: | YaST2 | Assignee: | Johannes Meixner <jsmeix> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Johannes Meixner
2006-01-25 15:09:48 UTC
Actually, the English here is not very good. This string wasn't in the last pot file. What exactly are you trying to say? In my scanner.pot it is - but perhaps it is not in yours because you get only changed strings? I want to say that "Firewall is not currently running and/or it would (or will?) not be started automatically." but this text is too long. Perhaps "Firewall not running or would not be started automatically." would be more clear? How about "Firewall not running and should not be started" 1. Doesn't "should" mean that it is not recommended to do something but if you insist, you could do it nevertheless? I mean that the Firewall will not be started automatically in the future (e.g. after a reebot or after a runlevel change or whatever). I am not talking about whether it is recommended or not to start the Firewall now or later or whenever. 2. There must be a "or" not an "and" because there are two issues "not running" and/or "will not be started" which can be true or false independent of each other (i.e. a logical "or"). Why has it suddenly become my bug now? I am no native English speaker! I cannot provide perfect English text! Here a correct German text: "Firewall nicht aktiv oder wird nicht automatisch gestartet." Please provide the right English text. "should not" as in "not supposed to be" it sounds like the case is that the firewall currently is not running and its configuration is that it shouldn't be started in the current circumstances. you could also try to work out using the standard firewall stuff instead of making up new ways of interacting with the firewall. It is your bug because I can't fix the source code. I can tell you here what to write, but I can't fix the source. I don't understand why this string wasn't in my last pot file. "firewall currently is not running and its configuration is that it shouldn't be started in the current circumstances" That's it! Please provide a nice English string for this. I take the bug but set it as NEEDINFO to you. Regarding "using the standard firewall stuff": If "the standard firewall stuff" could do what I need, I would of course use it (I was in contact with Lukas). Enhancing "the standard firewall stuff" very much only to get support for the special scanner case was at least problematic (and probably impossible in the 10.1 time-frame). Details:
This special case could happen for example when the Firewall services
are not "innserved" (i.e. Firewall would not start during booting
or when runleven changes) but the user has started the Firewall
manually ("rcSuSEfirewall2 start").
This indicates that the user has a special selfmade Firewall setup
and if there is a special selfmade Firewall setup I don't want
to cause conflicts with my simple Firewall settings in the scanner
module (i.e. in this case the user cannot do Firewall settings
in the scanner module - he must use the Firewall module).
"Firewall is not and should not be running" If you fix the English, I expect the German will get fixed next translation. Sorry, I need again info. In comment #7 I overlooked the "and". Actually the meaning is "firewall currently is not running and/or its configuration is that it shouldn't be started in the current circumstances" Is "Firewall is not or should not be running" or even "Firewall is not and/or should not be running" possible, see comment #4 2. If you change it to or, it makes it apply to either case. You could have a firewall not running that ought to be running or a firewall running that shouldn't be. If that is what you mean, change it to or. If you mean that the firewall both isn't running and isn't supposed to be running, leave and. Many thanks for your explanations. "have a firewall not running that ought to be running or a firewall running that shouldn't be" is exactly what I mean. This shows that there is something strange with the Firewall and then I will not change this special Firewall setup. Therefore I use now "Firewall is not or should not be running." (The original text hat a '.' at the end). New yast2-scanner package submitted to STABLE. It should not end in a . These texts are status information and not meant to have end punctuation. I have removed them from all the similar strings in the last pot file. Fixed. Now without '.' at the end in STABLE. |