Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NFR] allow Request::getBestLanguage() to return language without dialect #3135

Closed
quasipickle opened this issue Dec 15, 2014 · 3 comments
Closed
Labels
new feature request Planned Feature or New Feature Request

Comments

@quasipickle
Copy link
Contributor

quasipickle commented Dec 15, 2014

When I use \Phalcon\Mvc\Request->getBestLanguage() on my browser, it returns "en-US". I think it would be helpful in some cases to have a way to just return "en", as my language files won't be broken down into "en-UK", "en-US", "en-CA", etc.

Something like getBestLanguageFamily(), or a variable passed to getBestLanguage() would be helpful.

@dschissler

This comment was marked as abuse.

@sergeyklay sergeyklay added this to the 4.0.0 milestone Jul 18, 2017
@stale stale bot added the stale Stale issue - automatically closed label Apr 16, 2018
@sergeyklay sergeyklay reopened this May 2, 2018
@stale stale bot removed the stale Stale issue - automatically closed label May 2, 2018
@phalcon phalcon deleted a comment from stale bot Feb 23, 2019
@niden
Copy link
Member

niden commented Feb 23, 2019

Closing in favor of #13855. Will revisit if the community votes for it, or in later versions.

@niden niden closed this as completed Feb 23, 2019
@niden niden added the new feature request Planned Feature or New Feature Request label Mar 11, 2019
@niden niden removed this from the 4.0.0 milestone Mar 11, 2019
@niden niden reopened this Mar 11, 2019
@niden niden added the 4.1 label Jun 21, 2019
@stale stale bot added the stale Stale issue - automatically closed label Dec 23, 2019
@phalcon phalcon deleted a comment from stale bot Dec 23, 2019
@stale stale bot removed the stale Stale issue - automatically closed label Dec 23, 2019
@niden niden mentioned this issue Jan 11, 2020
5 tasks
niden added a commit that referenced this issue Jan 11, 2020
niden added a commit that referenced this issue Jan 11, 2020
niden added a commit that referenced this issue Jan 11, 2020
niden added a commit that referenced this issue Jan 11, 2020
niden added a commit that referenced this issue Jan 11, 2020
niden added a commit that referenced this issue Jan 11, 2020
niden added a commit that referenced this issue Jan 11, 2020
@niden
Copy link
Member

niden commented Jan 11, 2020

Resolved in #14698

Thank you @quasipickle

@niden niden closed this as completed Jan 11, 2020
niden added a commit that referenced this issue Feb 4, 2020
niden added a commit that referenced this issue Feb 4, 2020
niden added a commit that referenced this issue Feb 4, 2020
niden added a commit that referenced this issue Feb 4, 2020
niden added a commit that referenced this issue Feb 4, 2020
niden added a commit that referenced this issue Feb 4, 2020
niden added a commit that referenced this issue Feb 4, 2020
@niden niden added this to Phalcon v5 Aug 25, 2022
@niden niden moved this to Released in Phalcon v5 Aug 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature request Planned Feature or New Feature Request
Projects
Archived in project
Development

No branches or pull requests

5 participants