BloomDesktop: Command for GitHub Copilot

This project uses the following methods to make strings localizable in react components:

• use an l10n-aware component such as My Text, My Text, etc.
• useL10n("My Text", "myKey") — note the order: the English text first, then the id

There should be a selected line with a string. If there is not, stop and tell me that I have to select a line with a string to be localized.

Wrapping the string

If the string is already wrapped in a l10n-aware component or useL10n, go on to the XLF portion of these instructions. Otherwise, wrap it in useL10n2(). Or useL10n(english, id).

// somewhere in Foobar dialog
<button>Brighten everything</button>

to this:

import { useL10n } from "../../react_components/l10nHooks";
// somewhere in Foobar dialog
<button>{useL10n("Brighten everything", "FoobarDialog.BrightenEverything")}</button>

The import above will need the correct path relative to the current file. The file lives at src/BloomBrowserUI/react_components/l10nHooks.ts.

• Normally, don't fill in l10nComment parameter when using useL10n, that just clutters the code. We will put context in the xlf file instead. However if you want to use the later parameters, then you have to put something in that parameter.

Adding to XLF files

For each string, we have to have a matching record in one of the xlf files in the DistFiles/localization/en folder. There are high (DistFiles/localization/en/Bloom.xlf), medium (DistFiles/localization/en/BloomMediumPriority.xlf), and low (DistFiles/localization/en/BloomLowPriority.xlf) priority options. Check all three xlf files for a matching record. If you find it, tell me where it is. If you don't find it, stop and ask me which priority I want with numbers so I can respond 1 (high), 2 (medium), or 3 (low). Then create the record in the appropriate file, placing the record next to similar records. For example, here we would want to group the FoobarDialog records together.