Update Create Workset For Linked Element by Denver-22 · Pull Request #3031 · pyrevitlabs/pyRevit

Denver-22 · 2026-01-24T06:53:00Z

Update Create Workset For Linked Element

Added translations (translations.json).
Reverted the "ZL_" prefix to the names of created Worksets.

Description

About translations:
In earlier commits, I added translations to the scripts themselves. However, this is not an optimal solution.
Then I moved the translations to the translations.json file. If this approach to translating messages in the script suits you and can be used as a template for translations in other scripts, I suggest moving the get_translations() function to the pyrevitlib\pyrevit\script.py script.

P.S.:
Sync with pyRevit has been added to the commit list. I hope this won't be a problem.

Update Create Workset For Linked Element - config.py: - Added translations - Reverted the "ZL_" prefix to the name of created Worksets

Update Create Workset For Linked Element: - Added translations

Update Create Workset For Linked Element - script.py: - Translations for both scripts saved to the translations.json file.

Update Create Workset For Linked Element - config.py: - Translations for both scripts have been saved to the translations.json file. - Fixed a bug I introduced earlier in the variable names.

Create translations.json for Create Workset For Linked Element (script, config)

devloai · 2026-01-24T06:53:03Z

Unable to trigger custom agent "Code Reviewer"You have run out of credits 😔
Please upgrade your plan or buy additional credits from the subscription page.

Fix russian translation

jmcouffin · 2026-01-24T08:33:25Z

Thanks @Denver-22 , I appreciate the effort.
In order to be more consistant here, please use this approach for translations (GH copilot generated instruction, I hope you are not offended 😸 ):

Details

Implementation Strategy for Localization

The forms module already has a foundation for localization through the WPFWindow._determine_xaml() method. Here's a comprehensive approach:

1. Localization Architecture Overview

The existing pattern already supports:

Default locale: en_us (English - US)
ResourceDictionary pattern: Separate XAML files for translations
Fallback mechanism: Localized → English → Base XAML

2. Implementation Details

File Naming Convention (Already in use)

For any XAML file, create language-specific ResourceDictionary files:

YourWindow.xaml  (base, no hardcoded strings)
YourWindow.ResourceDictionary.en_us.xaml  (English - default)
YourWindow.ResourceDictionary.fr_fr.xaml  (French)
YourWindow.ResourceDictionary.es_es.xaml  (Spanish)
YourWindow.ResourceDictionary.de_de.xaml  (German)
YourWindow.ResourceDictionary.ru.xaml     (Russian)
YourWindow.ResourceDictionary.chinese_s.xaml  (Simplified Chinese)

Base XAML Structure (Non-breaking)

```xml
<Window xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        Title="{DynamicResource WindowTitle}">
    <StackPanel>
        <TextBlock Text="{DynamicResource WelcomeMessage}" />
        <Button Content="{DynamicResource OkButton}" />
    </StackPanel>
</Window>
```

English ResourceDictionary (Default)

```xml
<ResourceDictionary
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:system="clr-namespace:System;assembly=mscorlib">

    <!-- Window Properties -->
    <system:String x:Key="WindowTitle">Example Window</system:String>
    
    <!-- UI Strings -->
    <system:String x:Key="WelcomeMessage">Welcome to pyRevit!</system:String>
    <system:String x:Key="OkButton">OK</system:String>
    
    <!-- Tooltips -->
    <system:String x:Key="OkButton.Tooltip">Click to confirm</system:String>
    
</ResourceDictionary>
```

French ResourceDictionary

```xml
<ResourceDictionary
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:system="clr-namespace:System;assembly=mscorlib">

    <system:String x:Key="WindowTitle">Fenêtre d'exemple</system:String>
    <system:String x:Key="WelcomeMessage">Bienvenue sur pyRevit!</system:String>
    <system:String x:Key="OkButton">OK</system:String>
    <system:String x:Key="OkButton.Tooltip">Cliquez pour confirmer</system:String>
    
</ResourceDictionary>
```

3. How the Existing System Works (No changes needed)

The WPFWindow class already handles this automatically:

def _determine_xaml(self, xaml_source):
    # ... existing code ...
    
    # Gets user_config.user_locale (e.g., "fr_fr")
    localized_xaml_resfile = xaml_file.replace(
        ".xaml", ".ResourceDictionary.{}.xaml".format(user_config.user_locale)
    )
    
    # Tries localized, then English, then base
    if os.path.isfile(localized_xaml_resfile):
        self.merge_resource_dict(localized_xaml_resfile)
    elif os.path.isfile(english_xaml_resfile):
        self.merge_resource_dict(english_xaml_resfile)
    
    return xaml_file

4. Migration Guide for Existing Forms (Non-breaking)

Step 1: Extract hardcoded strings from existing XAML
Step 2: Create ResourceDictionary files
Step 3: Update XAML to use DynamicResource

Before (hardcoded):

<Button Content="Select All" />

After (localized):

<Button Content="{DynamicResource SelectAllButton}" />

5. Accessing Localized Strings in Python Code

The WPFWindow class provides a method:

class MyWindow(forms.WPFWindow):
    def __init__(self):
        forms.WPFWindow.__init__(self, 'MyWindow.xaml')
        
        # Get localized string programmatically
        ok_text = self.get_locale_string("OkButton")
        
        # Use it
        self.status_tb.Text = ok_text

6. Best Practices

Key Naming Convention:

ComponentName.PropertyType

Examples:
SelectAllButton              # Button content
SelectAllButton.Tooltip      # Tooltip text
CategorySelection.Label      # Section label
ErrorMessage.FileNotFound    # Error messages

Fallback Strategy (already implemented):
- User's locale (e.g., fr_fr)
- English (en_us)
- Base XAML (if strings exist there)
Supporting new languages:
- Just add a new .ResourceDictionary.{locale}.xaml file
- No code changes required
- Users set user_config.user_locale

7. Backwards Compatibility ✅

No breaking changes because:

Existing XAMLs without ResourceDictionaries still work
ResourceDictionaries are optional enhancements
The system gracefully falls back to base XAML
user_config.user_locale defaults to en_us

8. Example: Migrating SelectFromList.xaml

Create localization files based on the ColorSplasher pattern (which already exists in the codebase):

```xml
<ResourceDictionary
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:system="clr-namespace:System;assembly=mscorlib">

    <system:String x:Key="SelectButton">Select</system:String>
    <system:String x:Key="CheckAllButton">Check All</system:String>
    <system:String x:Key="UncheckAllButton">Uncheck All</system:String>
    <system:String x:Key="ToggleAllButton">Toggle All</system:String>
    <system:String x:Key="ResetButton">Reset</system:String>
    <system:String x:Key="SearchPlaceholder">Search...</system:String>
    
</ResourceDictionary>
```

Summary

The forms module already supports localization through the existing _determine_xaml() mechanism. To add multi-language support:

✅ Keep base XAML with {DynamicResource} bindings
✅ Create .ResourceDictionary.{locale}.xaml files for each language
✅ Use the ColorSplasher pattern as a reference implementation
✅ No code changes needed - it's all configuration
✅ 100% backwards compatible - existing forms continue to work
✅ Defaults to en_us - English is always the fallback

Yes, the localization system works for all forms module helpers including SelectFromList, CommandSwitchWindow, GetValueWindow, etc. Let me show you how:

How Localization Works for Forms Module HelpersPerfect! Now I can give you a complete answer. Yes, the localization system works perfectly for the forms module helpers like `SelectFromList`! Here's exactly how:

How Localization Works for Built-in Forms Helpers

Current State of SelectFromList.xaml

Looking at the current SelectFromList.xaml, it has hardcoded English text:

<TextBlock x:Name="ctx_groups_title_tb" ... >List Group:</TextBlock>
<Button x:Name="checkall_b" Content="Check" ... />
<Button x:Name="uncheckall_b" Content="Uncheck" ... />
<Button x:Name="toggleall_b" Content="Toggle" ... />
<Button x:Name="reset_b" Content="Reset" ... />

How to Add Localization Support

Step 1: Modify SelectFromList.xaml to use DynamicResource

```xml
<Window xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        ShowInTaskbar="False"
        WindowStartupLocation="CenterScreen"
        HorizontalContentAlignment="Center">
    <Window.Resources>
        <!-- ... existing resources ... -->
    </Window.Resources>
    <DockPanel Margin="10">
        <StackPanel DockPanel.Dock="Top" Margin="0,0,0,10">
            <DockPanel>
                <ToggleButton x:Name="regexToggle_b" 
                              ToolTip="{DynamicResource SelectFromList.RegexToggle.Tooltip}"
                              Content="{StaticResource filterIcon}" ... />
                <StackPanel>
                    <TextBox x:Name="search_tb" Height="25" ... />
                    <!-- ... clear search button ... -->
                </StackPanel>
            </DockPanel>
            <DockPanel x:Name="ctx_groups_dock" Margin="0,10,0,0" Visibility="Collapsed">
                <TextBlock x:Name="ctx_groups_title_tb" FontSize="14" Margin="0,3,10,0"
                           DockPanel.Dock="Left" 
                           Text="{DynamicResource SelectFromList.GroupSelector.Label}" />
                <ComboBox x:Name="ctx_groups_selector_cb" Height="25"/>
            </DockPanel>
        </StackPanel>
        <StackPanel DockPanel.Dock="Bottom">
            <Grid x:Name="checkboxbuttons_g">
                <!-- ... grid definitions ... -->
                <Button x:Name="checkall_b" 
                        Content="{DynamicResource SelectFromList.CheckAll.Button}" 
                        Click="check_all" ... />
                <Button x:Name="uncheckall_b" 
                        Content="{DynamicResource SelectFromList.UncheckAll.Button}" 
                        Click="uncheck_all" ... />
                <Button x:Name="toggleall_b" 
                        Content="{DynamicResource SelectFromList.ToggleAll.Button}" 
                        Click="toggle_all" ... />
                <Button x:Name="reset_b"
                        Content="{DynamicResource SelectFromList.Reset.Button}" 
                        Click="button_reset" ... />
            </Grid>
            <!-- Note: select_b.Content is set dynamically in Python, handled separately -->
            <Button x:Name="select_b" Content="" Height="32" Click="button_select" ... />
        </StackPanel>
        <!-- ... rest of the form ... -->
    </DockPanel>
</Window>
```

Step 2: Create English ResourceDictionary

```xml
<ResourceDictionary
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:system="clr-namespace:System;assembly=mscorlib">

    <!-- Group Selector -->
    <system:String x:Key="SelectFromList.GroupSelector.Label">List Group:</system:String>
    
    <!-- Buttons -->
    <system:String x:Key="SelectFromList.CheckAll.Button">Check All</system:String>
    <system:String x:Key="SelectFromList.UncheckAll.Button">Uncheck All</system:String>
    <system:String x:Key="SelectFromList.ToggleAll.Button">Toggle All</system:String>
    <system:String x:Key="SelectFromList.Reset.Button">Reset</system:String>
    <system:String x:Key="SelectFromList.Select.Button">Select</system:String>
    
    <!-- Dynamic button labels (when filtered) -->
    <system:String x:Key="SelectFromList.Check.Button">Check</system:String>
    <system:String x:Key="SelectFromList.Uncheck.Button">Uncheck</system:String>
    <system:String x:Key="SelectFromList.Toggle.Button">Toggle</system:String>
    
    <!-- Tooltips -->
    <system:String x:Key="SelectFromList.RegexToggle.Tooltip">Toggle between using regular expression and fuzzy filtering</system:String>
    
</ResourceDictionary>
```

Step 3: Create French ResourceDictionary

```xml
<ResourceDictionary
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:system="clr-namespace:System;assembly=mscorlib">

    <!-- Group Selector -->
    <system:String x:Key="SelectFromList.GroupSelector.Label">Groupe de Liste:</system:String>
    
    <!-- Buttons -->
    <system:String x:Key="SelectFromList.CheckAll.Button">Tout Cocher</system:String>
    <system:String x:Key="SelectFromList.UncheckAll.Button">Tout Décocher</system:String>
    <system:String x:Key="SelectFromList.ToggleAll.Button">Basculer Tout</system:String>
    <system:String x:Key="SelectFromList.Reset.Button">Réinitialiser</system:String>
    <system:String x:Key="SelectFromList.Select.Button">Sélectionner</system:String>
    
    <!-- Dynamic button labels (when filtered) -->
    <system:String x:Key="SelectFromList.Check.Button">Cocher</system:String>
    <system:String x:Key="SelectFromList.Uncheck.Button">Décocher</system:String>
    <system:String x:Key="SelectFromList.Toggle.Button">Basculer</system:String>
    
    <!-- Tooltips -->
    <system:String x:Key="SelectFromList.RegexToggle.Tooltip">Basculer entre l'utilisation d'expressions régulières et le filtrage flou</system:String>
    
</ResourceDictionary>
```

Step 4: Handle Dynamic Python Text

Looking at the Python code in SelectFromList._list_options():

def _list_options(self, option_filter=None):
    if option_filter:
        self.checkall_b.Content = "Check"      # Dynamic text!
        self.uncheckall_b.Content = "Uncheck"  # Dynamic text!
        self.toggleall_b.Content = "Toggle"    # Dynamic text!

These need to be updated to use localized strings:

