note im not yet convinved about form type integration... if we go that way, we might want an optionintl => true to optionally change the source fromDateTimeZone::listIdentifiers() toTimezoneBundle

The intl variant IMHO should include, and be sorted by offset, from-xx:00 to+xx:00.

here we also see a different formatmeta - city vs.meta (city), i tend to prefer the latter =/

ill rebase and compile the full list tomorrow. Meanwhile, can we decide on#28846 Not sure we want to add the boilerplate classes now, only to deprecate them later again.

@ro0NL up to rebase and address any remaining comment?

@nicolas-grekas i've refigured out how the compile process went, and added a binary for it as such. Works for me :) Please validate.

Need to solve remaining comments still, but compiling is fast at least now :)

Should be rebased and finished as soon as#28846 is merged IMO.

@ro0NL#28846 has been merged now, so I think we can work on finishing this one.

Hm right, i felt awkward about a possible double-, yet Google did this:

As a plain list, without any context, i chose to avoid this duplication by using().

For the form, an alternative approach is to use optgroups per offset. Semantically (for JS & co) that might be more useful even. Havent come to play around with this though.

compiled the TZ offsets :)

hm shouldn't the offset be based on DST too?
Europe/Berlin as MEZ (+01:00) and MESZ (+02:00)

hm yes :) but we need a local time for that. Something likehttps://3v4l.org/57U2J could be taken into account inget(Raw)Offset(), allowing a local date (default now) to be specified.

status: needs work

@Hanmac i've removed the last commit, i dont think we need to compile offsets and instead simply useDateTimeZone directly.

status: needs review (still ready :))

@ro0NL Question about the Translation: i saw in the german translation something about normal time, but isn't that wrong for DST and should it say summer time instead?

maybe instead of going directly from DateTimeZone "Europe/Berlin" to Translation, maybe instead usegetTransitions for the abbr like "CET"/"CEST" and translate that ?

https://github.com/unicode-org/icu/blob/master/icu4c/source/data/zone also has different lables for that

@Hanmac i checked the google widget again :) today it includes

(GMT+02:00) Midden-Europese tijd - Amsterdam

(in englishCentral European Time)

so perhttps://github.com/unicode-org/icu/blob/78a4abc5ed5db9ddadb57dca0f5222e7639c124c/icu4c/source/data/zone/en.txt#L292-L295 it seems to always picklg (out oflg,ls andld) and only differs the offset based on local time.

I interpreted these codes as

lg: long generic, e.g. "Central European Time"
ls: long specific (not DST), e.g. "Central European Standard Time"
ld: long DST, e.g. "Central European Summer Time"

(http://site.icu-project.org/design/formatting/timezone/icu-4-8-time-zone-names#TOC-UTS-35-Time-Zone-Display-Name-Basics)

Symfony now followsls > lg > ld. I tend to believe we should also always uselg instead, as the fallback probably never happens (not sure why i pickedls instead 🤔 perhaps due this "standard" term)

So usinglg gives in fact shorter names 🎉 and is more in line with what@javiereguiluz expected in#28831 (comment) (AFAIK there's no mapping, nor translations available for continents, e.g. "Europe")

IMHO using the generic name solves the issue of names varied based on local time, thus a more simple implementation 👍 (the offset should be dynamic and is a display/rendering concern for now - unrelated here)

status: needs work

@Hanmac see3e09816, can you verify ... IMHO the results are much better now.

status: needs review

cc@fabpot

the Translations are in the Meta like de used for CET or MEZmeta:Europe_Central likelg{"Mitteleuropäische Zeit"} if you want you could usesg{"MEZ"} too.
From what i have seen you already use the meta stuff?

i think it is okay for now if the name you show is DST independent.

I think what the pro way would be:

• input timezone String "Europe/Berlin" call getTransitions on it with now time
• that gives you the offset and the abbr "CET"/"CEST" and if DST is on or off

do you need to parse the abbr?
i got the thinking you might needhttps://github.com/unicode-org/icu/blob/master/icu4c/source/data/zone/tzdbNames.txt but i am unsure now, because you already knew from the DST param what kind of label it should use? But that would make it depend on the local time and you can't prebuild it?

i currently don't know what the best way would be there

@Hanmac can you check once more :) the fallback forls is in fact required for translating Etc/GMT & co 🤷‍♂️

de.json currently is"Europe\/Berlin": "Mitteleuropäische Zeit (Berlin)", that's OK right? Im not sure i understand why we need the abbr. :/

From what i have seen you already use the meta stuff?

Yes

https://github.com/unicode-org/icu/blob/30d203459720bb64c850680a79b0f393a60934ca/icu4c/source/data/misc/metaZones.txt#L3553-L3557 gives us europe/berlin > Europe_Central

https://github.com/unicode-org/icu/blob/30d203459720bb64c850680a79b0f393a60934ca/icu4c/source/data/zone/de.txt#L1512-L1514 gives us Europe_Central > lg (Mitteleuropäische Zeit)

i think it is okay for now if the name you show is DST independent.

agree :)

I think what the pro way would be:

• input timezone String "Europe/Berlin" call getTransitions on it with now time
• that gives you the offset and the abbr "CET"/"CEST" and if DST is on or off

agree :)

do you need to parse the abbr?

again, not sure how the abbr. is related...

to clarify, SymfonyTimezones will not provide you the DST specific name (for now), only the generic one. Hence i suggested to only show the local offset with the generic tz name; that's what google does.

I think i understand,sg,ss,sd, most likely stands for "short generic/standard/dst" 😅 didnt know these were translatable (CEST in dutch, is MESZ in german :|)

Still, for the name itself, it's just another fallback. We only provide the long generic name for now.

Thank you@ro0NL.