Comments for palaso.org

Comment on XML indentation in .Net by Tim

Tim — Tue, 23 Feb 2010 02:44:29 +0000

Always the troublemaker… glad you asked of course
It seems that mono behaves identically to .net in this case except for one exception (see addendum above). But an equally large issue that I should have caught before did rear its ugly head and that is the difference between newline characters in Linux and Windows land. I changed liftIO to always output “\r\n” for newlines so all should be well now. Glad we caught that.

Comment on XML indentation in .Net by cambell

cambell — Mon, 22 Feb 2010 20:21:35 +0000

Dare I ask about the consistent / equivalent behaviour on Mono?

Comment on WeSay, Palaso, and Linux by kentling

kentling — Mon, 24 Aug 2009 13:20:18 +0000

Hey, thanks for your reflections. And thanks for your work in getting your programs working in Linux. When I consider the immensity of the work to be done on the heretofore undocumented languages of the world, and the number of people who don’t have (or the cash to buy) up to date proprietary OS/programs, linux just makes sense. So thanks; I appreciate your work.

Comment on Using SOLID to convert to one-ps-per-sense format by languist

languist — Mon, 06 Jul 2009 14:55:11 +0000

Hi John,

This latest post of yours (from the 27th) introduces
Thanks for another very useful Quick Fix, though I won’t quite be able to use it until it supports the standard hierarchy. Currently it assumes that the user is prepared to convert from standard to alternate, which seems unlikely to me.

I imagine the FLEx importer would be happy with either hierarchy as long as the \ps and \sn fields are paired up nicely together, though I’ve not tested this thoroughly.

What if instead, this Quick Fix first checked to see whether “MDF Unicode” or “MDF Alternate Unicode” was selected when the file was opened, and then:
- If standard, copy \ps down to just above each \sn.
- If alternate, copy \ps down to just below each \sn.

The current wording, “Push \ps down to subsequent \sn’s”, is ambiguous and therefore perfect.

Personally, I think that the alternative hierarchy is more intuitive and better matches FLEx. But from a theoretical standpoint, some linguists would disallow having a single sense with multiple parts of speech. They’d say that multiple senses must be multiple POS’s. Of course, FLEx enforces this one-to-one relationship, but MDF Alternate cannot.

Anyways, kudos again for posting this stuff publicly to make it easier to dialog about it in a way others can benefit from.

-Languist

Comment on More Quick Fixing For SOLID by languist

languist — Mon, 08 Jun 2009 18:52:48 +0000

I just helped a colleague to do the same thing: move \bw etc up to the top of the record, outside of the senses/subentry sections. It worked like a charm! We also were delighted to apply the handy feature for making implicit \sn fields explicit. I’ve been wanting that feature for a while. I’m sure there are other bulk edit features that could be useful (move \rf to just above \xv ?), but these two cover a lot of ground.
Suggestions:
1. expand the second feature to make all implicit fields explicit.
2. Add a fix for making all \sn fields empty except for the ones that should be published (i.e. ones that have sibling \sn fields). Renumber if necessary.

(I’m also submitting these ideas to the developer separately.)

Comment on WeSay: What’s it all about by chris.hirt

chris.hirt — Sun, 29 Mar 2009 23:21:34 +0000

Great job on the video, Cambell (or whoever put this together). It’s a great summary of how WeSay (and Palaso) is making a big impact in minority language development!