[
https://issues.jboss.org/browse/ARQ-1681?page=com.atlassian.jira.plugin.s...
]
Stefan Miklosovic commented on ARQ-1681:
----------------------------------------
In my opinion, the most doable approach is to have conf property like
<property name="language">es</property>
which would default to "en" and there would be templates bundled in api jar with
all translations so picking the right template is the matter of parsing that property in
runtime and picking the right template for that language.
In case of providing own languages, the most doable way is to just translate default
template to target language and sent a PR. While it is not merge and released, user always
can use its own translated template anyway.
Implement multilanguage support in Arquillian Exporter
------------------------------------------------------
Key: ARQ-1681
URL:
https://issues.jboss.org/browse/ARQ-1681
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Extension - Recorder
Affects Versions: recorder_1.0.0.Alpha1
Reporter: Alex Soto
Priority: Optional
Currently Reports are generated in English. In reports there are some static information
like some labels or footnotes, ...
Because test results are also documentation, it has sense that the report may be a part
of rendered final documents, but if for example all of them are written in Spanish, then
it is strange to have one document in English.
For this reason I think we should add some internal and external default directories
where to find translations so people can collaborate in translations, but also allowing
users to provide their own.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira