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

Typo in method name: fistSupportedLocaleWithFallback: aNiladicBlock #834

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 5 comments
Closed

Comments

@GoogleCodeExporter
Copy link

fistSupportedLocaleWithFallback: aNiladicBlock
    | availableLanguageLocaleIDs |
    availableLanguageLocaleIDs := GetTextTranslator availableLanguageLocaleIDs.
    self requestContext request acceptLanguage do: [ :each |
        | locale |
        locale := each value.
        (availableLanguageLocaleIDs includes: locale asLocaleID)
            ifTrue: [ ^ locale ] ].
    ^ aNiladicBlock value

In 3.1

Original issue reported on code.google.com by philippe...@gmail.com on 22 Oct 2014 at 2:08

@GoogleCodeExporter
Copy link
Author

Name: Seaside-Gettext-Core-pmm.12
Author: pmm
Time: 26 October 2014, 12:14:17 pm
UUID: 42231744-9475-49a3-a995-0e350894d6fc
Ancestors: Seaside-Gettext-Core-WillemVanDenEnde.11

Issue 834:  Typo in method name: fistSupportedLocaleWithFallback: aNiladicBlock
- https://code.google.com/p/seaside/issues/detail?id=834

Original comment by philippe...@gmail.com on 26 Oct 2014 at 11:15

  • Changed state: Fixed
  • Added labels: Gettext
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Mind that I had already pulled the Seaside-GetText package into the Seaside32 
repository. I now also grabbed your changed package in the Seaside30Addons 
repository and copied it over.

I suggest we do not use the Seaside30Addons anymore and just pull in packages 
in the main repo. There is a lot of confusion which of those packages work with 
which seaside version.

Original comment by jo...@yesplan.be on 5 Nov 2014 at 7:09

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Wasn't aware of that. Yes, makes sense.

Original comment by philippe...@gmail.com on 5 Nov 2014 at 7:13

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

I know and I am to blame. I have not done a good job lately at publishing the 
changes correctly and I just noticed I did not publish that repository change 
in the configuration.


Original comment by jo...@yesplan.be on 5 Nov 2014 at 7:27

  • Added labels: ****
  • Removed labels: ****

@jbrichau
Copy link
Member

This issue was moved to #1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants