|Summary:||RFE: User story: As a translator I would like to be able to run the Validation Checks on a whole book so that I can find errors even in existing translations.|
|Product:||[Retired] Zanata||Reporter:||Hedda Peters <hpeters>|
|Status:||CLOSED DUPLICATE||QA Contact:||Ding-Yi Chen <dchen>|
|Version:||unspecified||CC:||damason, mkim, sflaniga, zanata-bugs|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-02-05 00:07:20 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||846314|
Description Hedda Peters 2012-03-28 22:19:48 UTC
User story: As a translator I would like to be able to run the Validation Checks on a whole book so that I can find errors even in existing translations. It just occured to me when updating an already partly translated document. By chance, I opened the editor for an existing translation and was surprised to find Validation Warnings.
Comment 1 Runa Bhattacharjee 2012-07-30 13:20:13 UTC
Request for technical evaluation.
Comment 2 Michelle Kim 2012-11-13 01:03:13 UTC
Is this bug somewhat related to this bug https://bugzilla.redhat.com/show_bug.cgi?id=846314 ? If so, should we merge these two into one bug? I believe implenting the 846314 (error view on the project list) will enable translators to check if there is a error on already translated document?
Comment 3 David Mason 2012-11-13 01:25:51 UTC
This bug is related to, but also distinct from https://bugzilla.redhat.com/show_bug.cgi?id=846314 This bug does not necessarily require the validation state to be persisted - validations could be run on-demand for a list of documents (with some caching to prevent excessive processing).The other bug would require persistence of the validation state of every project, and would require this state to be constantly kept up-to-date.