Comments (3)
formats
is covered by #14. Still need to investigate timeZone
. Is timeZone
necessary for timestamp numbers as dates or do they have a defined time zone?
from next-intl.
Handling the timeZone
is indeed interesting. A server request doesn't include this information, therefore ideally we'd use a setting saved in the user profile or otherwise information from GeoIP. Both can not be known by this library, therefore the user should provide this.
from next-intl.
On the client side this is different. E.g. when the user provides a time via a date picker for example, we can typically read the timezone of the user and add it to the date. Not sure yet if that affects this library, as during render only timezone-aware dates should be used. In the change handler of a date picker a timezone can be added immediately.
from next-intl.
Related Issues (20)
- Example-app-router error when using output: 'export' (SSG) HOT 1
- Unable to find `next-intl` locale because the middleware didn't run on this request. HOT 1
- next-intl does not output index.html file HOT 1
- router issue when switching locale: path.startsWith is not a function HOT 8
- Incompatibility of Server-Side Functions with Client Component Layout in Next.js 14 /app HOT 1
- How to send the language (locale) code to Fetch operations processed by the Client Side? HOT 1
- Unable to Use loading.tsx with next-intl in App Router with i18n Routing HOT 4
- NextJS 15 support HOT 2
- Cannot retrieve Link's props from createLocalizedPathnamesNavigation HOT 1
- Middleware should gracefully handle unsupported but valid locale identifiers HOT 1
- Next.js - Navigation between pages in the pages router loses translations. HOT 3
- [Docs]: Typescript Validation HOT 1
- NextJS 15's `next/font` breaks alternate header injection. HOT 3
- Add Support for Setting HttpOnly and Secure Flags on NEXT_LOCALE Cookie HOT 4
- Localized search/query params HOT 1
- Using Link component with legacyBehavior+passHref producing warnings HOT 3
- getPathname with params HOT 6
- During build process static path are not translated to its reflection from pathnames mapping from config.ts file HOT 1
- Export Href type definition that works for getPathname, redirect & <Link /> params/props HOT 1
- Does not support Pages router with Next.js < 13 HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from next-intl.