quoting Jipí, Alkali Metal on exhibit in Victoria, Canada:

Table → Convert → Text to table → copypasta → Calc

+1 Confirmed.

Still going to take a lot of hand fixing. I've actually been working on that, it's just going to take a long while. There's multiple, multiple different numbers of tabs on various lines, sometimes multiple lines, so the table's a freaking mess.

quoting Nessari:

There's multiple, multiple different numbers of tabs on various lines, sometimes multiple lines, so the table's a freaking mess.

Before you convert to a table: Ctrl+h, click the plus sign next to “Other options”, check “Regular expressions”, search for \t\t and replace with \t. Then repeat until all tabs are single tabs.

Hey, I'm having some weird outputs from HTS, and I was hoping you could explain why it's happening, so I can figure out how to avoid these sorts of problems. Here's the rules and variables in question:

Æ  = æː  æ  æ̀ː  æ̀  æːˈ  æˈ
EA  = æːa æa  æ̀ːa æ̀ a æːˈa æˈa

EA > Æ

If it's relevant, there are also variables E and A, which follow the same schema as EA and Æ, except they have "e" and "a" in place of "æ(a)".

It is changing all the combinations with æ that I expect it to. However, [a] is becoming [æːˈ], which It shouldn't do. For instance, "lang" becoming "læːˈng" and "manij" becoming "mæːˈnij". Am I missing something obvious here?

the space.

{æ̀ a} <<<

in other words, a (EA_5) becomes æːˈ (Æ_5)

D'OH! >.< Thanks, Hallow XIII. Not sure how that space got in there.

I made an official release with a binary and everything!

This version support scripting, tab-delimited files, and conditions with `NOT` statements.


https://github.com/sfmorrigan/toolbox-sca/releases/tag/v0.1.0

I made my first Devblog post, summarizing project goals and future directions. Of course, I've probably discussed all of these issues here.

you've missed an i out of 'pernicious' on https://github.com/sfmorrigan/toolbox-sca/blob/master/README.md

Thanks. I decided to entirely rewrite that clause, "pernicious" was really not great word-choice.

So, I changed the readme on the site and re-set it in LaTeX.
SCA Manual PDF

I've been working a lot on cleaning up the code involved in using the feature models so that they won't suck. Also I have a website.

I have a serious question concerning how the SCA is started and runs:

The current situation leaves us with an uncomfortable state of affairs,  for technical reasons. The problem is that in "basic" mode, the whole rule file is parsed before loading the lexicon, so if the user messes about with normalization or segmentation flags, it's possible for the lexicon to be loaded using the wrong settings, if the user is not very careful.

I'm wondering what all of  you might prefer I do. I could remove basic mode entirely, since personally I feel like it's a lot easier to just use load statements than have to modify a batch  or shell file. Alternatively, I could change basic mode to restrict the ability to change segmentation and normalization settings.

At the very least, I think I will reduce the number of segmentation/normalization options, mostly because the majority are not necessary.  When using intelligent segmentation (the new manual will have an appendix on this), it's best to use  Canonical Decomposition1. When using no segmentation, there is really no reason to use normalization at all; it's really best to leave all inputs just as they are.

If  I make these changes, the number of options (and potential for difficulty) is reduced and it is much easier to flag on the command line. This seems like the best compromise and is what I will work toward doing soon.

Other news: I refactored the state-machine code and should be able to introduce negative conditions soon. At the very least, one will be able to negate single characters, if not entire groups.

Additionally, I'm fairly close changing the SCA to optionally use features. Unlike IPA Zounds, you will be able to mix literals like a and features like [-voiced;+continuant], since the former can simply be converted to the latter internally.

I've also been thinking about building a UI - I realize I've said in the past that I didn't see a point. Certainly for the purposes of running rule files, a UI is useless at best, and a hindrance at worst.

However there is substantial value in building what is essentially an IDE. Even something as simple as editing a rules file with syntax highlighting1, and executing the file would be a good use of a UI. But there is a lot of potential value in building this type of platform, like:

I'm looking into using JavaFX for this, but admittedly have only ever developed one relatively simple MV*-like application using JQuery and Handlebars. I suspect supporting the kinds of functionality I'd like to see would require a huge amount of work, and might detract from my ability to continue some of my research efforts, but it would be fantastic to have a platform with these capabilities.

Though it will mean cleaning up the API more, but I've been working on that and making good progress.

Guess what I finally did this morning

https://github.com/samanthamccabe/toolbox-sca/releases/tag/v0.5.0

