Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Commenting #227

Open
GoogleCodeExporter opened this issue Mar 13, 2015 · 5 comments
Open

Enable Commenting #227

GoogleCodeExporter opened this issue Mar 13, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link
Collaborator

Please allow users to leave comments on their translations. 

For example translators can let a comment when they are in doubt and approvers 
can leave a comment when they review the translation. 

Commenting helps further collaboration, older version of narro had commenting 
feature. 

Original issue reported on code.google.com by hitmana...@gmail.com on 26 Oct 2011 at 2:05

@GoogleCodeExporter
Copy link
Collaborator Author

Click the help icon brings the comment form. Tried to keep the translate form 
as clean as possible. Ideas are welcome.

Original comment by alex...@gmail.com on 27 Oct 2011 at 6:13

@GoogleCodeExporter
Copy link
Collaborator Author

I didn't know that. 

A comment icon would be a good idea. You can also have count of comments next 
to it (viz the blogger comment icon style http://playingwithsid.blogspot.com )

Original comment by hitmana...@gmail.com on 27 Oct 2011 at 7:41

@GoogleCodeExporter
Copy link
Collaborator Author

Any extra button comes with the cost of a greater page loading time. That's why 
initially only the original text and translation is shown.

When you click the help button, you get the translation list and comment box.

Not sure if this is the best idea. It depends what do people want to actually 
comment. Is it to ask a question before they translate, comment an existing 
suggestion or both.

If I'd implement the review tab, then we could have different views of the 
current translation page and we might have different options activated by 
default.

Suggestions are welcomed.

Original comment by alex...@gmail.com on 27 Oct 2011 at 4:34

@GoogleCodeExporter
Copy link
Collaborator Author

I understand the need to keep the pages lightweight. However commenting fosters 
collaboration. Also it is another avenue for translators to communicate and 
peer review. 

Putting comment under help makes it harder to find. Second it means that users 
comment to get support. 

Some of testcases for comments are: 

* User leaves a comment when they find a invalid string 'a' '.' 
* User leaves a comment when he is unable to find the right word for the 
translations
* User leaves a comment to ask others to review
* Users leave comment when suggesting a better translation 
* Project Approver leaves a comment on why they made changes to the 
translation. As a learning process. 

Review tab had been great help for localization sprints. Strong encourage you 
implement it in Narro 2.x.

This talk would give you more idea on sprint format: Translate -> Review -> 
Test pattern of localization.

http://www.slideshare.net/playingwithsid/mozilla-khmer-l10n-presentation-barcamp
-pnnom-penh-4



Original comment by hitmana...@gmail.com on 28 Oct 2011 at 1:36

@GoogleCodeExporter
Copy link
Collaborator Author

So currently commenting is enabled like this:

In the translate tab, there's a link % translations % comments. Clicking it 
opens the translations list and the comment box where you can add a comment and 
see other comments.

In the review tab, the same situation except the translations are shown by 
default.


Is there anything missing or wrong ?

Original comment by alex...@gmail.com on 19 Nov 2011 at 4:43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant