Results 1 to 2 of 2

Thread: Better translation QA

  1. #1
    Join Date
    Jul 2007
    Location
    Israel
    Beans
    22
    Distro
    Ubuntu 10.04 Lucid Lynx

    Better translation QA

    Typo reporting function

    Motivation:

    In Ubuntu the "Translate this Application" menu item under Help has become completely useless recently and I think we should consider an alternative while utilising gnome-screenshot and apport.

    Our goal is to enable an easy and quick way to report typos in apps, in the attached picture I described 5 simple steps to do so (this can also help detect visual glitches in apps or RTL problem, just a thought).

    Possible cons:
    The app in undetectable or the user decides to report a typo in a website while thinking this is a problem with the app (although highly plausible).
    There will be too many bug reports to handle, Launchpad changes are required for this to work.


    1st step:

    After spotting the typo the users can just click on Help -> Report a broken translation.
    This action will launch a series of actions starting with gnome-screenshot -a (that will capture a specific area of the screen) the next actions should somehow prepare the file and add save it to a temp folder (/tmp in our case, gnome-screenshot).


    2nd step:

    The user will be presented with a crosshair so he can select the desired area, (small floating message on top to bottom of the screen is optional, we have to make sure that the screenshot tool will not capture the message ☺)


    3rd step:

    The user will have an option to state exactly what seems wrong in his opinion and offer a correction. (in 2 distinct text boxes, 3rd box for comments is optional and I didn't add that in the mockup)
    Another option we can offer (does not appear in the mockup) is to add a small window on top that will show the user a thumbnail of the captured area.


    4th step:

    The following screen associates the typo report to the user using 3 options:
    The user will have the ability to log into his Launchpad account.
    The user does not have a Launchpad account and he decides this is the right time to sign up.
    The user have no interest in a Launchpad account, but he wishes to be informed of any further progress.
    The first option will show a username/password boxes for logging in.

    The second option will open the default browser with a registration pag, the two option are: sending the report at this step and not publishing it until the user sign up, if the user does not sign up the report is deleted within 24 hrs, the second option is adding a message at the end of the registration progress, at this point the user will dismiss the browser window and go back to the report window where he can sign in and continue.

    The third option will show a text box for entering an email address and a captcha (turing test) and a checkbox so the user will have the option to subscribe, we should consider whether its safe to let the users submit reports anonymously.

    This step involves the usage of apport (which I'm not familiar with), apport will collect the needed info about the system language etc. including the app name and version and will make sure that the report is good enough, apport also has the option of adding files to Lunchpad bug reports, this makes reporting a little more automatic (future thoughts: make this a GNOME native function using bug-buddy).


    5th step:

    The final screen, which shows a short greeting (your bug report has been submitted or otherwise not submitted in case there was an error and maybe even tells you what went wrong).
    The link to the bug in the middle.
    And finally a short message that thanks the user for taking the time to make the open source better.

    Reported as brainstorm idea 27054

    Kind regards,
    Yaron Shahrabani.
    Attached Images
    Attached Files
    Last edited by YaronSh; January 27th, 2011 at 09:29 AM. Reason: Adding brainstorm info

  2. #2
    Join Date
    Oct 2006
    Beans
    120
    Distro
    Kubuntu 10.10 Maverick Meerkat

    Re: Better translation QA

    First of all, I would like to say that this idea can really contribute to the translation process. The translation of an application requires from the translator to find the context of the string she/he is translating.
    By giving the user the option to report a typing error with a screenshot of the typo attached to the bug report, the translators can easily fix the typo, and with according to the string context.

    Just for the convenience of those who want to see the correct thumbnail, I attached all the steps in a nice and easy way:
    Attached Images

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
{"cc_re__cc_re__cc_by_sa_4_0": ["sing div for body_wrapper -->\r\n\r\n<div class=\"below_body\">\r\n<div id=\"footer_time\" class=\"shade footer_time\">All times are GMT +1. The time now is <span class=\"time\">07:00 PM</span>.</div>\r\n\r\n<div id=\"footer_copyright\" class=\"shade footer_copyright\">\r\n\t<!-- Do not remove this copyright notice -->\r\n\tvBulletin  2000 - 2016, Jelsoft Enterprises Ltd. Ubuntu Logo, Ubuntu and Canonical  Canonical Ltd. Tango Icons  Tango Desktop Project. \r\n<br>\r\nUser contributions on this site are licensed under the  <a href=\"https://creativecommons.org/licenses/by-sa/4.0/\">Creative Commons Attribution Share Alike 4.0 International License</a>. For details and our forum data attribution, retention and privacy policy, see <a href=\"http://ubuntuforums.org/showthread.php?t=2231107\">here</a> \r\n\r\n\t<!-- Do not remove this copyright notice -->\t\r\n</div>\r\n<div id=\"footer_morecopyright\" class=\"shade footer_morecopyright\">\r\n\t<!-- Do not remove cronimage or your scheduled tasks will cease to function -->\r\n\t\r\n\t<!-- Do not remove cronimage or your scheduled tasks will cease to f"], "copyright__copyright__copyright": ["to report a typing error with a screenshot of the typo attached to the bug report, the translators can easily fix the typo, and with according to the string context.\n\n    Just for the convenience of those who want to see the correct thumbnail, I attached all the steps in a nice and easy way:\n    Attached Images\n\nTags for this Thread\n\nBookmarks\n\nPosting Permissions\n\n  \u2022 You may not post new threads\n  \u2022 You may not post replies\n  \u2022 You may not post attachments\n  \u2022 You may not edit your posts\n  \u2022 \u00a0", "to report a typing error with a screenshot of the typo attached to the bug report, the translators can easily fix the typo, and with according to the string context.\n\n    Just for the convenience of those who want to see the correct thumbnail, I attached all the steps in a nice and easy way:\n    Attached Images\n\nTags for this Thread\n\nBookmarks\n\nPosting Permissions\n\n  \u2022 You may not post new threads\n  \u2022 You may not post replies\n  \u2022 You may not post attachments\n  \u2022 You may not edit your posts\n  \u2022 \u00a0", "to report a typing error with a screenshot of the typo attached to the bug report, the translators can easily fix the typo, and with according to the string context.\n\n    Just for the convenience of those who want to see the correct thumbnail, I attached all the steps in a nice and easy way:\n    Attached Images\n\nTags for this Thread\n\nBookmarks\n\nPosting Permissions\n\n  \u2022 You may not post new threads\n  \u2022 You may not post replies\n  \u2022 You may not post attachments\n  \u2022 You may not edit your posts\n  \u2022 \u00a0", "to report a typing error with a screenshot of the typo attached to the bug report, the translators can easily fix the typo, and with according to the string context.\n\n    Just for the convenience of those who want to see the correct thumbnail, I attached all the steps in a nice and easy way:\n    Attached Images\n\nTags for this Thread\n\nBookmarks\n\nPosting Permissions\n\n  \u2022 You may not post new threads\n  \u2022 You may not post replies\n  \u2022 You may not post attachments\n  \u2022 You may not edit your posts\n  \u2022 \u00a0", "to report a typing error with a screenshot of the typo attached to the bug report, the translators can easily fix the typo, and with according to the string context.\n\n    Just for the convenience of those who want to see the correct thumbnail, I attached all the steps in a nice and easy way:\n    Attached Images\n\nTags for this Thread\n\nBookmarks\n\nPosting Permissions\n\n  \u2022 You may not post new threads\n  \u2022 You may not post replies\n  \u2022 You may not post attachments\n  \u2022 You may not edit your posts\n  \u2022 \u00a0", "to report a typing error with a screenshot of the typo attached to the bug report, the translators can easily fix the typo, and with according to the string context.\n\n    Just for the convenience of those who want to see the correct thumbnail, I attached all the steps in a nice and easy way:\n    Attached Images\n\nTags for this Thread\n\nBookmarks\n\nPosting Permissions\n\n  \u2022 You may not post new threads\n  \u2022 You may not post replies\n  \u2022 You may not post attachments\n  \u2022 You may not edit your posts\n  \u2022 \u00a0"]}