Quick rundown:
I fixed a lot of minor bugs. Create shell scripts  / batch file to make running it easier. Changed how the program is invoked slightly. Wrote a 12 page manual, provided example files. Rewrote the regular expression engine, changed how normalization works (also, it's turned off by default).

If anyone wants it, I made a syntax hilighter in Sublime Text 3 also
http://haedus.org/releases/ToolboxSCA.tmLanguage

Woah. I've started a lexicon and some rules for a language family I'm working on, and...so elegant! so clear!

I haven't found any bugs yet, but if I do I'll let you know.


(I do have an idea for a feature that could be useful, though I don't know how easy it would be- would it be possible to tie adjacent rules together so that they run at the same time, so that you don't have to worry about their ordering? For example, I've got a vowel lowering rule in Quomonak where *i lowers to /e/ and all of *e *ɨ *o lower to /a/ before a coda *h. Normally, you have to write the rule governing *e *ɨ *o before you can write the rule governing *i, because otherwise you'll get a shift *i -> *e -> /a/. Obviously this is pretty easy to solve with judicious rule ordering or use of variables or an expanded rule set- but in more complicated cases it could be useful.)

EDIT- Wait, I'm using Windows command prompt...I have no idea what I'm doing, can someone give me a better rundown of how to open the thing?

EDIT2- What are the square brackets [ ] reserved for? They're listed as program-reserved characters, but I don't think it's mentioned in the manual what they're used for...

EDIT3- Can we do variable-to-variable transformations if the variables have the same number of segments in them? For example,

S = p t k
Z = b d g
V = a e i o u

S > Z / V_V

Is that a workable rule?

Hahah I was JUST thinking about that, because I was curious about JS Burke's Proto-Central-Mountain changes (he gave me an old copy of his rules and lexicon designed for mark's SCA) and I was curious how much more concise (and fast) it would be in my format. But I realized a bunch of his rules probably require this type of treatment. I think I know how to do that.

Ok, to run it: you should be able to just navigate to the folder it's in and run it using

toolbox.bat myrules.rule

or similar. Just make sure, when you load a lexicon, the path is either absolute (starting from the drive it's on) or relatively to where you are running the toolbox from.

Square brackets aren't reserved, per se but are parsed in a special way. They are intended for use with longer variable names, like in my Kuma-Koban examples, or phonetic features which will be supported in the next version (technically they are in THIS version, but I made it so you can't load them because I want to fix some things)

And yes, you can totally do that. I should make that more explicit in the manual.

Tried running

C:\Users\<my name>\Desktop\haedus-sca-0.5.0\toolbox.bat pq_rules.rule

and got an error message "Unable to access jarfile toolbox-sca-0.5.0.jar".

Sorry if I sound naggy- I'm just totally unfamiliar with the ins and outs of command prompt.


(EDIT:

[10:23] <dhok> I tried running
[10:23] <dhok> C:\Users\Campbell\Desktop\haedus-sca-0.5.0\toolbox.bat pq_rules.rule
[10:23] <dhok> and got an error message
[10:23] <dhok> Unable to access jarfile toolbox-sca-0.5.0.jar
[10:24] <dhok> same error message when I give it the full address of the rules file
[10:26] <H13> that is weird
[10:26] <H13> have you tried to run it from the command prompt rather than the .bat file
[10:27] <H13> also uh
[10:27] <H13> you may have to execute the batch file as admin
[10:27] <dhok> that is where I'm running it
[10:28] <H13> otherwise, use ur admin powers and give yourself normal-user execute permission
[10:28] <dhok> when I click on the batch file or run it as administrator it gives me an error message in command prompt so quickly I can't even read it before it closes

That's really weird. toolbox-sca-0.5.0.jar is in that folder right? Everything should be right there. it's very strange that it couldn't find it. You could try also running it manually with

java -jar toolbox-sca-0.5.0.jar pq_rules.rule

which is basically what the batch file does. Sorry you are having these problems, I've tested this quite extensively, so I really hope I didn't miss something.

Can't access the jarfile "toolbox-sca-0.5.0.jar". You wouldn't mind getting on #isharia, would you? It would be a great help.

• Allows insertion / epenthesis of segments (0 > e / #_sC)
• Logging to file + console
• Improved logging, including line number and file name for the script in which the error was found.
• Now attempts to log all compilation errors encountered in all loaded scripts before quitting
• Added some clarifications to the manual where users indicated some sections were unclear.

https://github.com/samanthamccabe/toolbox-sca/releases/tag/0.6.0