Zompist Bboard Again

bradrn wrote: ↑Thu Aug 08, 2024 2:27 am

Raholeun wrote: ↑Thu Aug 08, 2024 2:10 am If you need a constructive opinion on the revamped documentation, I'm glad to help.

Thanks! I was planning to post it here anyway for feedback.

Raholeun wrote: ↑Tue Aug 20, 2024 7:13 am Haven't had much time these past days, but I hope to have a look soon.

bradrn wrote: ↑Tue Aug 20, 2024 9:00 am Just let me know when you can get around to it.

θ / f ; will convert ⟨θɪn⟩→⟨fɪn⟩

ʔ / / _ [p t k b d g #]

ʔ / ~ / _ [p t k b d g #]

Raholeun wrote: ↑Wed Aug 21, 2024 4:18 am

bradrn wrote: ↑Tue Aug 20, 2024 9:00 am Just let me know when you can get around to it.

Please allow me to tackle this haphazardly. I started with the Getting Started page.

Occasionally, a sound change is followed by a commented section that illustrates how a specific item is impacted by the change. This is particularly helpful for those who are not yet familiar with the formulaic nature of sound change notation. Unfortunately, the use of examples is inconsistent. Sometimes, the input and output are provided within the code block, other times in the preceding or following text, and in some instances, no examples are given at all. It is recommended to adopt a consistent method for presenting examples. Ideally, an example should be included in the code block for every sound change demonstrated, regardless of how inane the result may appear.

Code: Select all

θ / f ; will convert ⟨θɪn⟩→⟨fɪn⟩

Likewise, the guide sometimes provides counterexamples by stating "; no change in". This is useful and you might consider using them more often.

Building on the previous point, users might sometimes struggle to understand why their sound change isn’t functioning as expected or why it’s causing an error. ncluding a section in the documentation that offers troubleshooting tips or a 'debugging guide' would be highly valuable. This could cover common mistakes, how to identify where an issue might be occurring, and steps to resolve typical errors. I guess it is preferable to empower users to diagnose and fix their issues on their own, rather than having to post here (or worse, DM you) and take up your time.

The relationship between wildcard tilde deletion and deletion via whitespace is not entirely clear to me. While the documentation introduces tilde deletion and explains the specific function it performs that whitespace deletion cannot, it doesn’t clarify whether tilde deletion can be universally applied in all scenarios where whitespace deletion is used. For example, you might want to explain why

Code: Select all

ʔ / / _ [p t k b d g #]

is or is not equivalent to

Code: Select all

ʔ / ~ / _ [p t k b d g #]

• When the replacement of the rule is blank, that simply means ‘delete the whole target’, i.e. ‘replace the target with <blank>’.
• The tilde is more complicated: it means ‘skip over the next category in the target’, which in most cases results in deletion (unless one uses backreferences or similar). It doesn’t really make sense to say ʔ / ~, because there’s no target category to skip over. The tilde is meant for cases like, say, Rounded [a e i] / ~ [ɔ ø y], where the first category in the target corresponds to no output in the replacement.

Finally, in the section about the graphical interface it is stated: "The graphical interface appears as follows (on desktop)". To me it is unclear if this implies that the web version is lacking some features mentioned. If so, what are the differences? If the web and desktop version are functionally identical, that is good to state as well.

Raholeun wrote: ↑Wed Sep 04, 2024 7:19 am When I have time, which probably will be after a deadline of mine end of Sept. I will happily give some feedback on the changes.

Darren wrote: ↑Sun Oct 13, 2024 5:43 am Some of those new changes look really neat! I like the idea of using braces within square brackets, and I like the noreplace feature, and the wildcard thingy is gonna be useful, and the report feature. I look forward to trying it out, 0.3.0 was already better than anything I know of out there.

There's one thing which I would rather like which is a random word generator using brassica format. I've always used zomp's gen, but it's clunky, can't handle digraphs and can't handle combining diacritics, and it requires explicit listing of all possible syllable types. Of course if you're too busy or plain don't want to do it that's okay but I think it would be a nice companion to Brassica and the paradigm builder.

putten

bradrn wrote: ↑Sun Oct 13, 2024 3:08 am Also: with this release, I think Brassica is mature enough to be advertised a little more widely.

bradrn wrote: ↑Sun Oct 13, 2024 8:31 am