This forum is a discussion about improving the "Flash Plugin - Keep it up to date and troubleshoot problems" article. If you'd like to participate, please register.

If you need help with Firefox, please ask a question.

Remaining template issue: line feeds

  • 2 Replies
  • Last reply by Tonnes
  1. Tonnes 63 posts
    Report Abuse

    Note that both the DisableHWAflash and closefirefox templates in this and the Adobe Flash plugin has crashed - Prevent it from happening again article do not really suffer from inserted spaces but inserted line feeds for some reason, like the optionspreferences template did. I’ve added another comment in bug 720228 hoping to get an explanation to why some (!) templates suffer from this, and if at least that part could be prevented or solved. Needless to say this keeps delivering some KB issues and annoyances even after fixing the optionspreferences issue. If it can’t be solved, we should take this into account.

    If it was up to me (though it may seem a bit picky), I’d prevent using templates in any part of a sentence for the time being. Also note that some locales (like ours) may not allow including words starting with a capital letter when they follow a colon (:) so sentences like "Close Firefox: [template content]" may cause trouble. Both issues would currently need us to use the template’s content instead to prevent a line jump and show proper grammar.

    Note that both the DisableHWAflash and closefirefox templates in this and the [[Adobe Flash plugin has crashed - Prevent it from happening again]] article do not really suffer from inserted spaces but inserted line feeds for some reason, like the optionspreferences template did. I’ve added another comment in [https://bugzilla.mozilla.org/show_bug.cgi?id=720228 bug 720228] hoping to get an explanation to why some (!) templates suffer from this, and if at least that part could be prevented or solved. Needless to say this keeps delivering some KB issues and annoyances even after fixing the optionspreferences issue. If it can’t be solved, we should take this into account. If it was up to me (though it may seem a bit picky), I’d prevent using templates in ''any'' part of a sentence for the time being. Also note that some locales (like ours) may not allow including words starting with a capital letter when they follow a colon (:) so sentences like "Close Firefox: [template content]" may cause trouble. Both issues would currently need us to use the template’s content instead to prevent a line jump and show proper grammar.
  2. AliceWyman 5146 posts
    Report Abuse

    I made a minor edit to the article ... and to the Adobe Flash plugin has crashed - Prevent it from happening again article. Could you review, to see if it helps at all?

    The line break before the Template:DisableHWAflash content is what I want since it's a numbered list. I added a <br> before [[T:DisableHWAflash]] anyway, just to make it clear that I want a line break.

    I removed the colon after "Close Firefox". I agree that the line break before the Template:closeFirefox content is a problem.

    Tonnes said

    Note that both the DisableHWAflash and closefirefox templates in this and the Adobe Flash plugin has crashed - Prevent it from happening again article do not really suffer from inserted spaces but inserted line feeds for some reason, <snip> Also note that some locales (like ours) may not allow including words starting with a capital letter when they follow a colon (:) so sentences like "Close Firefox: [template content]" may cause trouble.
    I made a minor edit to the article ... and to the [[Adobe Flash plugin has crashed - Prevent it from happening again]] article. Could you review, to see if it helps at all? The line break before the Template:DisableHWAflash content is what I want since it's a numbered list. I added a <nowiki><br></nowiki> before [[T:DisableHWAflash]] anyway, just to make it clear that I want a line break. I removed the colon after "Close Firefox". I agree that the line break before the Template:closeFirefox content is a problem. ''Tonnes [[#post-11298|said]]'' <blockquote> Note that both the DisableHWAflash and closefirefox templates in this and the [[Adobe Flash plugin has crashed - Prevent it from happening again]] article do not really suffer from inserted spaces but inserted line feeds for some reason, <snip> Also note that some locales (like ours) may not allow including words starting with a capital letter when they follow a colon (:) so sentences like "Close Firefox: [template content]" may cause trouble. </blockquote>
    Modified by AliceWyman on
  3. Tonnes 63 posts
    Report Abuse

    Clear… It doesn’t look like the 'br' makes any difference around the DisableHWAflash template - visually that is. As far as I know a single br is pretty much ignored unless used twice (resulting in a new line), or just once when following a line that contains an inline image at the end. (Now we’re at it: the latter is only true in localized previews, not en-US, so I sometimes add them just to get a right preview to match the en-US view. ;) )

    The closeFirefox template is what worries me more in this case. Even without the capitalization issue, the line feed just makes it look odd (like with optionsPreferences, not closeOptionsPreferences). I sure hope this can be fixed some day.

    I forgot to mention that these line feeds were actually inserted after optionsPreferences, but before closeFirefox. Either way, there must be an explanation, but the question is why some templates do and others do not suffer from it.

    Clear… It doesn’t look like the 'br' makes any difference around the DisableHWAflash template - visually that is. As far as I know a single br is pretty much ignored unless used twice (resulting in a new line), or just once when following a line that contains an inline image at the end. (Now we’re at it: the latter is only true in localized previews, not en-US, so I sometimes add them just to get a right preview to match the en-US view. ;) ) The closeFirefox template is what worries me more in this case. Even without the capitalization issue, the line feed just makes it look odd (like with optionsPreferences, not closeOptionsPreferences). I sure hope this can be fixed some day. I forgot to mention that these line feeds were actually inserted after optionsPreferences, but before closeFirefox. Either way, there must be an explanation, but the question is why some templates do and others do not suffer from it.