Associatinig two colums without merging them (assigning 'root ids')

[nh36]

It can sometimes happen that we can be sure two things aren't exact cognates, but still think they are utimately related. (For example we have two words for tiger *gla and *la, and the Achange word for 'song' (something like siang) is probably related to the Burmese si-khrang (maybe as a loan). So, it would be good to be able to associate two colums without them going into the transducers as one crossid.

[LinguList]

@nh36, we had this already in the form of either the same rootid, or -- a new idea -- by using inline alignments, where you choose one as the base form for your sound change and then use the slash to convert the other virtually into the first form. Like "gl/l a" vs. "l a". So you have preserved variation but don't need to explain it. I think that is the best way to deal with these cases, as you can easily pull out all of them later and think of stories. It is also fully supported in EDICTOR's annotations as of Version 2.0, i.e., EDICTOR will treat "gl/l a" as if it is "l a".

[nh36]

Yes yes, but I am not using EDICTOR, but CAPR. I do not have access to the data, which I think it in fact correct practice, because it means I cannot make typos. Basically this is the same thing as a note (for example about loanwords) it is to flag things that should not go into FOMA together, but should live together.

[LinguList]

I know you're not using EDICTOR, but I point you to useful conventions that expand upon conventions we used in the past. I can explain later why I think these are useful.

[nh36]

N.B. we cannot use the slash in actual language data (because we want those forms that go back to *gl- to be treated accordingly when they enter the transducers) and we cannot use the slash in proto-forms because we never write down proto-forms. So, even if I wanted to use slashes, where would I put them? But yes, we can discuss later if you want.

[LinguList]

Never mind.