react-language-switch

Simple context-based language-differentiating display and selector components for react. Implements both switches for inline editing and json-based content.

Install

1npm install --save react-language-switch

Usage

1import React from 'react'
2
3import LanguageProvider, { LanguageDisplay, LanguageSelect, LanguageText } from 'react-language-switch'
4
5/*
6* Inline-based Component --------------------------------------------
7*/
8const exampleHeader = {

9  title: {

10    en: "Example: react-language-switch",

11    jp: "事例: react-language-switch",

12    de: "Beispiel: react-language-switch"
13  },

14  meta: [
15    {

16      name: "description",

17      en: "An example page for the react-language-switch library.",

18      jp: "Yea my japanese aint good enough for this either...",

19      de: "Eine Beispiel Seite für die react-language-switch library."
20    }
21  ]
22}
23export function InlineApp() {
24  const lang = useLanguage('inline-example')
25
26  return (
27      <LanguageProvider
28        languages={["en", "jp", "de"]}
29        init={'jp'}
30        defaultTo={"en"}
31        remember={true}
32        id="inline-example"
33        header={exampleHeader}
34      >
35        <div className="App">
36          <header className="App-header">
37            Current Language: {lang.get()}<br />
38            <button onClick={() => lang.set('en')}>Change to English</button>
39            <LanguageDisplay>
40              <en>Hello</en><jp /><de /> {/* If a component at any dom level should
41              not be displayed for a specific language, simply add a void language
42              tag for that language at that dom level*/}
43              <h1>
44                <en>Example App</en> {/* Each language tag will only be displayed if 
45                the corresponding language is selected. */}
46                <jp>事例</jp>
47                <de>Beispiel App</de>
48              </h1>
49              <div className="name-display">
50                <en>by Zino J. Vieth</en>
51                <jp>ヴィース　ジーノ　ジョエル　からです</jp>
52                {/* Omitting German here will cause it to default to the English text*/}
53              </div>
54            </LanguageDisplay>
55            <div>
56              <LanguageSelect>
57                <en>EN</en>
58                &nbsp;|&nbsp;
59                <jp>JP</jp>
60                &nbsp;|&nbsp;
61                <de>DE</de>
62              </LanguageSelect>
63            </div>
64          </header>
65        </div>
66      </LanguageProvider>
67    )
68}
69
70/*
71* JSON-based Component ----------------------------------------------
72*/
73const exampleLanguageSetup = {

74  id: "json-example",

75  remember: true,

76  languages: ["en", "jp", "de"],

77  init: "en",

78  defaultTo: "en",

79  header: {

80    title: {

81        en: "Example: react-language-switch",

82        jp: "事例: react-language-switch",

83        de: "Beispiel: react-language-switch"
84    },

85    meta: [
86        {

87        name: "description",

88        en: "An example page for the react-language-switch library.",

89        jp: "Yea my japanese aint good enough for this either...",

90        de: "Eine Beispiel Seite für die react-language-switch library."
91        }
92    ]
93  },

94  content: {

95    title: {

96      en: "Example App",

97      jp: "事例",

98      de: "Beispiel App"
99    },

100    name: {

101      en: "by Zino J. Vieth",

102      jp: "ヴィース　ジーノ　ジョエル　からです"
103      // omitting German here will cause it to default to English
104    }
105  }
106}
107export function JsonApp() {
108
109  const lang = useLanguage("json-example")
110
111  return (
112    <LanguageProvider
113        json={exampleLanguageSetup}
114      >
115        <div className="App">
116          <header className="App-header">
117            <h1>
118              <LanguageText name="title" />
119            </h1>
120            <div className="name-display">
121              <LanguageText name="name" />
122            </div>
123            <div>
124              <LanguageSelect>
125                <en>EN</en>
126                &nbsp;|&nbsp;
127                <jp>JP</jp>
128                &nbsp;|&nbsp;
129                <de>DE</de>
130              </LanguageSelect>
131            </div>
132            <button 
133              onClick={() => lang.setContent("name", { en: "by some guy", de: "von sonem Typen", jp: "ばかからです" })}
134            >Change Name</button>
135          </header>
136        </div>
137      </LanguageProvider>
138  )
139}
140

Usage Notes

• Do not nest LanguageDisplay and LanguageSelect! Both of these functions work recursively to move through the tree of its children.
• If you are using multiple LanguageProviders with localStorage active in your app, pass each of them a unique id if you want them to be able to remember different language settings.
• Passing header data via json to the LanguageProvider causes it to use react-helmet to update header/meta tags dynamically. These can be overwritten using react-helmet at a nested level anywhere else in your app. Currently only supports title and meta tag!
• If you are using multiple LanguageProviders that you pass header-data to, the last to render will always take priority, not the last to be updated! Therefore you should avoid using multiple LanguageProviders to update meta data, unless they update different tags.
• For the language list, avoid names that are the same as html or jsx tags, if you are planning to use the inline LanguageDisplay component.
• It is possible, and in certain scenarios necessary, to use both inline and json-based components. For example when wanting to display different text for the LanguageSelector buttons depending on the currently selected language, or when wanting to omitt entire components in some languages while primarily using the json-based component.
• When using inline componentns, if a component at any dom level should not be displayed for a specific language, simply add a void language tag for that language at that dom level.
• Generally avoid using multiple of the same language tags at the same dom level when using the inline component, as it may not behave as you expect if you omit any of the language tags listed in the languages list.
• To use a language of one LanguageProvider within the scope of another LanguageProvider, use the useLanguage hook.
• If you are using components that iterate over components, avoid using this library's inline components due to their recursive nature (creating a LanguageDisplay component inbetween each dom layer). See the following code for an example.

1// DO NOT DO => (because it will most likely lead to incorrect behaviour of your child-iterating component)
2<LanguageDisplay>
3  <Carousel>
4    <div>
5      <en>English language content</en>
6      <de>German language content</de>
7      <jp>Japanese language content</jp>
8    </div>
9    <div>
10      {/*...*/}
11    </div>
12  </Carousel>
13</LanguageDisplay>
14// Because this library will generate the following:
15<LanguageDisplay>
16  <Carousel>
17    <LanguageDisplay>
18      <div>
19        <LanguageDisplay>
20          <en>English language content</en>
21          <de>German language content</de>
22          <jp>Japanese language content</jp>
23        </LanguageDisplay>
24      </div> 
25      <div>
26        <LanguageDisplay>
27          {/*...*/}
28        </LanguageDisplay>
29      </div>
30      </LanguageDisplay>
31  </Carousel>
32</LanguageDisplay>
33
34// Optimally you should use the LanguageText component in this case or a custom mapping using the useLanguage hook or simply make sure that LanguageDisplay primarily wraps language tags:
35<Carousel>
36  <div>
37    <LanguageDisplay>
38      <en>English language content</en>
39      <de>German language content</de>
40      <jp>Japanese language content</jp>
41    </LanguageDisplay>
42  </div>
43  <div>
44      {/*...*/}
45  </div>
46</Carousel>

Future Features

• JSON-based select component (void element LanguageSelect)
• External JSON-fetching
• UserAgent / browser language preset

Version History

1.0.13 useLanguage JSON parse error

• Fixed a json.parse() crash-causing bug.

1.0.12 useLanguage SSR Fix

• Fixed a bug that caused useLanguage to cause a crash when called in specific situations.

1.0.11 useLanguage Fix

• Fixed a bug causing useLanguage to continually send storage updates causing a "max render update depth exceeded" error.

1.0.10 Quickfixed SSR Support

1.0.9 Now supports SSR

1.0.8 getContent defaultTo Bugfix

• Fixed a bug where the app would crash if the defaultTo language would be used when calling useLanguage.getContent()

1.0.7 Quickfixed the Quickfix

1.0.6 getContent Quickfix

1.0.5 Hook Content Getter and Setter

• Made content accessible through the hook via

1const lang = useLanguage("[id]")
2lang.getContent("[name]")
3lang.setContent(
4  "[name]", 
5  {
6    en: "[english content]", 
7    de: "[german content]"
8  }
9)

1.0.4 Package and Readme Updates

• Added keywords.
• Updated usage notes.
• Added version history.

1.0.3 Quickfix

• Removed leftover console logs.

1.0.2 Major Fixes

• Fixed defaultTo bug when using json component.
• Fixed a bug causing children of LanguageDisplay and LanguageSelect to lose their properties.
• LanguageText now throws an error when no name-property is passed to it.

1.0.1 Readme Fixes

1.0.0 Original Release

Containing

• useLanguage
• inline components: LanguageDisplay, LanguageSelect
• json component: LanguageText
• LanguageContext and LanguageProvider (mandatory to use)

License

MIT © ZJVieth