[{"data":1,"prerenderedAt":221},["ShallowReactive",2],{"page:/zh/guides/iso-8601-and-unix-time":3},{"id":4,"title":5,"body":6,"description":207,"extension":208,"eyebrow":209,"faq":210,"locale":211,"meta":212,"navigation":213,"pageType":214,"path":215,"related":210,"seo":216,"stem":219,"__hash__":220},"pages/zh/guides/iso-8601-and-unix-time.md","ISO 8601 与 Unix 时间",{"type":7,"value":8,"toc":195},"minimark",[9,13,30,33,45,48,51,55,58,62,119,128,131,148,158,162,165,180,183],[10,11,12],"h2",{"id":12},"数字与格式化日期",[14,15,16,17,21,22,25,26,29],"p",{},"Unix 时间戳紧凑且便于计算；ISO 8601 可读，并能声明 UTC 偏移。",[18,19,20],"code",{},"2023-11-14T22:13:20Z"," 中的 ",[18,23,24],{},"Z"," 表示 UTC，对应 Unix 时间戳 ",[18,27,28],{},"1700000000"," 秒。",[10,31,32],{"id":32},"保持同一时刻",[14,34,35,37,38,41,42,44],{},[18,36,20],{}," 与 ",[18,39,40],{},"2023-11-15T06:13:20+08:00"," 描述同一时刻，转换为 Unix 时间后得到相同数值。若 ISO 字符串没有 ",[18,43,24],{}," 或偏移，就必须由外部规则说明它属于哪个时区。",[10,46,47],{"id":47},"往返转换的选择",[14,49,50],{},"面向人工查看的日志和数据交换，适合使用带明确偏移的 ISO 字符串；需要紧凑存储和算术处理时，可使用明确记录单位的 Unix 数值。源数据包含有效小数秒时，应在往返过程中保留精度。",[10,52,54],{"id":53},"iso-8601-与-rfc-3339","ISO 8601 与 RFC 3339",[14,56,57],{},"RFC 3339 是面向互联网时间戳的更受限格式子集。实际 API 中应查看字段规范，不要仅凭字符串外观猜测是否允许省略偏移或采用不常见日期形式。",[10,59,61],{"id":60},"带偏移日期与-unix-时间如何对应","带偏移日期与 Unix 时间如何对应？",[63,64,65,78],"table",{},[66,67,68],"thead",{},[69,70,71,75],"tr",{},[72,73,74],"th",{},"表示方式",[72,76,77],{},"同一时刻的值",[79,80,81,91,100,110],"tbody",{},[69,82,83,87],{},[84,85,86],"td",{},"UTC",[84,88,89],{},[18,90,20],{},[69,92,93,96],{},[84,94,95],{},"北京偏移",[84,97,98],{},[18,99,40],{},[69,101,102,105],{},[84,103,104],{},"纽约偏移",[84,106,107],{},[18,108,109],{},"2023-11-14T17:13:20-05:00",[69,111,112,115],{},[84,113,114],{},"Unix 秒",[84,116,117],{},[18,118,28],{},[14,120,121,122,124,125,127],{},"末尾的 ",[18,123,24],{}," 表示 UTC 零偏移；带正负号的偏移说明显示钟点与 UTC 相差多少。去掉偏移后，日期就需要一个来源时区才能确定具体时刻。把北京钟点直接加上 ",[18,126,24],{}," 是宣称它为 UTC，会改变含义，并没有完成换算。",[10,129,130],{"id":130},"按步骤核对往返转换",[14,132,133,134,139,140,142,143,147],{},"在",[135,136,138],"a",{"href":137},"/zh/timestamp-to-date/","时间戳转换器","输入 ",[18,141,28],{},"，选择秒，复制 ISO 输出。再到",[135,144,146],{"href":145},"/zh/date-to-timestamp/","日期转时间戳","，输入 2023 年 11 月 14 日 22:13:20、选择 UTC 和秒，结果应回到同一个整数。",[14,149,150,153,154,157],{},[18,151,152],{},"2023-11-14T22:13:20.123Z"," 对应 ",[18,155,156],{},"1700000000123"," 毫秒。如果目标系统只支持整数秒，123 毫秒就无法保留。交换数据前应确认双方允许的精度，而不是只核对日期格式。",[10,159,161],{"id":160},"哪种格式适合接口","哪种格式适合接口？",[14,163,164],{},"ISO 8601 包含的形式比许多程序解析器支持的更多。RFC 3339 是面向互联网交换的较窄格式约定；扩展日期、钟点和明确偏移通常更便于兼容。",[14,166,167,170,171,174,175,179],{},[18,168,169],{},"[America/New_York]"," 后缀附带 IANA 时区标识，但不是所有 ISO 或 RFC 3339 解析器都接受。普通接口优先使用 UTC ISO 输出，涉及地区规则的排程另存时区名称。不要把 ",[18,172,173],{},"03/04/2026"," 这种日期顺序不明确的字符串写进接口；缺少偏移的日期应参照",[135,176,178],{"href":177},"/zh/guides/time-zones-and-dst/","时区与夏令时指南","解释。",[10,181,182],{"id":182},"标准与运行时参考",[184,185,186],"ul",{},[187,188,189],"li",{},[135,190,194],{"href":191,"rel":192},"https://www.rfc-editor.org/rfc/rfc3339",[193],"nofollow","RFC 3339",{"title":196,"searchDepth":197,"depth":197,"links":198},"",2,[199,200,201,202,203,204,205,206],{"id":12,"depth":197,"text":12},{"id":32,"depth":197,"text":32},{"id":47,"depth":197,"text":47},{"id":53,"depth":197,"text":54},{"id":60,"depth":197,"text":61},{"id":130,"depth":197,"text":130},{"id":160,"depth":197,"text":161},{"id":182,"depth":197,"text":182},"比较数字 epoch 和可读 ISO 8601 日期，理解偏移、Z 标记与安全往返转换。","md","指南 / 格式",null,"zh",{},true,"guide","/zh/guides/iso-8601-and-unix-time",{"title":217,"description":218},"ISO 8601 与 Unix 时间戳 — 日期、Z 和 UTC 偏移","比较 ISO 8601 日期字符串与 Unix 时间戳，理解 Z、UTC 偏移和安全往返转换。","zh/guides/iso-8601-and-unix-time","HKy4WWyQlA9JGPGT3ga82ViamOWbA-MzuglurP7hZlE",1792032485846]