Zompist Bboard Again

Darren wrote: ↑Sat Mar 02, 2024 7:05 pm

bradrn wrote: ↑Sat Mar 02, 2024 7:03 pm While trying to implement some new features, I realised I’m confused by this statement:

Darren wrote: ↑Sat Jan 27, 2024 6:03 pm 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.

It's a minor inconvenience at worst.

bradrn wrote: ↑Sat Mar 02, 2024 7:09 pm Hmm… surely it should only give question marks if there’s another category declaration afterwards?

Darren wrote: ↑Sat Mar 02, 2024 7:39 pm

bradrn wrote: ↑Sat Mar 02, 2024 7:09 pm 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 wrote: ↑Sat Mar 02, 2024 7:46 pm

Darren wrote: ↑Sat Mar 02, 2024 7:39 pm

bradrn wrote: ↑Sat Mar 02, 2024 7:09 pm 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 wrote: ↑Sat Jan 27, 2024 6:03 pm 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.

bradrn wrote: ↑Fri May 10, 2024 7:11 am

Darren wrote: ↑Sat Jan 27, 2024 6:03 pm 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 wrote: ↑Fri May 10, 2024 7:31 pm

bradrn wrote: ↑Fri May 10, 2024 7:11 am

Darren wrote: ↑Sat Jan 27, 2024 6:03 pm 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 wrote: ↑Sat May 11, 2024 4:10 am

Darren wrote: ↑Fri May 10, 2024 7:31 pm

bradrn wrote: ↑Fri May 10, 2024 7:11 am

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!

• 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

• 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

• I don't have a → key on my keyboard, but I do have programming fonts installed which include a -> ligature. Would it be possible to recognise the -> digraph to separate the input and output as well?
• I was trying to implement a toy version of a Northern Vanuatu-style sound change (where unstressed vowels disappear, influencing the vowel in the preceding syllable to massively increase the vowel inventory of a language).

  [o u] / [ø y] / _ C Frnt
  [i y e ø o u] / [e ø ɛ œ ɔ o] / _ C [V -Open]
  a / [ɛ ɔ] / _ C Open
  V / / _ #

  This results in an ambiguity where it thinks words like tati and tatu could both end up as either tɛt and tɔt, rather than tati becoming tɛt and tatu becoming tɔt. I can fix this by breaking rule 3 into two rules, one for aCi and one for aCu, but that feels wrong. I tried a backreference and I think I managed to crash the parser, since I got "exit with exit code 1" and then it wouldn't work until I refreshed the browser window. Is there another way to do what I want here that I missed in the documentation?

Ketsuban wrote: ↑Fri May 24, 2024 11:24 pm

• I was trying to implement a toy version of a Northern Vanuatu-style sound change (where unstressed vowels disappear, influencing the vowel in the preceding syllable to massively increase the vowel inventory of a language).

  [o u] / [ø y] / _ C Frnt
  [i y e ø o u] / [e ø ɛ œ ɔ o] / _ C [V -Open]
  a / [ɛ ɔ] / _ C Open
  V / / _ #

  This results in an ambiguity where it thinks words like tati and tatu could both end up as either tɛt and tɔt, rather than tati becoming tɛt and tatu becoming tɔt. I can fix this by breaking rule 3 into two rules, one for aCi and one for aCu, but that feels wrong. I tried a backreference and I think I managed to crash the parser, since I got "exit with exit code 1" and then it wouldn't work until I refreshed the browser window. Is there another way to do what I want here that I missed in the documentation?

a C [i u] / @2 [ɛ ɔ] @1 C @2 [i u]

Ketsuban wrote: ↑Fri May 24, 2024 11:24 pm

• I don't have a → key on my keyboard, but I do have programming fonts installed which include a -> ligature. Would it be possible to recognise the -> digraph to separate the input and output as well?

I was trying to implement a toy version of a Northern Vanuatu-style sound change (where unstressed vowels disappear, influencing the vowel in the preceding syllable to massively increase the vowel inventory of a language).

[o u] / [ø y] / _ C Frnt
[i y e ø o u] / [e ø ɛ œ ɔ o] / _ C [V -Open]
a / [ɛ ɔ] / _ C Open
V / / _ #

This results in an ambiguity where it thinks words like tati and tatu could both end up as either tɛt and tɔt, rather than tati becoming tɛt and tatu becoming tɔt. I can fix this by breaking rule 3 into two rules, one for aCi and one for aCu, but that feels wrong.

I tried a backreference and I think I managed to crash the parser, since I got "exit with exit code 1"

bradrn wrote: ↑Sat May 25, 2024 4:18 am

I tried a backreference and I think I managed to crash the parser, since I got "exit with exit code 1"

Now this shouldn’t happen at all: I’ve never managed to crash Brassica. What sound change did you enter that triggered this?

Ketsuban wrote: ↑Sat May 25, 2024 5:21 am

bradrn wrote: ↑Sat May 25, 2024 4:18 am

I tried a backreference and I think I managed to crash the parser, since I got "exit with exit code 1"

Now this shouldn’t happen at all: I’ve never managed to crash Brassica. What sound change did you enter that triggered this?

a / @1 [ɛ ɔ] / _ C @1 Open

Ketsuban wrote: ↑Fri May 24, 2024 11:24 pm

• I don't have a → key on my keyboard, but I do have programming fonts installed which include a -> ligature. Would it be possible to recognise the -> digraph to separate the input and output as well?

Man in Space wrote: ↑Mon Jul 08, 2024 10:44 pm Thank you for all your hard work on this resource most valuable.

bradrn wrote: ↑Sat May 11, 2024 5:29 am

• Allow recognising combining diacritics as forming automatic multigraphs

Darren wrote: ↑Sat Jan 27, 2024 5:44 pm It's intuitive enough; or at least, it's not counterintuitive – with the guide it's easily usable even for me. I have had trouble getting it to understand non-precomposed characters like <ɛ́ ɔ́ ɑ̃>; it keeps treating the accents separately for some reason.

bradrn wrote: ↑Mon Jul 15, 2024 5:48 pm Given the above logic, I’m curious to know what your specific problem was, and why writing out the categories wasn’t enough to solve it?