AletheiaFact / AletheiaFact/aletheia

Enhancement: Implementation of internationalization (i18n) in date formatting

Abierto
#2,071 0 comentarios 0 reacciones 0 asignados Ver en GitHub
tech
Lenguaje dominante
TypeScript
Estrellas
55
Forks
20
Merge medio
2 d 6 h
PR fusionados (30 d)
2

Descripción

### Background Information

Currently, date formatting is hardcoded or set to a specific format. To improve the user experience globally and avoid future problems, we need to implement full internationalization (i18n) in date presentation.

The goal is for the system to detect the user's locale settings and display the date in the correct format, language, and order for that region (e.g., DD/MM/YYYY for pt-BR, MM/DD/YYYY for en-US, YYYY-MM-DD for en-CA, etc.).

### Steps to Reproduce

1. Change your browser settings and set the primary language to English (United States) - en-US (where the common format is MM/DD/YYYY).
2. Refresh the page in the application.

Expected result: The date should adapt to the locale and display in the expected format for en-US.

### How

_No response_

### Expected Behavior

The date format must dynamically adapt to the locale (language and region) configured by the user in the browser or in the application settings.
The expected formatting is that which follows the regional standard:

When the locale is pt-BR (Portuguese - Brazil):

- Expected format: Day/Month/Year (DD/MM/YYYY)
- Example for October 15, 2025: 10/15/2025

When the Locale is en-US (English - US):

- Expected Format: Month/Day/Year (MM/DD/YYYY)
- Example for October 15, 2025: 10/15/2025

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.