Add info about HTML and JS new features #327

xfq · 2021-12-02T11:51:15Z

Fix #7.

Changes:

Remove "intended audience"
Change the question from "How do I prepare my web pages to display varying international date formats?" to "How do I manage date formats on a web page?"
Divide the article into two parts: input and output of dates
Mention the date & time markup in HTML5
Mention the JavaScript Date object (I choose not to mention Temporal for now, because I want to wait until there are at least two shipping implementations)
Remove the information on Java/JSP, ASP, and Perl. I don't think these can provide much guidance to developers nowadays, because Java/Spring and PHP are much more popular.

r12a · 2022-08-16T14:43:22Z

@xfq i just came across this. Do you want to continue to make these changes? If so, i think we need to solve the conflicts first. Then i have a number of suggestions ranging from organisation of sections to typos.

xfq · 2022-08-17T05:02:31Z

Do you want to continue to make these changes?

Yes. I have resolved the conflicts.

r12a · 2022-08-17T09:43:25Z

ac0a810#diff-925e46831aa6b3e93b26574309eda5813c4092dc831e2dfa6757c86b0a167c72 is showing a massive number of changes to the repo. I'm not sure what that's about, and whether it means all the files mentioned will be updated (which is not a good idea). Could you take a look and let me know?

xfq · 2022-08-17T11:58:49Z

That's normal, as I need to resolve the merge conflicts. Those modifications are already in the gh-pages branch.

himorin · 2022-08-17T14:07:56Z

That's normal, as I need to resolve the merge conflicts. Those modifications are already in the gh-pages branch.

In addition, some more explanation. When some branch is created at 100th history of HEAD, and bunch of updates are committed to HEAD during discussion held in PR of the branch - like 170th HEAD, the branch is ahead of HEAD over 70 commits. If there is conflict(s) between PR and ones during 70 commits, conflicted file(s) are required to be resolved. For this, there are several ways, like:

take updates between 100th and 170th HEAD, per file which is modified within the PR (named as resolve conflict button on merging)
just rebase from 100th to 170th HEAD, like modify history of PR from '100th HEAD -> commit for PR' to '170th HEAD -> commit for PR', which results to modify the PR as started from 170th HEAD
merge from origin/HEAD to the PR, which applies all modification happened on HEAD, like taking all commits between 100th and 170th into the PR (history will be 100th HEAD -(fork)-> commit for PR -> all changes between 100-170)

For the last, commit for merging all changes (e.g. 100th to 170th in example above) will be shown lie ac0a810, but Files changed tab in PR will show will show only changes between 170th HEAD and the PR which is similar to the original change for the PR.

xfq · 2022-08-17T23:33:11Z

Thanks for your explanation, @himorin!

questions/qa-date-format.en.html

r12a · 2022-09-01T11:30:56Z

questions/qa-date-format.en.html

-      <p>Use <code>$ENV{'HTTP_ACCEPT_LANGUAGE'}</code> to get the preferred language. Use <code>POSIX:strftime</code> to format date values.
-        You'll have to do your own mapping of the accepted languages value to a date format string.</p>
-    </div>
+    <p>How this is done will vary depending on your development environment.</p>


The section "Store and display a date" also seems to lack focus. In fact, i think it's trying to do 2 separate things:

describe how local date/time formats can be different and problematic, and what works or doesn't work if you try to use a generic format

