Hi Linda, I'm so glad to hear it! Thanks for reporting back about those permissions as well -- I never would have thought of those.
-Jane On Tue, Jan 19, 2021 at 10:20 PM Linda Jansová <[email protected]> wrote: > Hi Jane, Jennifer and everyone else interested in translations, > > We have tried repeating the steps but to no avail. > > However, after digging a bit deeper into the issue, we have found out > that there is a specific CREATE_TRANSLATION permission and also related > UPDATE_TRANSLATION and DELETE_TRANSLATION permissions. Our admin account > did not have these permissions granted by default and therefore only > English showed up in the translation dropdowns within the web client. > Adding the permissions to relevant permission groups (not only to the > admin ones) has sorted the issue. > > So now everything seems to work as expected :-). > > Linda > > On 1/12/21 7:40 AM, Linda Jansová wrote: > > Hi Jennifer, > > > > Thank you very much for sharing that Jane's steps have worked for you! > > We will repeat them and see what happens :-). > > > > Linda > > > > On 1/11/21 10:25 PM, Jennifer Pringle wrote: > >> Hi Linda, > >> > >> The steps Jane lists are what we did to get French added as an option > >> to the drop downs in the admin interfaces to add translations. It > >> also adds the language to the locale switcher in the upper right corner. > >> > >> For me, I have the staff client set to English (US) and I have > >> English (US), English (Canada), and French (Canada) available in both > >> the local switcher in the upper right and in the drop downs for the > >> "Apply Translations" pop up in the admin pages. (I can't speak to > >> what displays in the drop down if I set my locale in the upper right > >> to something other than English (US) as we don't currently have > >> things set up to use different languages for the web client, just the > >> OPAC.) > >> > >> Hope this helps, > >> > >> Jennifer > >> > >> > >> Quoting Linda Jansová <[email protected]>: > >> > >>> Hi Jane, > >>> > >>> Thank you! But it seems you mean the locale switcher in the upper > >>> right corner of the web client. I have actually had another > >>> translation dropdown on my mind - the one which enables you to add a > >>> new translation from within the web client. I have attached a > >>> screenshot with an example from Item Status Administration in Server > >>> Administration. > >>> > >>> I have double checked that Czech does not appear in the dropdown > >>> even when the web client as such is switched to English (in a way, > >>> it would make sense that you might want to translate to another > >>> language, not the one you are currently viewing the web client in; > >>> on the other hand, it is rather likely that you may wish to add a > >>> missing translation for the current language - it would also be > >>> clear which strings are missing and how the context is translated to > >>> make sure the translation is a good fit for a particular place in > >>> the web client). So the only translation option seems to be English, > >>> regardless of the interface language... > >>> > >>> Linda > >>> > >>> On 1/9/21 7:40 PM, Jane Sandberg wrote: > >>>> Hi Linda, > >>>> > >>>> To get another entry in the dropdown, you will want to: > >>>> > >>>> 1) Edit the locales array in > >>>> Open-ILS/src/eg2/src/environments/environment.prod.ts to include > >>>> 'cs-CZ' > >>>> > >>>> 2) Re-compile the Angular client by running the commands: > >>>> cd Open-ILS/src/eg2 > >>>> ng build --prod > >>>> > >>>> 3) As the root user, run the command: make install > >>>> > >>>> -Jane > >>>> > >>>> On Sat, Jan 9, 2021 at 7:09 AM Linda Jansová > >>>> <[email protected] <mailto:[email protected]>> wrote: > >>>> > >>>> Hi, > >>>> > >>>> We are on 3.5.1 and are trying to set up the translation feature > >>>> which > >>>> is now available directly in web client. > >>>> > >>>> So far we can only see English as a language to which one can > >>>> translate. > >>>> > >>>> How could we add Czech as another option in the dropdown? > >>>> > >>>> Thank you in advance for any ideas! > >>>> > >>>> Linda > >>>> > >>>> _______________________________________________ > >>>> Evergreen-general mailing list > >>>> [email protected] > >>>> <mailto:[email protected]> > >>>> > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general > >>>> > >>>> < > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general> > >>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> Jane Sandberg > >>>> Electronic Resources Librarian > >>>> Linn-Benton Community College > >>>> [email protected] <mailto:[email protected]> / 541-917-4655 > >>>> Pronouns: she/her/hers > >>>> > >>>> Library instagram: @lbcc_library > >>>> <https://www.instagram.com/lbcc_library/> > >>>> > >>>> _______________________________________________ > >>>> Evergreen-general mailing list > >>>> [email protected] > >>>> > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general > >>>> > >> > >> > > > > _______________________________________________ > Evergreen-general mailing list > [email protected] > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general > -- Jane Sandberg Electronic Resources Librarian Linn-Benton Community College [email protected] / 541-917-4655 Pronouns: she/her/hers Library instagram: @lbcc_library <https://www.instagram.com/lbcc_library/>
_______________________________________________ Evergreen-general mailing list [email protected] http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
