Closed Bug 1446326 Opened 7 years ago Closed 7 years ago

[FTL] Copy button ignore DATETIME built-in function

Categories

(Webtools Graveyard :: Pontoon, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1437857

People

(Reporter: felix.bau, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20180310025718 Steps to reproduce: I pressed the copy button on: https://pontoon.mozilla.org/de/common-voice/messages.ftl/?time=201802271115-201803142224&string=175865 Actual results: It pasted only "Effective " to the textarea below Expected results: The textarea should've contained the following line: privacy-effective = Effective { DATETIME($date, month: "long", year: "numeric", day: "numeric") }
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Pontoon doesn't copy full string - copy button → [FTL] Copy button ignore DATETIME built-in function
(In reply to Djfe from comment #1) > This string doesn't even have a copy button for some reason: > https://pontoon.mozilla.org/de/common-voice/messages.ftl/?time=201802271115- > 201803142224&string=175940 Because it's stuck in advanced mode. See the green FTL, and notice the format STRINGID = translation The string is also displayed incorrectly in the sidebar, and in the history.
I see, I saw the FTL button before, but didn't know what it was for ^^ (I'm studying the help documents of pontoon now) Though: on this one string (only the second one I linked) pressing FTL doesn't switch to simple mode for some reason though. it stays in FTL
Doc: https://mozilla-l10n.github.io/localizer-documentation/tools/pontoon/ui.html#fluent---ftl-files That's supposed to happen when the string has syntax issues, but this one should be correct. The reality is that this specific feature of Fluent wasn't used yet, and clearly Pontoon has some problems dealing with it. P.S. I see that German has only suggestions. Are you in touch with someone to get the strings reviewed and approved?
Component: General → Pontoon
Product: Localization Infrastructure and Tools → Webtools
Version: unspecified → other
All these issues boil down to bug 1437857. Bumping its priority.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Cool, it's fixed by now :) I got one last question, that the documentation doesn't answer, yet Is it allowed/correct to reorder items in the datetime function to get let's say the correct order for a date in germany? https://pontoon.mozilla.org/de/common-voice/messages.ftl/?extra=has-suggestions&string=175865 Effective {DATETIME($date, month: "long", year: "numeric", day: "numeric")} Gültig ab {DATETIME($date, day: "numeric", month: "long", year: "numeric")} 23.03.2018
(In reply to Djfe from comment #8) > Cool, it's fixed by now :) > I got one last question, that the documentation doesn't answer, yet > Is it allowed/correct to reorder items in the datetime function to get let's > say the correct order for a date in germany? > https://pontoon.mozilla.org/de/common-voice/messages.ftl/?extra=has- > suggestions&string=175865 > > Effective {DATETIME($date, month: "long", year: "numeric", day: "numeric")} > Gültig ab {DATETIME($date, day: "numeric", month: "long", year: "numeric")} > > 23.03.2018 The order of element is irrelevant, the output depends on the current locale https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat var date = new Date(Date.UTC(2018, 03, 23, 7, 0, 0)); var options = { month: 'long', year: 'numeric', day: 'numeric' }; console.log(new Intl.DateTimeFormat('en-US', options).format(date)); // Result: April 23, 2018 console.log(new Intl.DateTimeFormat('de', options).format(date)); // Result: 23. April 2018
Man, blazing fast support :) Thx!!
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.