[opensuse-translation] Possible typo in snapper.xx.po
Linenumbers are taken from snapper.de.po: 336:"<p><b><big>Snapshots Configuration</big></b><p>\n" 353:"<p><b><big>Snapshot Overview</big></b><p>\n" 370:"<p><b><big>Snapshot Overview</big></b><p>\n" The second <p> should probably be a </p>, at least that's why the syntax would imply. Btw. where should one report such typos? I've tried the bugzilla recently, but the feedback was not that great (I wask asked for y2logs repeatedly, even though I stated the line in the sourcecode(not the .po file) where the typo was and what the typo was :| ). Regards, Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-01 01:11, Michael Skiba wrote:
Linenumbers are taken from snapper.de.po: 336:"<p><b><big>Snapshots Configuration</big></b><p>\n" 353:"<p><b><big>Snapshot Overview</big></b><p>\n" 370:"<p><b><big>Snapshot Overview</big></b><p>\n"
The second <p> should probably be a </p>, at least that's why the syntax would imply.
Btw. where should one report such typos? I've tried the bugzilla recently, but the feedback was not that great (I wask asked for y2logs repeatedly, even though I stated the line in the sourcecode(not the .po file) where the typo was and what the typo was :| ).
I'm confused. :-? Are you a translator, or just a user reporting an error in the translation? :-) If you are a translator, you don't need to report, the .po files are your responsibility, yours and your team. The translator for that file does it, and you handle it internally. If you are the translator, but you report an error in the msgid (english original text), then you would not report against the .po file, but against the .pot file. In this case the course of action is not clear to me. You might report in Bugzilla a string error against lcn:snapper.pot, and refuse the stupidity of requesting yast logs. Pardon my language. It is absurd to ask for yast logs for everything. Tell them that they are absolutely empty, see if they can digest it. Or that you don't have factory installed :-/ Or you might report here and hope that Karl or somebody else can handle it. Seeing the above absurdity, it is the only thing you can do. :-( If you are not a translator, but you report a translation error, you would use bugzilla, using the component "translation". But in this case, it is not a translation error, so see the above paragraph re bugzilla. Or, seeing that you found the .po file, there is an email there for the translator or his team. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk93leQACgkQIvFNjefEBxrvKQCeIWNqgmJnoLmMMrChRxvcAgLB YIoAoK+PVT88UOFPeetrj8166nwAFv9t =gRiM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Sonntag, 1. April 2012, 01:40:20 schrieb Carlos E. R.:
I'm confused. :-? I'm tired Carlos *_*
If you are the translator, but you report an error in the msgid (english original text), then you would not report against the .po file, but against the .pot file. Indeed I'am and have been since quite a while :-) You are correct of course and I should go to sleep, but before the relevant lines from snapper.pot:
Line 291: #: src/helps.ycp:45 msgid "" "<p><b><big>Snapshots Configuration</big></b><p>\n" Line 302: #: src/helps.ycp:54 msgid "" "<p><b><big>Snapshot Overview</big></b><p>\n" Line 314: #: src/helps.ycp:64 msgid "" "<p><b><big>Snapshot Overview</big></b><p>\n"
In this case the course of action is not clear to me. [...] Or you might report here and hope that Karl or somebody else can handle it. Seeing the above absurdity, it is the only thing you can do. :-(
Same here, would be good if we could get an official answer I know that Karl (he's the i18n contact afterall) is reading this list and I think Stephan is too. But bugzilla might be more convinient for them ... Regards, Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-01 02:11, Michael Skiba wrote:
Am Sonntag, 1. April 2012, 01:40:20 schrieb Carlos E. R.:
I'm confused. :-? I'm tired Carlos *_*
It happens :-) I'm a late sleeper. I stay till I notice that I'm sleepy. :-)
Indeed I'am and have been since quite a while :-)
Yes, I noticed just after sending that email O:-)
You are correct of course and I should go to sleep, but before the relevant lines from snapper.pot:
Line 291: #: src/helps.ycp:45 msgid "" "<p><b><big>Snapshots Configuration</big></b><p>\n"
The problem is that I don't find them. Ah! I got it, there are two snapper files, one in yast, another in lcn. Yes, indeed, there is a bug.
In this case the course of action is not clear to me. [...] Or you might report here and hope that Karl or somebody else can handle it. Seeing the above absurdity, it is the only thing you can do. :-(
Same here, would be good if we could get an official answer I know that Karl (he's the i18n contact afterall) is reading this list and I think Stephan is too. But bugzilla might be more convinient for them ...
Let's wait till they say what to do. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk93n5sACgkQIvFNjefEBxphmQCfXGoiUsgLGILwLltUNCkYPJci OV8AoJcWvV5XJuimrAafdBgo5OmbXZdT =74Qf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 01/04/12 01:11, Michael Skiba wrote:
Btw. where should one report such typos? I've tried the bugzilla recently, but the feedback was not that great (I wask asked for y2logs repeatedly, even though I stated the line in the sourcecode(not the .po file) where the typo was and what the typo was :| ).
Usually I report such typos via bugzilla, providing the whole item (comments, source line, msgid) from the POT file and a proposal for the fix, as Carlos said. To avoid a request for y2logs, once I was told to add a line like: "y2logs are not needed as the bug is already apparent in the cited source code" Best, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Andrea Turrini <andrea.turrini@gmail.com> writes:
Usually I report such typos via bugzilla, providing the whole item (comments, source line, msgid) from the POT file and a proposal for the fix, as Carlos said.
To avoid a request for y2logs, once I was told to add a line like:
"y2logs are not needed as the bug is already apparent in the cited source code"
This sounds perfect to me :) Using bugzilla is always the best (if your time permits). If you think trouble is to be expected, CC: me. If nothing helps, either mail to the yast devel ML or to this translation ML--I'm sure we can find a solution in the end. Sometimes, weird things just happen. Simple misunderstandings, vacation, wrong assignments, changing responsibilities, etc. ;) -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Montag, 2. April 2012, 14:51:51 schrieb Karl Eichwalder:
This sounds perfect to me :) Using bugzilla is always the best (if your time permits). If you think trouble is to be expected, CC: me. If nothing helps, either mail to the yast devel ML or to this translation ML--I'm sure we can find a solution in the end. Sure, in the end, but why go through troubles if there is an easy way :D
Ok so basicly you're saying that we should report typos in bugzilla (makes sense, since it minimizes the risk of getting lost also everything is in one place). Is there anything we can do to make the process more streamline? What's with the component tag in bugzilla? YaST-Modules all belong in YaST I guess, but where do I file webyast/lcn under? (btw. what does lcn actually stand for?) Regards, Michael
Michael Skiba <mailinglist@michael-skiba.de> writes:
Ok so basicly you're saying that we should report typos in bugzilla (makes sense, since it minimizes the risk of getting lost also everything is in one place).
Yes, that's it.
Is there anything we can do to make the process more streamline?
Sending patches to the maintainers would probably also ok. But then, you would be on your own to figure out all the needed background info (who is the maintainer, where is the repo, etc.).
What's with the component tag in bugzilla? YaST-Modules all belong in YaST I guess, but where do I file webyast/lcn under? (btw. what does lcn actually stand for?)
Yes, for yast typos, please use the yast component. For the rest, use what might fit best and as fallback "other" or "translation". If you know the real maintainer, assign it to him. BTW, you can assign yast typo bugs directly to yast2-maintainers@suse.de (but only yast typo bugs, please). lcn stands for "localization" (not invented by me). -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
participants (5)
-
Andrea Turrini -
Carlos E. R. -
Carlos E. R. -
Karl Eichwalder -
Michael Skiba