[zanata-bugs] [Bug 961185] Provide some way to get exact locales in zanata.xml

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=961185

Carlos Munoz <camunoz at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |irooskov at redhat.com



--- Comment #11 from Carlos Munoz <camunoz at redhat.com> ---
Parag,

I understand why automating this would make things easier for you. However,
there is a workaround for this, and frankly as repetitive as it might be, it is
something you only have to do when you start a project and when/if you ever
need to add or remove a locale from the list. Even when you are creating a new
project version, copying the previous version's zanata.xml should be a fairly
(if not fully) complete starting point.

I am cc'ing Isaac to make him aware of this bug, and discuss prioritization.

In the meanwhile, here is how I think this would work, and some problems
related to it:

We can add a client-level command to generate the zanata.xml file.
This command would need to pull all available locales for a given project
version from the server (and because there is no zanata.xml, the project,
version and server would need to be passed via command line). Once this is
done, the client would need to scan the local file system looking for localized
files (this means using the --includes argument), and try to make a "best
guess" on the mappings.

I say a "best guess" because take the following example: if there is a local
'es' file, and the server only contains locales 'es-ES' and 'es-CO' (just an
example), then the client would really have no idea which one to map to the
local file. This means the user still needs to validate that the zanata.xml
file was generated correctly and fixing any possible issues, thus reverting
back to a non-automated process.

This is not too different from the current process which is to download
zanata.xml and add any necessary locale mappings, and remove unused locales.

Another option like Sean mentioned in comment#1 is to add a way to download
zanata.xml. This still leaves you with your current predicament of having to
massage the zanata.xml file, but at  least it removes the step of logging into
Zanata and downloading the file.

Yet another option that comes to mind is to have a client command that
"analyzes" your zanata.xml looking for errors. It could tell a user if it
doesn't have all locales available in the server, if it has locales NOT
available in the server, and other suspicious things.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=WPgDXJUD1X&a=cc_unsubscribe