In T216307#4959186, @Harjotsingh wrote:

Hi,

Could you tell the expected behaviour of the rendering ? how it is supposed to look.

I tried testing one - File on SVG translate

Hi @Mhurd. We are no longer actively working on CodeMirror and won't be able to prioritize this. To the best of my knowledge, we tried to do this at some point but it was not as straightforward as we thought.

Thanks @FaFlo!

@Glrx If you don't mind, I will merge this into T216283: [BUG] SVG translate does not recognize labels in text elements rather than tspan.

In T215184#4957235, @aezell wrote:

If we share these on-wiki but then go with a solution like a browser extension, is that going to be a confusing shift?

@MaxSem: From a conversation with @Mooeypoo it seems like there is some confusion on what the desired behavior is here. I've made it clearer in the ticket.

In T216207#4956276, @Glrx wrote:

There was a problem with File:999-percentages.svg when used on toolforge. I suspect toolforge cached a local copy of the file. I uploaded a new version of the file to Commons and purged the Commons File: page. I suspect the purge invalidates conventional WMF servers but not toolforge's cache. Toolforge probably thinks the file is still fresh, so it does not contact Commons to see if the file is still current.

The app is now live!

Thanks @Glrx. I'll take that file off the ticket.

@ITait The app is all set to go live later today. Bryan and I created four test applications as part of our testing. You'll see them when you login.

@Glrx I do see the popup but I also see the preview rendered fine. Do you see the preview?

In T213937#4955334, @Glrx wrote:

No, you should not overlook any transform.

Transforms and other properties in switch clauses should only be promoted (aka hoisted) if they appear on each and every clause of the switch. Such promotions must concatenate with any existing transforms rather than replace the existing transforms. Do not assume that properties on one clause exist on all other clauses. That was the mistake that SVGTranslate 2.0 was doing.

SVG files are programs, and any manipulations of the SVG should be done with the same care as optimizing compilers.

@Glrx Do you recommend overlooking transforms entirely if they apply on one element in a switch but not others? Can we?

Let's try keeping all attributes and see if that resolves some of the issues we are seeing.

@Esanders You see this checkbox on Special:Preferences? That's very surprising. GlobalPreferences UI should only load on Special:GlobalPreferences.

In T210682#4951858, @MusikAnimal wrote:

In T210682#4951844, @jmatazzoni wrote:

....That would mean another calculation methodology; it is not trivial to do this. Just for the sake of avoiding complexities right now, I would advise against doing that for the MVP.

I'm not too worried about this, which is not uncommon but more or less an edge case. So if we don't find a way to handle such errors, what would happen in the event, as I said, of a "case where a stored page ID refers to a page that was subsequently deleted"? (As I say, I assume that is what Leon was referring to by "broken," but I might be wrong.) What would the system do?

It's a matter of saying "this page isn't in revision, so use archive instead". Easier said than done, but it shouldn't be too bad. If we don't do anything, it might error out (since the data it wants isn't there), or you just get blank values in the report, not sure.

In T215580#4949949, @MaxSem wrote:

...Which raises a question: what shall we do with attributes? Currently, we only preserve id and style when making the DOM translatable.

In T210564#4949871, @Samwilson wrote:

Doing so will also deploy T214452; is that okay?

@Samwilson Please update prod with the merged PRs above. Especially the one with improved upload comment.

Thanks @ITait. I have updated it with the new link. Are you talking about this message?

@Samwilson Works for me! Please update production too.

@ITait I've updated the test site with the changes. Please give it a whirl and let me know if anything looks off.

@ITait At one point in the application, it says, For questions about this application, or to access or change your answers, contact eyoung@wikimedia.org. Should I change that to be your email instead?

In T215302#4948628, @ITait wrote:

@Niharika heard back from legal and they're working on a privacy statement. In the mean time, please keep the 2018 link.
Once the site goes live on for submissions on the 15th, what is our ability to edit that URL? If the answer is not at all, I will tell legal to edit the wiki with a redirect instead of changing the URL in the site. Thanks!

We have scope for editing the URL but it will affect translations. I'll keep the 2018 link for now.

@Glrx Oh, that might be the problem. Thanks for all your help in fixing up these files!

@Jinoytommanjaly What do you mean when you say it is getting overwritten? I just added Hindi translations for the same file and I see them. I think you are getting confused because the translations are added to the same file. You can change the language you see by using the Render this language in dropdown box on Commons. See this link.

@Samwilson Is this ticket still required? Can we put it on the back-burner if it's not urgent anymore?

@Jinoytommanjaly @KCVelaga I also created this ticket which is related to the issue you raised.

In T215690#4940541, @Jinoytommanjaly wrote: