Ukelele 3.6b6

[John Brownie]

I’ve finally got everything together to release a new beta version, 3.6b6. It has the following changes:

• The bundle name was not set when initially creating a keyboard layout collection, leading to unexpected file names. This is fixed.
• The metadata about a keyboard layout was only being written when a language was specified. Now it is written if any value (language, template icon or caps lock switching) is given.
• The private use language range was not handled correctly, using the range rather than specific values for the code. This is now handled properly, and you will be asked which code to use if you select the private use range.
• There is now an option on the Keyboard menu to export an inventory of the outputs produced by the keyboard layout. This generates a CSV file which can be opened by a spreadsheet program or as a table in a word processor, allowing you to sort in any way. The table has columns for output, the Unicode code points of the output, the keys pressed and the keys pressed by key code.

It should be available via Software Update or at https://software.sil.org/ukelele/.

John

[Sorin Paliga]

Thank you, John, for your constant improving this wonderful app

On 13 Aug 2025, at 11:07, 'John Brownie' via Ukelele Users <ukelel...@googlegroups.com> wrote:



--
You received this message because you are subscribed to the Google Groups "Ukelele Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukelele-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ukelele-users/CAC13VMyAvDgoAUK6SyaktNHh71pxC-Lr%3DdJo1EQ-g5ZnkqzPQw%40mail.gmail.com.

[Gé van Gasteren]

I’ve just updated from within Ukelele, all is wonderful with the new output list, thanks a lot!

I did have some trouble there with Microsoft Excel:

When I import the .csv file in Excel, it doesn’t go through the "tweak the importing conversion" sequence and everything comes out wrong.

After changing the file extension to .txt, Excel does display the dialog for setting the importing parameters and things work out, as long as choose the right options:

Delimited and File Origin: UTF-8 in the first panel, and Comma as delimiter in the next panel.

In Apple’s Numbers, the .csv file opens correctly right away and nicely formatted, too.

--

[John Brownie]

On 13 Aug 2025 at 13:10:40, Gé van Gasteren <gevang...@gmail.com> wrote:

I’ve just updated from within Ukelele, all is wonderful with the new output list, thanks a lot!

I did have some trouble there with Microsoft Excel:

When I import the .csv file in Excel, it doesn’t go through the "tweak the importing conversion" sequence and everything comes out wrong.

After changing the file extension to .txt, Excel does display the dialog for setting the importing parameters and things work out, as long as choose the right options:

Delimited and File Origin: UTF-8 in the first panel, and Comma as delimiter in the next panel.

In Apple’s Numbers, the .csv file opens correctly right away and nicely formatted, too.

I haven’t used Excel in a long time, so hadn’t checked. It seems that this is a long-standing issue with Excel, that it assumes MacRoman as the character encoding.

Checking online, people suggested that the Import Wizard would work. If you do that (create an empty spreadsheet, then Import from the File menu), you get the option to say it’s UTF-8 and comma-separated, but then it gets it wrong with the rows that contain a carriage return (U+000D) or line feed (U+000A), despite them being quoted correctly.

There’s no good solution to this problem, as far as I know. One would be to change the actual output to some other representation, such as XML or code point format, though that sort of breaks the model. If anyone has a better idea, let me know!

It does also work correctly in LibreOffice, which shows the options when you open the file. Numbers is still the easiest way to use it.

John

[Gé van Gasteren]

You actually looked into it!

My take was that Microsoft users are – probably – used to that kind of stuff, so they’ll figure out a way to do it, just as I did.

And with the procedure you described I do get the Wizard upon importing the .csv file. 

I had made the "mistake" of opening it from the Finder :-)

Right, I hadn’t seen the errors at CR and LF but Excel does go wrong there – as TextEdit, in fact.

Maybe it wouldn’t be a big loss to skip those two?

--

You received this message because you are subscribed to the Google Groups "Ukelele Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukelele-user...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/ukelele-users/CAC13VMwnqY2SvvckhmnHSDvEzUWu_TdVq3_kh5tNiVaA%3DEv7Ag%40mail.gmail.com.