Hi @Ejegg and @AKanji-WMF ! Just re-confirming that we do want to test V2 in the upcoming Japan campaign. Please let me know if there are any blockers or if we're good to go. Thank you! CC @spatton for vis

Hi Francesca,

@TomaszGorski bumping this on over to you!

@Ejegg let's keep for just these variants, so we can measure any change in KPI

Thank you @Ejegg ! Exciting stuff. Yukari, Seilo, and Ichi all reviewed. Just one edit they requested: changing the text in the donate button from "寄付" to "この内容で寄付する".

@spatton FYI ^

Dang! I really wanted to see how that would affect performance. I suspect it's one of the biggest variables (since currently the placeholder is in English). But if that's easier, then I'm fine with it

Hi @Ejegg just a friendly bump on my last message. Please let me know.

Hi @Ejegg just a heads up that Thea, Evelyn, and I chatted and we made a couple edits to the proposed variants, which are 2. You can find them in the Slides

In T307704#8411342, @Eileenmcnaughton wrote:

I spun off a sub-task to add a deprecation notice to testmeister as the lack of one was identified above as being confusing

In T307704#8411331, @Eileenmcnaughton wrote:

@CDenes_WMF can you flesh out what "doesn't show us how the dynamic content actually renders" means?

In T307704#8410947, @TSkaff wrote:

Thanks @CDenes_WMF, I just wanted to confirm: Have you tried making a real donation and seeing which email you get?

Tomasz also checked French and Portuguese and it is having the same issue as Spanish: fr-CA in tesmeister actually sends him the fr-FR civi template/copy and pt-BR in testmeister actually sends him the pt-PT civi template/copy

Hi both.

Just checked Testmeister. Testmeister is still causing the same issue as was documented in this phab task back in May. Thus, we currently have no dependable way of sending ourselves the coded Thank You emails in order to test how they actually render. The Civi interface does not provide this, and Testmeister is seemingly still broken. This is a blocker for QA. It's a big priority on our end. Could this please be prioritized? @TSkaff

HI all. Just wanted to follow up on this -- has Testmeister been fixed? Is it dependable? We need to do proofing our thank you emails for non-English languages. Please let me know, it is time sensitive. @Eileenmcnaughton @TSkaff Thanks!

Thanks Elliott! Yes the slides are much easier to digest IMO :) (wikilove to Thea for creating them).
We could either *not* store the Furigana at all; or Seilo suggested we could save it in Civi's "Nickname" field:

We definitely don't want to translate for those languages in the near future. Thank you for checking though!

Reviewed and confirmed we don't need any other languages from the disabled list (pretty cool they have Sardinian tho!). Thanks both :)

Hi @Eileenmcnaughton any updates on our ability to send ourselves the emails in production? We currently are unable to easily proof coded emails ATM. Thank you

Thank you, yes this is pretty urgent because currently we do not have any way of proofing the emails post-coding.

Thanks Eileen. The preview feature often has currency formatting issues, so it is not accurate enough to work for our proofing needs.

@AnnWF does that mean Testmeister is officially deprecated? If so, is there another tool we can use in order to send ourselves & test coded thank you emails?

@Eileenmcnaughton friendly bump!

@Eileenmcnaughton please do let us know the exact code we should use per Kristie's request above, and Tomasz can apply it to the non-English templates moving forward

@TSkaff FYI ^

Thanks for the update David. The LATAM pre-test is running today. So we can investigate incoming donations and check that they are getting the esLATAM copy.

Im basing this off of the fact the LATAM email starts with ¡Hola and the valencian starts with Benvolgut/Benvolguda

Hi! Adding on that pt-BR is having the same behavior: Testmeister Production is sending me a different email (see ATTACHED) from what is in the respective pt-BR Civi template

Thank you, David! Replies in-line:

Hi @DStrine, apologies if I was unclear. The text is identical in testmeister but it is *Not* identical (i.e. it is different) in the Civi templates, and it should be different (as the translations are not the same) . Please see my previous comment which states that the translations are different in Civi and includes the links to the civi templates:

Hi David! Could you please clarify what you mean by "until the esMX email text is changed"?

Thank you Rakhi. The Email sent is still in esES (not esMX).
However, I went to production testmeister and sent myself a copy of esES and a copy of esMX and the esMX is using the same copy as esES. Here are the links to the templates that Tomasz shared with me, that show esES copy and the esMX copy, and how they are different:
esES template
esMX template

Rakhi please feel free to share with me the tester's thank you email copy, and I can decipher it is esMX or esES. Thank you!

RE "You could update the signatures for all languages without updating the rest of the copy of the email." That wouldn't work unfortunately, as a majority of our non-English languages are gendered, so we'd have to re-translate everything if we're switching from a male signature (Jimmy) to a female signature (Maryana)

Thanks for the update David. I would flag then that at the present moment, our English thank you email has been updated to Maryana but all other languages haven't been updated yet (due to bandwidth limitations and other priorities), and are still from Jimmy. So all non-English donors will currently receive an email with Sender Maryana and body/signature from Jimmy (screenshot above).
CC @krobinson for visibility on this because I expect you may get some tickets from donors who notice the mismatch.

Looping in @RKumar_WMF who was coordinating the payments testing. Rakhi, could you please see David's question above? Thank you!

@Cstone O @DStrine Just one edit needed, to capitalize the first sentence:

