| 2016-02-21 22:48:36 |
Mingye Wang |
bug |
|
|
added bug |
| 2016-02-21 22:59:22 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces, consider using some grey/
blue/green/whatever '·' characters, but please make sure it does
not break alignment. (you definitely want to do so)
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
*[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces, consider using some grey/
blue/green/whatever '·' characters, but please make sure it does
not break alignment. (you definitely want to do so)
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
*[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
|
| 2016-02-21 23:01:03 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces, consider using some grey/
blue/green/whatever '·' characters, but please make sure it does
not break alignment. (you definitely want to do so)
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
*[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
*[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
|
| 2016-02-21 23:56:11 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
*[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
*[id^=msgset_][id*="_singular"],
*[id^=msgset_][id*="_plural"],
*[id^=msgset_][id*="_translation"],
label[id^=msgset_] /* suggestions */ {
font-family: monospace; /* console-ish monospace */
white-space: pre; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
|
| 2016-02-22 00:02:29 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
*[id^=msgset_][id*="_singular"],
*[id^=msgset_][id*="_plural"],
*[id^=msgset_][id*="_translation"],
label[id^=msgset_] /* suggestions */ {
font-family: monospace; /* console-ish monospace */
white-space: pre; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
div[id^=msgset_][id*="_singular"],
div[id^=msgset_][id*="_plural"],
label[id^=msgset_]:not(.no-translation),
textarea[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
|
| 2016-02-22 00:04:49 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
div[id^=msgset_][id*="_singular"],
div[id^=msgset_][id*="_plural"],
label[id^=msgset_]:not(.no-translation),
textarea[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
div[id^=msgset_][id*="_singular"],
div[id^=msgset_][id*="_plural"],
label[id^=msgset_]:not(.no-translation),
textarea[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre !important; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
|
| 2016-02-22 00:10:03 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
div[id^=msgset_][id*="_singular"],
div[id^=msgset_][id*="_plural"],
label[id^=msgset_]:not(.no-translation),
textarea[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre !important; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: none; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
div[id^=msgset_][id*="_singular"],
div[id^=msgset_][id*="_plural"],
label[id^=msgset_]:not(.no-translation),
textarea[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre !important; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: lightgrey; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
|
| 2016-02-22 00:14:52 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
div[id^=msgset_][id*="_singular"],
div[id^=msgset_][id*="_plural"],
label[id^=msgset_]:not(.no-translation),
textarea[id^=msgset] {
font-family: monospace; /* console-ish monospace */
white-space: pre !important; /* console-ish as-is whitespaces */
}
div[id^=msgset] > br {
display: none; /* kill the extra linebreaks */
}
.translation samp {
background: lightgrey; /* now kill the circle */
padding: 0; /* and its extra space */
}
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
<moved to https://userstyles.org/styles/124565/launchpad-monoist>
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
|
| 2016-02-22 00:55:24 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
<moved to https://userstyles.org/styles/124565/launchpad-monoist>
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
<moved to https://userstyles.org/styles/124565/launchpad-monoist>
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
|
| 2016-02-22 03:08:36 |
Dingyuan Wang |
bug |
|
|
added subscriber Dingyuan Wang |
| 2016-02-22 21:42:02 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
As a translator who cares about console-column alignment, I use the
following custom CSS rules on translations.launchpad.net to use monospace
fonts and make everything work as I wish:
<moved to https://userstyles.org/styles/124565/launchpad-monoist>
The image-circles always annoyed me since it breaks the alignment, and
rarely work well (as reported above). Since launchpad mainly deals with
program translations, why not just make the default fit better with
programs? |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<stylesheet for translators: https://userstyles.org/styles/124565>
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
|
| 2016-02-24 21:42:03 |
Mingye Wang |
summary |
spaces-as-circle-imgs in translations does not cover all whitespace cases |
successive whitespaces merged into just one by browser |
|
| 2016-02-24 21:42:28 |
Mingye Wang |
summary |
successive whitespaces merged into just one by browser |
successive whitespaces removed by browser, causing formatting problems |
|
| 2016-02-24 21:42:53 |
Mingye Wang |
summary |
successive whitespaces removed by browser, causing formatting problems |
successive whitespaces removed by browser, messes up CLI formatting |
|
| 2016-02-24 21:43:44 |
Mingye Wang |
affects |
launchpad |
ubuntu-translations |
|
| 2016-02-24 21:44:11 |
Mingye Wang |
bug task added |
|
launchpad |
|
| 2016-02-24 21:46:45 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<stylesheet for translators: https://userstyles.org/styles/124565>
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<stylesheet for translators: https://userstyles.org/styles/124565>
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
|
| 2016-02-24 21:47:23 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<stylesheet for translators: https://userstyles.org/styles/124565>
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<stylesheet for translators: https://userstyles.org/styles/124565>
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images (mis?)feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
|
| 2016-02-24 21:47:55 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<stylesheet for translators: https://userstyles.org/styles/124565>
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images (mis?)feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line. This is NOT
what projects owners who decided to use lp want to see.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<stylesheet for translators: https://userstyles.org/styles/124565>
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images (mis?)feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
|
| 2016-02-24 21:49:05 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line. This is NOT
what projects owners who decided to use lp want to see.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<stylesheet for translators: https://userstyles.org/styles/124565>
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images (mis?)feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line. This is NOT
what projects owners who decided to use lp want to see.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<hot-fix stylesheet for translators: https://userstyles.org/styles/124565>
(also with an example of failed help string as screenshot)
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images (mis?)feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
|
| 2016-02-24 21:51:24 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line. This is NOT
what projects owners who decided to use lp want to see.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<hot-fix stylesheet for translators: https://userstyles.org/styles/124565>
(also with an example of failed help string as screenshot)
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images (mis?)feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line. This is NOT
what projects owners who decided to use lp want to see.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<hot-fix stylesheet for translators: https://userstyles.org/styles/124565>
(also with an example of a failed help string as screenshot)
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images (mis?)feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
|
| 2016-02-24 21:52:33 |
Mingye Wang |
description |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line. This is NOT
what projects owners who decided to use lp want to see.
(There are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<hot-fix stylesheet for translators: https://userstyles.org/styles/124565>
(also with an example of a failed help string as screenshot)
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images (mis?)feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
In launchpad translations, when the original text starts with
whitespaces, launchpad will show something like:
En: ·--help-xxx foo bar…
···········The xxx help printed is formatted in…
[i] · represents a space character. Enter a space in the equivalent
position in the translation.
Unfortunately, non-leading/trailing spaces are still discarded by the
browser, since they are not transformed to the circles. Additionally,
this is not enabled for suggestions.
Translators are often seen confused by this, which makes projects like
aria2/zh_CN print ugly help messages on the command line. This is NOT
what projects owners who decided to use lp want to see.
(Imagine that there are supposed to be 2 spaces before 'foo'.)
Suggestion
----------
<hot-fix stylesheet for translators: https://userstyles.org/styles/124565>
(also with an example of a failed help string as screenshot)
1. Use monospace fonts for all translation strings
2. Use `white-space: pre;` rule to deal with whitespaces effortlessly.
3. Remove the spaces-as-images (mis?)feature. The newlines look fine to me
(so far). You might want to change the rest too:
a. Perhaps add an explicit end-of-string marker like a red paragraph-
sign or a red dollar-sign.
b. If you still want to emphasize spaces (you definitely want to),
consider using some grey/ blue/green/whatever '·' characters, but
please make sure it does not break alignment (i.e. one-col-wide).
c. There is a unicode 'Enter' character for newlines, but it doesn't
have wide support in fonts. Consider going Vim-ish and using a
yellow dollar-sign, or just keep using the enter image (the absense
of spaces-replacements makes it look lonely though.)
Rationale
---------
Column-level alignment has always been an important thing for translation,
especially for CLI apps, which are quite common in the FOSS word that lp
currently handles.
As a translator who does care about this, I believe the changes done in my
stylesheet should be applied globally, using a wiser implementation. The
circles almost never work well -- to me it's a mis-feature. |
|
| 2016-02-24 21:54:45 |
Mingye Wang |
summary |
successive whitespaces removed by browser, messes up CLI formatting |
successive whitespaces removed by browser, messes up CLI formatting by confusing translators |
|
| 2016-05-05 18:24:42 |
Mingye Wang |
launchpad: status |
New |
Confirmed |
|
| 2016-05-05 18:24:46 |
Mingye Wang |
bug task deleted |
ubuntu-translations |
|
|
