Just to clarify the idea behind having multiple message.xml files is so
plugins are self contained, i.e. they include their own translation
strings. This means that removing a plugin will also remove messages
that are not used in the rest of the application.
I believe the application uses all message.xml files that are relevant
to the current page, including apps/qubit/i18n and any plugin
message.xml files that apply. I'm not sure how conflicts between the
different files are resolved, but it would guess it's entirely arbitrary
based on the order in which the files are read. The translated messages
are found based on matching the source message string, so the
translation ids are not a factor in translating messages.
There is also a command line task which can be used to break the
message.xml files up so that plugin messages are moved to the
appropriate plugin directory.
> php symfony i18n:rectify pt
This will move Portugese strings from apps/qubit/i18n/pt/messages.xml to
the various plugins.
Regards,
--
David Juhasz,
Software Engineer
Artefactual Systems Inc.
www.artefactual.com
This is great, does it apply to v1.0.9.1? I ask this because the rectify command is not documented at all when i run the symfony command. Specifically on the i18n section i get 3 other commands 'diff', 'extract' and 'find'. I tried them all before i managed to get everything running great again but couldn't find out what any of these commands actually did.
By the way, my translation became broken because of a problem I had already seen but forgot to comment with the community. Some of the users making translations on our ICA-AtoM installation break the system. For instance, there's a translation string which original english text goes like 'End date&dagger'. When this string is translated through the web 'Translate User Interface' this field gets saved as 'Data final†', after this, the whole translation system is completely borked and broken. After manually editing the messages.xml to have this field be 'Data final†' everything gets back to working normally again. I believe this is not easily fixed but does anyon have an idea how one could tackle this situation in order to prevent future breakage of the system by our users
-- David Juhasz, Software Engineer, Artefactual Systems Inc. http://www.artefactual.com | P: +1.604.527.2056 | F: +1.604.521.2059
Restart your services:
Repopulate the search index:
Let us know if that works! If not, I'll ask one of our team members to offer further suggestions.
Cheers,
--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/d7408551-e50a-4474-a951-8aff2c328962%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks Dan,
Actually some of the translations is just where we can find tips to fill the archival description.
I know it shows only the rules from isad, but in Brazil we use another rule called Nobrade, which is basically the same thing, but changes one or two fields or names.
But, not only that. I work in a public military entity that only works with processes, so we will fill out some registers differently, like, the identifier must be the number of the legal process.
So, this is some kind of changes I will work with.
I am also studying how to do a Nobrade template to send you, so our community can view the description in another rule.
I am going to look at Transifex to try to help you also.
Thanks for the help.
Tati
You received this message because you are subscribed to a topic in the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/T2YWp89Y0MM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZJMpaf5AWar64Ae1FRgq7fAghz-VnMG34W1E9f87M0PNg%40mail.gmail.com.
This page in our documentation also contains some basic guidance on how to build a new theme plugin. Building a new template plugin is of course very different from building a theme plugin, but some of the initial steps to create and register your new plugin might be helpful to you. See:
Finally, you might find our Vagrant box useful as a local development environment. We have some basic instructions on setting up the 2.3 AtoM Vagrant box with VirtualBox here:
On YouTube we have a series of video tutorials about using the command-line in AtoM - these tutorials use the 2.3 Vagrant box, and the first 3 videos will assist you with installation and configuration of Vagrant for local development and testing. See:
Please feel free to ask questions in this forum, and our developers will try to provide some assistance. Be sure to look at our Developer resources on the wiki as well:
In general, we prefer to receive pull requests via GitHub. Information on our code review process, our coding standards, how to contribute code (including via pull request), and more is included in the Development resources linked above. To make it easier for our developers to perform code review, we also prefer a series of smaller commits, instead of one giant pull request.
Let us know how it goes!
Cheers,
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAGdZUcysfxtV0nycxY8vL-S0Pn5jg_pxjE6ONTm3GuHtW9e5jA%40mail.gmail.com.