def _list_options(self, option_filter=None):
    if option_filter:
        # Use get_locale_string to fetch from ResourceDictionary
        self.checkall_b.Content = self.get_locale_string("SelectFromList.Check.Button")
        self.uncheckall_b.Content = self.get_locale_string("SelectFromList.Uncheck.Button")
        self.toggleall_b.Content = self.get_locale_string("SelectFromList.Toggle.Button")
    else:
        self.checkall_b.Content = self.get_locale_string("SelectFromList.CheckAll.Button")
        self.uncheckall_b.Content = self.get_locale_string("SelectFromList.UncheckAll.Button")
        self.toggleall_b.Content = self.get_locale_string("SelectFromList.ToggleAll.Button")

Similarly, in _setup():

def _setup(self, **kwargs):
    # custom button name?
    button_name = kwargs.get("button_name", None)
    if button_name:
        self.select_b.Content = button_name
    else:
        # Use localized default
        self.select_b.Content = self.get_locale_string("SelectFromList.Select.Button")
    
    # ... rest of setup ...

Step 5: Update ctx_groups_title_tb dynamically

def _setup(self, **kwargs):
    # ... existing code ...
    
    # context group title?
    self.ctx_groups_title = kwargs.get(
        "group_selector_title", 
        self.get_locale_string("SelectFromList.GroupSelector.Label")  # Localized default
    )
    self.ctx_groups_title_tb.Text = self.ctx_groups_title

Complete Example of How It All Works Together

User's Locale is French (`user_config.user_locale = "fr_fr"`)

User calls SelectFromList:

from pyrevit import forms

items = ['item1', 'item2', 'item3']
selected = forms.SelectFromList.show(
    items, 
    multiselect=True,
    button_name='Sélectionner les Éléments'  # Can override
)

WPFWindow loads XAML:
- Checks for SelectFromList.fr_fr.xaml → Not found
- Checks for SelectFromList.en_us.xaml → Not found
- Checks for SelectFromList.ResourceDictionary.fr_fr.xaml → Found!
- Merges it into the window resources
- Loads base SelectFromList.xaml
XAML bindings resolve:
- {DynamicResource SelectFromList.CheckAll.Button} → "Tout Cocher"
- {DynamicResource SelectFromList.GroupSelector.Label} → "Groupe de Liste:"

Python code accesses strings:

self.get_locale_string("SelectFromList.Check.Button")  # Returns "Cocher"

Summary: It Works Seamlessly! ✅

Component	Localization Method	Non-Breaking?
Static XAML text	`{DynamicResource KeyName}`	✅ Yes - base XAML still works if no ResourceDict
Dynamic Python text	`self.get_locale_string("KeyName")`	✅ Yes - can add try/except or default fallback
User-provided text	Pass through `kwargs`	✅ Yes - user text always takes precedence
File loading	Automatic via `_determine_xaml()`	✅ Yes - already implemented!

The forms module already has everything needed to support localization. You just need to:

Create the .ResourceDictionary.{locale}.xaml files
Update XAML to use {DynamicResource} instead of hardcoded text
Update Python code to use self.get_locale_string() for dynamic text
No breaking changes - everything falls back gracefully!

Renamed keys in translations.json to comply with convention.

- Renamed keys in translations.json to comply with convention. - Some optimizations.

Denver-22 · 2026-01-24T09:36:29Z

@jmcouffin
I've reviewed your proposal.
In principle, I'm not against it. And I probably would have done it that way from the start.
However, the script uses translations not only for WPFWindow class forms, but also for forms.alert(), the transaction name, and the if statement, for which XAML translations are not applicable.
Then I'll have to separate translations not only by language for SelectFromList but also keep translations.json for other cases. This means that eliminating the use of translations.json (and the function for reading it, get_translations()) won't be possible.
If you think this is desirable in any case, I suggest implementing it in the next PR.

jmcouffin · 2026-01-25T14:13:44Z

@Denver-22 thks,
I agree to disagree 🤣

github-actions · 2026-01-25T14:29:45Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26025+1418-wip

github-actions · 2026-01-30T20:49:46Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26030+2037-wip

github-actions · 2026-01-30T20:50:25Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26030+2039-wip

github-actions · 2026-01-30T21:15:13Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26030+2101-wip

github-actions · 2026-01-30T21:48:14Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26030+2136-wip

github-actions · 2026-01-30T22:01:26Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26030+2147-wip

github-actions · 2026-01-30T22:23:25Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26030+2212-wip

github-actions · 2026-02-01T10:55:39Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1043-wip

github-actions · 2026-02-01T11:23:26Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1111-wip

github-actions · 2026-02-01T13:16:26Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1304-wip

github-actions · 2026-02-01T13:35:48Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1323-wip

github-actions · 2026-02-01T14:48:04Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1433-wip

github-actions · 2026-02-01T15:49:55Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1538-wip

github-actions · 2026-02-01T15:56:23Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1543-wip

github-actions · 2026-02-01T16:05:11Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1553-wip

