|
Bugzilla – Full Text Bug Listing |
| Summary: | Typos in yast2 partitioner | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Gerald Pfeifer <gp> |
| Component: | YaST2 | Assignee: | Thomas Fehr <fehr> |
| Status: | RESOLVED FIXED | QA Contact: | Karl Eichwalder <ke> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aj, ke |
| Version: | Alpha 0plus | ||
| Target Milestone: | Alpha 5 | ||
| Hardware: | All | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Thanks for the report. I'm going to change it as follows (note, the superfluous space is also in the English string). Shane, will you update your translation memory accordingly, please? #. error popup text #: storage/src/inst_custom_part.ycp:1250 msgid "" "The value for the partition end is invalid.\n" "\n" "Enter the end cylinder number (such as 77), an offset (like +122),\n" "or the size of the partition (for example, +100M or 1.8GB )\n" msgstr "" "Der Wert für das Partitionsende ist ungültig.\n" "\n" "Geben Sie die Nummer des Endzylinders (z.B. 77), einen Offset\n" "(z.B. +122) oder die Größe der Partition (z.B. +100M oder 1.8GB) ein.\n" Shane, please answer comment #2! We have not used our own translation memories for this project. The translation as currently implemented is in the set of po files handed off to the vendor an dthat is the translation that will be in SLE10 SP1. yes, for SLE10 SP1. But this string is mostly ok in SLE10 and so the bug relates to openSUSE 10.2 and later only. I thought those messages are save in your translation memory, and so it is necessary to fix the messages in the memory. Sorry for insisting for further information, Shane. As far as I know, we will re-use the translations from SLE10 SP1 in openSUSE10.3. ok, now I see. So let's check again during the 10.3 cycle. Thomas, these help texts as available in the yast translation SVN also lack full stops (instead there is one paren too much): #. helptext for popup create partition line 6 of 6 #: storage/src/include/custom_part_helptexts.ycp:160 msgid "<p>It is also possible to specify the size of the partition directly (e.g ., +100M or +20000K))</p>" msgstr "" #. helptext for popup create extended partition line #: storage/src/include/custom_part_helptexts.ycp:170 msgid "" "<p>Enter the starting cylinder number of the partition.\n" "After that, either specify an ending cylinder number or an offset from the firs t cylinder (e.g., +66).\n" "It is also possible to specify the size of the partition directly (e.g., +2G, + 100M, or +20000K)</p>\n" msgstr "" Here the reporter wants you to remove a space before a closing paren: #. error popup text #: storage/src/inst_custom_part.ycp:1250 msgid "" "The value for the partition end is invalid.\n" "\n" "Enter the end cylinder number (such as 77), an offset (like +122),\n" "or the size of the partition (for example, +100M or 1.8GB )\n" msgstr "" [The German translation in our SVN trunk now is basically fine.] Thanks, fixed the mentioned typos in ycp code. |
One error messages reads "Fehler Der Wert für das Partitionsende ist ungültig. Geben Sie die Nummer des Endzylinder (z.B. 77), ein Offset (wie +122) oder die Größe der Partition (z.B. +100M oder 1,8GB ) ein" There are several problems here: 1. "1,8GB" should read "1.8GB", because YaST does not support the former. This is a real bug, where the documentation example fails to work. 2. There is an extraneous blank before the last closing parenthesis. 3. The second sentence lacks a full stop. 4. It should read "einen Offset" instead of "ein Offset".