Brassica SCA [v0.2.0]

[bradrn]

While trying to implement some new features, I realised I’m confused by this statement:

I always end up having to make a category "X" which is just all the left over shit like ŋ kʷ pʷ ɨ ˈ θ and never gets used for anything.

If those graphemes never get used for anything, then why do you need to include them in a category in the first place?

It's the category that never gets used. When rules produce new graphemes, sometimes it doesn't mind but other times it just gives a bunch of question marks.

Hmm… surely it should only give question marks if there’s another category declaration afterwards? That was my intention, at least; if it’s not doing that, there’s a bug.

It's a minor inconvenience at worst.

Sure, but for the next version I’d like to focus on fixing these inconveniences (so I can finally release v1.0).

[Darren]

Hmm… surely it should only give question marks if there’s another category declaration afterwards?

I think you must be right. I guess I'm just too lazy to redefine all the categories at the same time.

[bradrn]

Hmm… surely it should only give question marks if there’s another category declaration afterwards?

I think you must be right. I guess I'm just too lazy to redefine all the categories at the same time.

As am I, which is why categories … end adds to the existing categories rather than clearing them (which would be new categories … end). I think the documentation is pretty clear on this point, though please let me know if it isn’t.

[Darren]

Hmm… surely it should only give question marks if there’s another category declaration afterwards?

I think you must be right. I guess I'm just too lazy to redefine all the categories at the same time.

As am I, which is why categories … end adds to the existing categories rather than clearing them (which would be new categories … end). I think the documentation is pretty clear on this point, though please let me know if it isn’t.

Hence why I use categories and add a junk category for all the new graphemes I've produced.

[bradrn]

I always end up having to make a category "X" which is just all the left over shit like ŋ kʷ pʷ ɨ ˈ θ and never gets used for anything.

Development has slowed down a lot, but finally got around to fixing this! In the next release, you’ll be able to write extra ŋ kʷ pʷ ɨ ' θ at the beginning of the file, which will tell Brassica to recognise those multigraphs as ‘extra’ characters throughout all subsequent category redefinitions.

[Darren]

I always end up having to make a category "X" which is just all the left over shit like ŋ kʷ pʷ ɨ ˈ θ and never gets used for anything.

Development has slowed down a lot, but finally got around to fixing this! In the next release, you’ll be able to write extra ŋ kʷ pʷ ɨ ' θ at the beginning of the file, which will tell Brassica to recognise those multigraphs as ‘extra’ characters throughout all subsequent category redefinitions.

Aye that's great I'll give it a crack today

[bradrn]

I always end up having to make a category "X" which is just all the left over shit like ŋ kʷ pʷ ɨ ˈ θ and never gets used for anything.

Development has slowed down a lot, but finally got around to fixing this! In the next release, you’ll be able to write extra ŋ kʷ pʷ ɨ ' θ at the beginning of the file, which will tell Brassica to recognise those multigraphs as ‘extra’ characters throughout all subsequent category redefinitions.

Aye that's great I'll give it a crack today

Note that it’s not released yet!

[Darren]

Development has slowed down a lot, but finally got around to fixing this! In the next release, you’ll be able to write extra ŋ kʷ pʷ ɨ ' θ at the beginning of the file, which will tell Brassica to recognise those multigraphs as ‘extra’ characters throughout all subsequent category redefinitions.

Aye that's great I'll give it a crack today

Note that it’s not released yet!

Ah right guess I'll have to wait

[bradrn]

For reference, this is my list of what to get done for the next release, which with luck could finally get to v1.0.0:

• Figure out some better way of handling stress, tone etc.
• Improve Brassica’s understanding of MDF dictionary files
• Allow display of intermediate results
• Get the CLI closer to feature parity with the GUI
• Improve documentation

And some things which I’ve already implemented:

• extra directive (as just mentioned)
• Up to 10× speed improvement on desktop by parallelisation
• Allow recognising combining diacritics as forming automatic multigraphs
• Wildcards can now occur in the replacement of a rule