github-actions · 2026-02-01T16:24:15Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1612-wip

github-actions · 2026-02-01T16:38:27Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1624-wip

github-actions · 2026-02-01T17:50:08Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1738-wip

github-actions · 2026-02-01T17:56:10Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1743-wip

github-actions · 2026-02-01T18:44:47Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1829-wip

github-actions · 2026-02-01T19:50:15Z

📦 New work-in-progress (wip) builds are available for 5.3.1.26032+1937-wip

github-actions · 2026-02-01T20:07:58Z

📦 New work-in-progress (wip) builds are available for 6.0.0.26032+1956-wip

github-actions · 2026-02-01T20:16:35Z

📦 New work-in-progress (wip) builds are available for 6.0.0.26032+2005-wip

github-actions · 2026-02-01T20:20:22Z

📦 New work-in-progress (wip) builds are available for 6.0.0.26032+2008-wip

github-actions · 2026-02-01T20:24:28Z

📦 New public release are available for 6.0.0.26032+2040

github-actions · 2026-02-01T20:35:05Z

📦 New public release are available for 6.0.0.26032+2040

Denver-22 added 6 commits January 24, 2026 08:37

Update Create Workset For Linked Element - config.py

da80d7d

Update Create Workset For Linked Element - config.py: - Added translations - Reverted the "ZL_" prefix to the name of created Worksets

Update Create Workset For Linked Element

7960e97

Update Create Workset For Linked Element: - Added translations

Merge branch 'pyrevitlabs:develop' into develop

bbd87e7

Update Create Workset For Linked Element - script.py

6859ed2

Update Create Workset For Linked Element - script.py: - Translations for both scripts saved to the translations.json file.

Update Create Workset For Linked Element - config.py

d4e551e

Update Create Workset For Linked Element - config.py: - Translations for both scripts have been saved to the translations.json file. - Fixed a bug I introduced earlier in the variable names.

Create translations.json

eed19b5

Create translations.json for Create Workset For Linked Element (script, config)

Update translations.json

96244fd

Fix russian translation

Denver-22 added 3 commits January 24, 2026 12:34

Update Create Workset For Linked Element - translations.json

016c388

Renamed keys in translations.json to comply with convention.

Update Create Workset For Linked Element - script.py

31fc4cd

- Renamed keys in translations.json to comply with convention. - Some optimizations.

Update Create Workset For Linked Element - config.py

bdee2c8

- Renamed keys in translations.json to comply with convention. - Some optimizations.

jmcouffin merged commit 17a6fa9 into pyrevitlabs:develop Jan 25, 2026

jmcouffin self-assigned this Jan 25, 2026

jmcouffin added the Localization Issues related to pyRevit localization [subsystem] label Jan 25, 2026

Uh oh!

Conversation

Denver-22 commented Jan 24, 2026

Description

Uh oh!

devloai bot commented Jan 24, 2026

Uh oh!

jmcouffin commented Jan 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Implementation Strategy for Localization

1. Localization Architecture Overview

2. Implementation Details

File Naming Convention (Already in use)

Base XAML Structure (Non-breaking)

English ResourceDictionary (Default)

French ResourceDictionary

3. How the Existing System Works (No changes needed)

4. Migration Guide for Existing Forms (Non-breaking)

5. Accessing Localized Strings in Python Code

6. Best Practices

7. Backwards Compatibility ✅

8. Example: Migrating SelectFromList.xaml

Summary

How Localization Works for Forms Module HelpersPerfect! Now I can give you a complete answer. Yes, the localization system works perfectly for the forms module helpers like SelectFromList! Here's exactly how:

How Localization Works for Built-in Forms Helpers

Current State of SelectFromList.xaml

How to Add Localization Support

Step 1: Modify SelectFromList.xaml to use DynamicResource

Step 2: Create English ResourceDictionary

Step 3: Create French ResourceDictionary

Step 4: Handle Dynamic Python Text

Step 5: Update ctx_groups_title_tb dynamically

Complete Example of How It All Works Together

User's Locale is French (user_config.user_locale = "fr_fr")

Summary: It Works Seamlessly! ✅

Uh oh!

Denver-22 commented Jan 24, 2026

Uh oh!

jmcouffin commented Jan 25, 2026

Uh oh!

github-actions bot commented Jan 25, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

Uh oh!

jmcouffin commented Jan 24, 2026 •

edited

Loading

How Localization Works for Forms Module HelpersPerfect! Now I can give you a complete answer. Yes, the localization system works perfectly for the forms module helpers like `SelectFromList`! Here's exactly how:

User's Locale is French (`user_config.user_locale = "fr_fr"`)