I'm on staging testmeister and have tried to send myself a copy of "recurring_notification" in Italian, but I never receive it :/ Am I using the wrong link?

HI all, I noticed in the description of this task that the country/language combos are not accurate. South Africa is not in the bundle this year (will be a stand-alone campaign in May), and Ukraine and Israel are missing.

Thanks all! I'm a bit unclear on what we mean by "included" ? That's the document with the English source text. If you scroll down to page 2 you'll see the version for translations (i.e. "For Non-English Translations - Removing Endowment Language"), and that' exactly what we had translated into all these languages. If Pats just wants to makes sure that we followed that text, then yes... but otherwise please let me know.

ah noted, thanks @DStrine !

@DStrine bump on this please-- Want to make sure it doesn't get lost in the phab abyss :)

Thanks Eileen! Do you mind please re-coding the Chinese email to take from the Chinese-Traditional copy (instead of the currently Chinese-Simplified)? I don't feel comfortable yet having myself or Tomasz re-doing the entirety of the email/code without first undergoing any training. Please let me know if that' OK with you.

@Eileenmcnaughton we only want Chinese-Traditional; however, there is currently no Chinese email present in the UI tool (neither traditional nor simplified)

@Eileenmcnaughton could you please grant @TomaszGorski the same 'CiviCRM Admin' role? He is on the Localization team and will need it for post-coding review. TY!

Awesome, thanks Eileen :)

Great, thanks for all the details Eileen!

Great, thank you! I've never used this webpage before, a few questions:

Thank you very much @Eileenmcnaughton ! This link in your comment above is not working for me. Could you please let me know how best to proceed?

Awesome, thank you!

Hi @Ejegg ! I have a last minute edit to request for the Hungarian EOY Thank You email please. We got some really late feedback from the Hungarian reviewer (community/chapter member) who mentioned the first paragraph of the email is problematic now in Hungary due to the recent Pegasus scandal.

Pre-test date is confirmed as November 16th. Would it potentially be possible to have this in production by November 5th or 10th (giving us a couple days to proof and do a test donation)?? Please let us know, thank you!

Hi @Damilare ! Thanks :) What "heading" are you referring to? I think it should go either under or above the tax deductibility link within the green box of the screenshot.

Thanks yall. We are coordinating a final round of post-coded proofing. The versions sent to Tomasz will be funneled to DayTranslatinos for a final-final proof. We will communicate the greenlight here once that proof is complete and/or if any errors/edits are surfaced.

Great, thank you Eileen! @TomaszGorski Auto Recurring is off 'hold' and ready for post-coding proof. We can do this post-coding proof via DayTranslations. Will add details to the Asana card

Hi @Eileenmcnaughton we're seeing that what's in production (atleast for PT) is still the old version of these emails. Can you please let us know when these new versions are coded up and on staging or production? The new version copy is linked both in Tomasz's comment on June 3rd and also linked in the separate phab task that was requested: https://phabricator.wikimedia.org/T285375. Once those are coded and on staging, then we can do the post-coded proofing via a Civi self-send

Hi @Eileenmcnaughton we're seeing that what's in production (atleast for PT) is still the old version of these emails. Can you please let us know when these new versions (copy linked above in description) are coded and on staging or production? And then we can do the post-coded proofing via a Civi self-send

Created https://phabricator.wikimedia.org/T285375

Great, thank you very much for the update Eileen :) I'll leave it to you and Michael then, on when to deploy.

@DStrine do we need to create a separate phab task for getting the new copy/translations shared above by Tomasz into production?

Hey yall. Can't help here unfortunately-- I did not code these emails. Here's the phab task for when we handed these off for coding originally.

Next sprint is fine, it's not a critical edit. This should be it for this email. If we have any other edits to other Japanese emails (I don't expect we will.. then I will make it a separate phab task). Thank you!

Sure thing. How do I submit? I thought the phab task itself was the submission heh

Makes sense & sounds good (we had added it thinking that the first edit had not already been started on, and that it would be efficient to combine-- but since it's too late no worries) Will address it in the other phab task. Thank you!

To clarify on Tomasz's note "This one is specific to the Thank You email for recurring/monthly donations in Japanese, and concerns the first sentence of the first paragraph that looks like this now"

Hi David! It's just an edit to the translation of the current Japanese Thank You email in production, in order to make the translation clearer (Seilo suggestion). Thus why we bundled it within the same phab ticket: as it's two edits to the same TY email (one is the link in the footer; one is the text in the %ifrecurring% of paragraph). Please lmk if you need any additional info or context

Thank you Tomasz, that looks good to me and ready for the review by DT

Hi @krobinson ! If it's almost identical, then that sounds like a great solution :) Happy to have DayTranslations do a quick proof

Thank you Christine!! :)

Thanks for the tag Sam. No issues to raise-- The message draft looks great.

Hi @Cstone ! Third and Final batch of proofing has been complete. Here are the last languages that need edits. Edits can be found in linked google doc in yellow highlight:

• Spain-Spanish
• Ukrainian

Hi @DStrine ! Not resolved just quite yet. Second batch needs to be put in production (per my comment on Apr 14). And third and final batch details coming soon. Thank you!

@TSkaff for vis. Not positive if this falls in TY email umbrella; but could you please confirm we are OK to proceed on this project from your end? In a nutshell, we are re-translating the auto recurring failure. TY!