Closed Bug 1058665 Opened 10 years ago Closed 5 years ago

KB editor window should display line numbers

Categories

(support.mozilla.org :: Knowledge Base Software, task, P3)

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: underpass_bugzilla, Unassigned)

References

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux i686; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release)
Build ID: 20140822024446

Steps to reproduce:

In long articles (such as "Keyboard shortcuts") we need the line numbers even when the diff is not enabled, because it is nearly impossible to understand which paragraph you are localizing.

https://support.mozilla.org/it/kb/Scorciatoie%20da%20tastiera%20di%20Firefox/edit

The best option would be the possibility to toggle line numbers. If it's not possible, then they should be added as for the diff visualization.

Thanks.
Reporter - are you saying you need the line numbers in the approved English version?
Flags: needinfo?(simone.lando)
I would be better to have the line numbers in the approved version when viewing it in the left panel of the page (I'll try to upload a picture). Currently we have two ways to display it: one is the plain text and one is the diff. 

The diff has indeed the line numbers, but the plain text has not.
Flags: needinfo?(simone.lando)
Michal, your input?
Flags: needinfo?(mdziewonski)
I think it's a very nice feature to have, so if it's an easy copy/paste job between editor and source views, let's do it! (anecdotal information: I usually copy the text into an external editor, such as Sublime Text)

To expand on this (thwack me on the head and tell me to open a new bug, if necessary), would it be possible to unite or lock scrolling for both panels? This way when you scroll up/down, both content panels follow.
Flags: needinfo?(feer56)
Flags: needinfo?(mdziewonski)
Sumodev would need to comment.  I am not sure.
Flags: needinfo?(feer56)
This will be listed as a "feature" request in our backlog doc: https://docs.google.com/a/mozilla.com/spreadsheets/d/1BGULIZZxFv54EcVoBo1IGPzsjlOsuUB-0CnaU_oJjjQ/edit?pli=1#gid=0 (potentially a good "starter" bug for a dev contributor)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Hello, I ask you to please add this feature since articles like "Keyboard shortcuts" are becoming nearly impossible to handle. Thanks.
We'll try to get as part of the 25% in the next sprint, Simone. It all depends how easy it is to turn on.
Cleaning up old bug before the migration. This may become a feature request for the new platform.
Assignee: nobody → mdziewonski
Status: NEW → ASSIGNED
Flags: needinfo?(mdziewonski)
+NI from Madalina for handling & prioritization.

Changing from "Localization" to "Knowledge Base Software", as it would be useful for all locales and not only during the l10n process.

In the "Rich Text" or "HTML" views, the editor window for Knowledge Base articles (and any additional content views, for example requests here https://bugzilla.mozilla.org/show_bug.cgi?id=1345865) should display line numbers for each separate line of the content displayed.
Component: Localization → Knowledge Base Software
Flags: needinfo?(mdziewonski) → needinfo?(mana)
Summary: Needed line numbers even when the diff is not enabled → [feature request] KB editor window should display line numbers
Component: Knowledge Base Software → Feature request
Product: support.mozilla.org → support.mozilla.org - Lithium
Summary: [feature request] KB editor window should display line numbers → KB editor window should display line numbers
Assignee: mdziewonski → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(mana)
Moving back to the original product and component since we aren't moving back to Lithium.
Component: Feature request → Localization
Product: support.mozilla.org - Lithium → support.mozilla.org
Sorry, is there any chance to see this bug solved anyway?
Thanks.
(In reply to Underpass from comment #14)
> Sorry, is there any chance to see this bug solved anyway?
> Thanks.

I'll let vesper or another admin reply but from what I read in https://support.mozilla.org/en-US/forums/contributors/712503 developer resources are very limited.
(In reply to vesper from comment #11)

> Changing from "Localization" to "Knowledge Base Software", as it would be
> useful for all locales and not only during the l10n process. 

I missed that.  I'm changing the component to "Knowledge Base Software".
Component: Localization → Knowledge Base Software
needs developer time which we are trying to figure out so P3
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: