[jboss-as7-dev] Process for patching localized translation files

[Tomaz Cerar]

There is also another use case that we need a workflow for.
What happens when we "refactor" properties, for example when keys are
renamed. 
Which is quite often considering that when internals of subsystem changes
usually keys are renamed and names unified (i.e. subsystem is converted to
ResourceDefinition)

--
tomaz


-----Original Message-----
From: jboss-as7-dev-bounces at lists.jboss.org
[mailto:jboss-as7-dev-bounces at lists.jboss.org] On Behalf Of Brian
Stansberry
Sent: Thursday, May 10, 2012 7:48 PM
To: Manuel Ospina
Cc: jboss-as7-dev at lists.jboss.org Development
Subject: [jboss-as7-dev] Process for patching localized translation files

Hi Manuel,

Can you describe a bit what process we should follow for handling
community updates to the localized text files in the AS? For example, the
various LocalDescriptions_fr.properties files.

The files are now in the AS codebase itself, so naturally people are going
to start sending in patches that directly edit them [1]. But I suspect
that's not the correct process, and perhaps changes need to go through
https://translate.jboss.org/ with the person proposing the patch signing
up and joining the appropriate language team?

If the process isn't as simple as us directly accepting patches via
github, it would be great to include some comments at the top of each file
pointing to instructions on how to submit fixes.

[1] For example, https://github.com/jbossas/jboss-as/pull/2292

--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev