Bug 884347
Summary: | Users are not warned when using an unsupported directory layout for 'file' project type | ||
---|---|---|---|
Product: | [Retired] Zanata | Reporter: | Ding-Yi Chen <dchen> |
Component: | Usability | Assignee: | David Mason <damason> |
Status: | CLOSED UPSTREAM | QA Contact: | Zanata-QA Mailling List <zanata-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | development | CC: | damason, dchen, mkim, sflaniga, zanata-bugs |
Target Milestone: | --- | Keywords: | Reopened, screened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 864280 | Environment: | |
Last Closed: | 2015-07-29 02:51:07 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 864277, 864280 | ||
Bug Blocks: |
Description
Ding-Yi Chen
2012-12-06 01:56:08 UTC
Is our new mapping rule going to fix this issue? Can you please confirm if this still a issue? If not, can we close the bug? thanks (In reply to Michelle Kim from comment #1) > Is our new mapping rule going to fix this issue? Can you please confirm if > this still a issue? If not, can we close the bug? thanks No, Tested with zanata-server-3.6.0, zanata-maven-plugin-3.4.2 Project freemind: It has ./FM_Key_Mappings_Quick_Guide_hr.odt ./FM_Key_Mappings_Quick_Guide_fr.odt ./FM_Key_Mappings_Quick_Guide_et.odt ./FM_Key_Mappings_Quick_Guide_ru.odt ./FM_Key_Mappings_Quick_Guide_it.odt ./FM_Key_Mappings_Quick_Guide.odt The mapping rules. <rules> <rule pattern="FM_Key_Mappings_Quick_Guide.odt">{filename}_{locale_with_underscore}.odt</rule> </rules> Push with: mvn zanata:push -Dzanata.pushType=both -Dzanata.disableSSLCert FM_Key_Mappings_Quick_Guide_fr.odt is now push as both fr translation of FM_Key_Mappings_Quick_Guide.odt, as well as source document by its own. Current zanata can avoid this by providing src-dir, trans-dir, includes and excludes, but it needs quite a lot of trial and error. Most of the project expected the document translation (except podir and publican) like {filename}-{locale_with_underscore}. so it is better to make it as default. Actually zanata can The mapping rule can fix the issue, a This is not a bug, it is a documentation-reading issue. Read this attentively:
> raw project type assumes that all translations are in sibling directories of the source directory, named with locale code and containing the same directory structure as the source directory.
Sibling directories, not subdirectories. The source directory must not contain the translation directories.
In short, this layout is not valid for raw project type because srcdir contains the translation dirs:
- {project}/document.txt
- {project}/de/document.txt
- {project}/ja/document.txt
the correct structure has a separate source directory that does not contain translation directories:
- {project}/source/document.txt
- {project}/de/document.txt
- {project}/ja/document.txt
I am closing this as not a bug (it is the implemented behaviour and it is correctly documented). Support for different directory structure should be an RFE.
It is usability bug then. Except for publican (podir) or man page, most projects I have seen are like Source: document.ext Translation: document_<locale>.ext Freemind and LibreOffice are two exapmles. Please try to push those to Zanata, yes, I have tried. It is achievable, but time consuming. I agree, it is a usability bug. If raw projects can't support overlapping source and target directories (they is supported for .properties, although it isn't pretty), we should at least detect this unsupported configuration and warn the user. (In reply to Sean Flanigan from comment #5) > I agree, it is a usability bug. If raw projects can't support overlapping > source and target directories (they is supported for .properties, although > it isn't pretty), we should at least detect this unsupported configuration > and warn the user. That makes sense, we should definitely implement that ASAP. I have created a separate RFE for changing how the directory structure works, with just the relevant information. People should not have to read all the cruft here to understand that change: https://bugzilla.redhat.com/show_bug.cgi?id=1207475 Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-231 |