Language Inconsistency in Personal Details Section During Checkout - Arabic Language Setting

Open Beginner friendly
#177 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend, localization

Research direction

Reproduce the checkout flow with Arabic selected, then trace the card payment settings page and its personal-details text to the relevant localization entries. Verify which labels remain in English and compare them with the Arabic translations. Done means the personal-details page is fully displayed in Arabic during checkout without affecting other languages.

Written by the indexing model from the issue text.

Description

Overview:
When switching the language to Arabic in the Enatega Food Delivery website and proceeding to the card payment settings during checkout, a language inconsistency is observed. The page that requests personal details remains in English, which can be confusing for users who expect a fully localized experience.

Steps to Reproduce:
Access the Enatega Food Delivery website.
Change the language to Arabic.
Add items to the cart and proceed to the checkout section.
Navigate to the card payment settings.
Observe that the page requesting personal details (e.g., name, address) is displayed in English.

Expected Behavior:
The page requesting personal details during the card payment settings should be fully translated and displayed in Arabic when the language is set to Arabic, ensuring a seamless and localized user experience.

Actual Behavior:
The page requesting personal details remains in English after switching the language to Arabic during checkout.

image

Activity

Dominant language
TypeScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gray-mueller/full-stack-document-solution

All issues in gray-mueller/full-stack-document-solution

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.