Curtis Ekstrom
As you may have noticed, I am joining the proofreading team here at OpenSuSE. I downloaded through SVN the "latest" pot files, and have checked out a couple of them, only to find that I'm not certain which rules to apply where. I read through the proofreading guide on capitalization, etc, but am unsure where I could find information in the strings themselves that would help me decide what rules to apply.
Often you can derive this information from a source file derived comment; those comments are marked with '#.' in the po files: #. progress step title #: src/users_finish.ycp:35 #, fuzzy msgid "Writing Users Configuration..." msgstr "" If some such comments are missingm, but desparately needed, we must ask the yast developers to provide them. Either via the yast ML or bugzilla. Maybe, this ML will also work because some developers already reading this list.
Also, as long as a new translation stays within the string limits, would a new rewording of the string be in order? One, and now that I wish to cite it, I can't find it, reads something like: "If you continue, the following repositories will be subscribed to:" This was later, if I'm not mistaken, corrected to: "If you continue, the following repositories will be subscribed:"
This seems awkward. Wouldn't something like: "If you continue, you will subscribe to the following repositories:" This is still within the character limit (isn't it?).
I'd say this would be fine. But better talk to the developers if in doubt. Because only a subset of all messages is available for proofing, it could happen that a similar text was approved previously, or a related help text might exist that the developer would like to modify accordingly. If wanted, I can grant you SVN commit rights. I'd also like to repeat a general reminder: If you edit help texts with embedded HTML-like markup, you must make sure that this markup stays unchanged. Example: "<p>This is an example. " "Some more text.</p>" Neither change the final "</p>" to "<p>" nor kill the white-space at the end of the first line before the double-quote. Also do not introduce dots where they do not belong... In the beginning, it would be great if you proofreaders would crosscheck your files to catch those syntax errors and, of course, for consistency. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-proofreading+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-proofreading+help@opensuse.org