Re: [OPEN-ILS-GENERAL] Translations in Angular 6+ (Was Evergreen 3.3 Release Update)
Correction, we export XMB but re-import XTB. Dan, I have opened https://bugs.launchpad.net/evergreen/+bug/1821067 to make the changes needed for supporting XMB/XTB files. On Wed, Mar 20, 2019 at 1:47 PM Bill Erickson wrote: > Dan, > > Let's be sure to export the current translations before any changes are > made. IIRC, we want .xmb format, though it's probably a good idea to > export a few more formats to be safe. Once you select a locale, the export > option is the first/top tool in the toolbar along the right. > > I'll go ahead and export the current .xmb file for Czech and commit it to > a working branch for safe keeping. > > -b > > > > On Wed, Mar 20, 2019 at 12:11 PM Daniel Wells wrote: > >> Hello Eva, >> >> Thank you for raising this concern. I think we are in the process of >> figuring things out as we go along. >> >> Our current best plan (I think) is to use the account we set up with >> POEditor.com. It looks like you already have an account there, so at least >> you are familiar with what I am talking about. What hasn't been figured >> out yet is what that overall update process looks like, and what the new >> build steps will be. For the first part at least, your input will be very >> valuable. >> >> We did a test import back in November or so (I think it was at the >> Hack-a-way). I would like to try to do another import to add any >> new/changed strings and see what happens, but being a completely new and >> unfamiliar tool, I am a little afraid of losing any work already put in >> there. >> >> So, a few questions: >> >> 1) Based on what you have already done in POEditor, do you think it is a >> viable solution? >> >> 2) I will do my best to preserve what is there, and I hope the re-import >> does the right thing, but how much would it take to redo the work done >> there so far if things go very badly? >> >> 3) Do you have a planned timeline for upgrading to 3.3? >> >> Sincerely, >> Dan >> >> >> On Mon, Feb 25, 2019 at 11:52 AM Cerninakova Eva wrote: >> >>> Hi Daniel, >>> >>> Considering the last year discussion about integrating Angular 6 >>> template translations into the Evergreen translation tools, I would like to >>> ask a question about translation workflow of Evergreen 3.3 release. Will it >>> change some way in comparison with previous releases, due the impossibility >>> to use Launchpad for translations of Angular strings? And if so, how the >>> Angular strings are supposed to be translated during the 3.3 release >>> process? (I am asking from translators point of view.) >>> >>> Thanks for the answer ;-) >>> Eva >>> >>> >>> >>> >>> >>> >>> >>> --- >>> Mgr. Eva Cerniňáková >>> cer...@jabok.cz >>> Tel. +420 211 222 409 >>> >>> Knihovna Jabok >>> http:/knihovna.jabok.cz >>> Tel. +420 211 222 410 >>> Jabok - Vyšší odborná škola sociálně pedagogická a teologická >>> Salmovská 8, 120 00 Praha 2 >>> >>> >>> >>> st 20. 2. 2019 v 16:03 odesílatel Daniel Wells >>> napsal: >>> Hello all, Two weeks have slid by once more, and today we mark, ostensibly, the feature freeze for Evergreen 3.3. Any new features not committed by the end of the day will need to wait for the 3.4 release in the fall. Once again, here are the feature branches under consideration: https://bugs.launchpad.net/evergreen/+bugs?%3Alist=NEW%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE%3Alist=WISHLIST_option=none%3Alist=86802=Search=title=0 As careful observers will note, we still have one week after today before the 3.3 beta. However, this exists not as a time to continue adding features, but as a time to make corrections for obvious issues which crop up due to feature freeze activity. The cutoff for new features has historically encouraged a mad dash of activity, and this scheduling gap exists not as an excuse to postpone such dashings, but to remedy the problems it brings. So I gladly encourage those so inclined to dash as madly as ever, but understand that it ends tonight! Now, that said, if a branch is in an obvious state of active review and revision, yet doesn't make the cutoff, please let me know and we can probably work it in. I intend to start doing internal building and testing starting tomorrow morning, and will not be terribly keen on straggling code walking in unannounced. Thank you for your diligence and understanding. Sincerely, Dan On Wed, Feb 6, 2019 at 12:40 PM Daniel Wells wrote: > Dearest fellow Evergreeners, > > After several months of quiet contemplation and tireless toiling by > many members of the Evergreen community, it is past time for a brief > message from me, your minimalist 3.3 release manager. > > First, as we enter this final trimester of the release process, it > seems worth revisiting the originally proposed
Re: [OPEN-ILS-GENERAL] Translations in Angular 6+ (Was Evergreen 3.3 Release Update)
Dan, Let's be sure to export the current translations before any changes are made. IIRC, we want .xmb format, though it's probably a good idea to export a few more formats to be safe. Once you select a locale, the export option is the first/top tool in the toolbar along the right. I'll go ahead and export the current .xmb file for Czech and commit it to a working branch for safe keeping. -b On Wed, Mar 20, 2019 at 12:11 PM Daniel Wells wrote: > Hello Eva, > > Thank you for raising this concern. I think we are in the process of > figuring things out as we go along. > > Our current best plan (I think) is to use the account we set up with > POEditor.com. It looks like you already have an account there, so at least > you are familiar with what I am talking about. What hasn't been figured > out yet is what that overall update process looks like, and what the new > build steps will be. For the first part at least, your input will be very > valuable. > > We did a test import back in November or so (I think it was at the > Hack-a-way). I would like to try to do another import to add any > new/changed strings and see what happens, but being a completely new and > unfamiliar tool, I am a little afraid of losing any work already put in > there. > > So, a few questions: > > 1) Based on what you have already done in POEditor, do you think it is a > viable solution? > > 2) I will do my best to preserve what is there, and I hope the re-import > does the right thing, but how much would it take to redo the work done > there so far if things go very badly? > > 3) Do you have a planned timeline for upgrading to 3.3? > > Sincerely, > Dan > > > On Mon, Feb 25, 2019 at 11:52 AM Cerninakova Eva wrote: > >> Hi Daniel, >> >> Considering the last year discussion about integrating Angular 6 template >> translations into the Evergreen translation tools, I would like to ask a >> question about translation workflow of Evergreen 3.3 release. Will it >> change some way in comparison with previous releases, due the impossibility >> to use Launchpad for translations of Angular strings? And if so, how the >> Angular strings are supposed to be translated during the 3.3 release >> process? (I am asking from translators point of view.) >> >> Thanks for the answer ;-) >> Eva >> >> >> >> >> >> >> >> --- >> Mgr. Eva Cerniňáková >> cer...@jabok.cz >> Tel. +420 211 222 409 >> >> Knihovna Jabok >> http:/knihovna.jabok.cz >> Tel. +420 211 222 410 >> Jabok - Vyšší odborná škola sociálně pedagogická a teologická >> Salmovská 8, 120 00 Praha 2 >> >> >> >> st 20. 2. 2019 v 16:03 odesílatel Daniel Wells >> napsal: >> >>> Hello all, >>> >>> Two weeks have slid by once more, and today we mark, ostensibly, the >>> feature freeze for Evergreen 3.3. Any new features not committed by the >>> end of the day will need to wait for the 3.4 release in the fall. Once >>> again, here are the feature branches under consideration: >>> >>> >>> https://bugs.launchpad.net/evergreen/+bugs?%3Alist=NEW%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE%3Alist=WISHLIST_option=none%3Alist=86802=Search=title=0 >>> >>> >>> As careful observers will note, we still have one week after today >>> before the 3.3 beta. However, this exists not as a time to continue adding >>> features, but as a time to make corrections for obvious issues which crop >>> up due to feature freeze activity. The cutoff for new features has >>> historically encouraged a mad dash of activity, and this scheduling gap >>> exists not as an excuse to postpone such dashings, but to remedy the >>> problems it brings. So I gladly encourage those so inclined to dash as >>> madly as ever, but understand that it ends tonight! >>> >>> Now, that said, if a branch is in an obvious state of active review and >>> revision, yet doesn't make the cutoff, please let me know and we can >>> probably work it in. I intend to start doing internal building and testing >>> starting tomorrow morning, and will not be terribly keen on straggling code >>> walking in unannounced. Thank you for your diligence and understanding. >>> >>> Sincerely, >>> Dan >>> >>> >>> On Wed, Feb 6, 2019 at 12:40 PM Daniel Wells wrote: >>> Dearest fellow Evergreeners, After several months of quiet contemplation and tireless toiling by many members of the Evergreen community, it is past time for a brief message from me, your minimalist 3.3 release manager. First, as we enter this final trimester of the release process, it seems worth revisiting the originally proposed timeline: 2/20/19 - Feature freeze 2/27/19 - Beta release 3/20/19 - Release Candidate 3/27/19 - Final release Accordingly, we are now exactly two weeks away from our intended feature freeze date. Please recall, however, that there is now a one week buffer between feature cutoff and the actual beta release, so if we reach
