Skip to content
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.

Typo in method name: fistSupportedLocaleWithFallback: aNiladicBlock #1

Open
jbrichau opened this issue Mar 28, 2015 · 4 comments
Open

Comments

@jbrichau
Copy link
Member

From @GoogleCodeExporter on March 25, 2015 14:2

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 [email protected] on 22 Oct 2014 at 2:08

Copied from original issue: SeasideSt/Seaside#834

@jbrichau
Copy link
Member Author

From @GoogleCodeExporter on March 25, 2015 14:2

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 [email protected] on 26 Oct 2014 at 11:15

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

@jbrichau
Copy link
Member Author

From @GoogleCodeExporter on March 25, 2015 14:2

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 [email protected] on 5 Nov 2014 at 7:09

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

@jbrichau
Copy link
Member Author

From @GoogleCodeExporter on March 25, 2015 14:2

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

Original comment by [email protected] on 5 Nov 2014 at 7:13

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

@jbrichau
Copy link
Member Author

From @GoogleCodeExporter on March 25, 2015 14:2

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 [email protected] on 5 Nov 2014 at 7:27

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

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

No branches or pull requests

1 participant