I felt I'd mess it up by sending this to i18n through NNTP and design through e-mail... Let's see if sending to both by NNTP will fix that.
On 12/11/2013 06:41 PM, Matthew Flaschen wrote:
That's almost certainly not possible in every language. It could work as a suggestion, though ("If possible...").
Jared said that it doesn't even have to be treated as a sentence, can be something like "Editing: [article name]".
However, it might be better to wrap the title (language aside, it could provide better usability for some scenarios, e.g. if you lock your phone when editing, then come back to it and want to see what page you're on).
I'm not sure if I understand the example use case. Also, this solution has all sorts of other problems. Let's say we try to do it in PHP, we don't even know the browser window width. Let's say we do it in JavaScript, we know the browser window width, but we don't know how many characters will fit in a single line... For those reasons I'd rather stick with text-overflow: ellipsis in CSS.
"Juliusz Gonera" wrote:
[...] On 12/11/2013 06:41 PM, Matthew Flaschen wrote:
That's almost certainly not possible in every language. It could work as a suggestion, though ("If possible...").
Jared said that it doesn't even have to be treated as a sentence, can be something like "Editing: [article name]".
However, it might be better to wrap the title (language aside, it could provide better usability for some scenarios, e.g. if you lock your phone when editing, then come back to it and want to see what page you're on).
I'm not sure if I understand the example use case. Also, this solution has all sorts of other problems. Let's say we try to do it in PHP, we don't even know the browser window width. Let's say we do it in JavaScript, we know the browser window width, but we don't know how many characters will fit in a single line... For those reasons I'd rather stick with text-overflow: ellipsis in CSS.
The solution is to have three DIVs nested into another DIV or, alternatively, a table of three columns. * Line wrapping is forbidden in each of them. * The central one employs CSS text-overflow: ellipsis and shows the full title on mouseover. * The outer two have i18n'ed strings like "Editing:" or "is being edited" which most often means that either the left or the right column is empty, depending on the language, shrinking to zero width.
Purodha
On 12/12/2013 04:12 AM, P. Blissenbach wrote:
The solution is to have three DIVs nested into another DIV or, alternatively, a table of three columns.
- Line wrapping is forbidden in each of them.
- The central one employs CSS text-overflow: ellipsis and shows the full title on mouseover.
- The outer two have i18n'ed strings like "Editing:" or "is being edited" which most often means that either the left or the right column is empty, depending on the language, shrinking to zero width.
I'm not sure if I understand. Does it mean that a translator would always leave one of the messages empty? That sounds a bit complicated for the translators.
On 12/11/2013 10:31 PM, Juliusz Gonera wrote:
However, it might be better to wrap the title (language aside, it could provide better usability for some scenarios, e.g. if you lock your phone when editing, then come back to it and want to see what page you're on).
I'm not sure if I understand the example use case.
You open your browser back up and you want to see the full article name you're editing.
Let's say we do it in JavaScript, we know the browser window width, but we don't know how many characters will fit in a single line... For those reasons I'd rather stick with text-overflow: ellipsis in CSS.
I'm suggesting using the browser's normal wrapping algorithm (the same one a normal paragraph or div uses), rather than truncating or splitting the string based on an explicit calculation.
Matt Flaschen
The reason for not wrapping is this is a fixed header element and we want to reduce the amount of space it takes up on screen.
if you forget the entire name of the article you can scroll up to the top of the page.
*Jared Zimmerman * \ Director of User Experience \ Wikimedia Foundation
M : +1 415 609 4043 | : @JaredZimmermanhttps://twitter.com/JaredZimmerman
On Thu, Dec 12, 2013 at 5:12 PM, Matthew Flaschen mflaschen@wikimedia.orgwrote:
On 12/11/2013 10:31 PM, Juliusz Gonera wrote:
However, it might be better to wrap the title (language aside, it could
provide better usability for some scenarios, e.g. if you lock your phone when editing, then come back to it and want to see what page you're on).
I'm not sure if I understand the example use case.
You open your browser back up and you want to see the full article name you're editing.
Let's say we do it in JavaScript, we know the browser window width, but
we don't know how many characters will fit in a single line... For those reasons I'd rather stick with text-overflow: ellipsis in CSS.
I'm suggesting using the browser's normal wrapping algorithm (the same one a normal paragraph or div uses), rather than truncating or splitting the string based on an explicit calculation.
Matt Flaschen
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
mediawiki-i18n@lists.wikimedia.org