describe how to produce dates and times in your code (one method described is that using JavaScript – but it doesn't mention the time element in HTML

Is option 3 really something useful these days? Or is it part of the discussion "How language interacts with date/time settings and where to get the language from" ?

Do you have any specific suggestions? I think option 3 is still useful. Do you think it should be removed or split into a separate article?

questions/qa-date-format.en.html

netlify · 2023-02-08T13:55:47Z

✅ Deploy Preview for i18n-drafts ready!

Name	Link
🔨 Latest commit	`2f3f6ba`
🔍 Latest deploy log	https://app.netlify.com/sites/i18n-drafts/deploys/66d6a04afabff20008834a56
😎 Deploy Preview	https://deploy-preview-327--i18n-drafts.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

aphillips

in progress

aphillips · 2024-08-22T14:39:02Z

questions/qa-date-format.en.html

@@ -56,21 +59,104 @@ <h1>Date formats</h1>


 <section id="question">
-<h2>Question</h2>
-<p class="question">How do I prepare my web pages to display varying international date formats?</p>
 <p>Visitors to a web site from varying locales may be confused by date formats. The format MM/DD/YY is unique to the United States (but sometimes used in Canada, too, which can obviously create some confusion there). Most of Europe uses DD/MM/YY. Japan uses YY/MM/DD. The separators may be slashes, dashes or periods. Some locales print leading zeroes, others suppress them. If a native Japanese speaker is reading a US English web page from a web site in Germany that contains the date 03/04/02 how do they interpret it?</p>


This paragraph (which you didn't touch) is misleading. There are many formats in use. The field order problem is only part of the issue.

The field order problem is, IMHO, the most obvious and confusing issue for web users. This paragraph also mentions the separator differences, and leading zeros, etc.

I know there are other problems that are not mentioned, such as whether to use month names, whether the year is 2 or 4 digits, whether the numbers are full-width or half-width (in CJK), which calendar to use, etc. Do these also need to be mentioned at the beginning of the article? Or should we write a separate article to talk about various date formats, just like our article on font styles and line breaking?

questions/qa-date-format.en.html

Co-authored-by: Addison Phillips <[email protected]>

xfq · 2024-09-24T05:19:06Z

Discussions during TPAC 2024: https://www.w3.org/2024/09/23-i18n-minutes.html#t03

Add info about HTML and JS new features

66aade8

xfq requested a review from r12a December 2, 2021 11:51

xfq added 3 commits December 9, 2021 13:51

Move a paragraph

8175fab

Change the question

093fbfc

Add intro

80df8cd

Merge branch 'gh-pages' into xfq/qa-date-format

ac0a810

xfq added 8 commits August 22, 2022 10:40

Move the headings

5d8fe11

Typo fix

ff0c79f

Markup fix

67d45a5

Editorial fixes

32f26d1

Mention customized date and time picker

0a306b6

Clarification

6dbad0f

Point to MDN

33a32e9

Update the authors

4ea7edc

r12a requested changes Sep 1, 2022

View reviewed changes

xfq added 7 commits September 2, 2022 16:20

Remove the heading

fa3e8ea

Add information on how the content author gets the information

765e8be

Mention getTimezoneOffset

2262a28

Add what the content authors are achieving

2676d8d

Add more information on customized date and time picker

c90f8f1

Add the step attribute

77a6ff9

trigger netlify

a7643ad

w3c deleted a comment from netlify bot Feb 8, 2023

Mention Temporal

d706d29

aphillips reviewed Aug 29, 2024

View reviewed changes

Update questions/qa-date-format.en.html

2f3f6ba

Co-authored-by: Addison Phillips <[email protected]>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add info about HTML and JS new features #327

Add info about HTML and JS new features #327

xfq commented Dec 2, 2021 •

edited

Loading

r12a commented Aug 16, 2022

xfq commented Aug 17, 2022

r12a commented Aug 17, 2022

xfq commented Aug 17, 2022

himorin commented Aug 17, 2022 •

edited

Loading

xfq commented Aug 17, 2022

r12a Sep 1, 2022

xfq Sep 3, 2024

netlify bot commented Feb 8, 2023 •

edited

Loading

aphillips left a comment

aphillips Aug 22, 2024

xfq Sep 3, 2024

xfq commented Sep 24, 2024

Add info about HTML and JS new features #327

Are you sure you want to change the base?

Add info about HTML and JS new features #327

Conversation

xfq commented Dec 2, 2021 • edited Loading

r12a commented Aug 16, 2022

xfq commented Aug 17, 2022

r12a commented Aug 17, 2022

xfq commented Aug 17, 2022

himorin commented Aug 17, 2022 • edited Loading

xfq commented Aug 17, 2022

r12a Sep 1, 2022

Choose a reason for hiding this comment

xfq Sep 3, 2024

Choose a reason for hiding this comment

netlify bot commented Feb 8, 2023 • edited Loading

✅ Deploy Preview for i18n-drafts ready!

aphillips left a comment

Choose a reason for hiding this comment

aphillips Aug 22, 2024

Choose a reason for hiding this comment

xfq Sep 3, 2024

Choose a reason for hiding this comment

xfq commented Sep 24, 2024

xfq commented Dec 2, 2021 •

edited

Loading

himorin commented Aug 17, 2022 •

edited

Loading

netlify bot commented Feb 8, 2023 •

edited

Loading