Re: [FLEx] Digest for flex-list@googlegroups.com - 2 Messages in 2 Topics

[Lynnika Butler]

Hi Jon,

Thanks for your reply!  I got some similar suggestions from Beth, and I tried inserting a line break between glosses in the Configure Reversal Index window...it looks great in FLEx, but completely failed to function in the output!  (Senses just ran together.)

However, I did discover a little checkbox in the Pathway Configuration Tool which lets you choose "Bullet" as a Sense Layout option.  When I did that, the output did *not* have bulleted senses, but it did have each vernacular sense (gloss? I'm probably playing fast & loose with terminology here) on its own line, which is what I originally wanted.  Through some tinkering with field modifications in LibreOffice, I was able to get bullets, arrows, adjust indentation, etc.--though trying to get precise indentation *with* bulleting is maddeningly elusive.  Still, it is definite progress and makes my mini-dictionary much easier to browse visually.  A sample entry after I did some tweaking looks roughly like this:

willow

daghush willow used for eel baskets

gayalilh dughululhiswulh fine-leaved river willow

kuwalh willow with gray leaves

tgulh willow with greasy leaves; black willow

It's not final, but it's getting better!

Thanks,

Lynnika

On Wed, May 23, 2012 at 3:05 PM, <flex...@googlegroups.com> wrote:

  Today's Topic Summary

Group: http://groups.google.com/group/flex-list/topics

• Reversal index & Pathway [1 Update]
• Regular expressions [1 Update]

 Reversal index & Pathway

J V C <jvco...@gmail.com> May 23 05:02PM +0800  

Yes, it would be great if these headers could be turned off. They were
especially troublesome to me (and hard to delete) when I published our
two-column dictionary because each one created two section breaks
(before and after the header, so that the header would span both columns).
 
Lynnika, while viewing the reversal index, you can configure quite a lot
by going to Tools, Configure, Reversal Index. If "display each sense in
a paragraph" can't be made to work the way you want it, you could change
the separator character between senses. I believe you would click on
Referenced Senses and fill in the Between field. You could use something
unique as the separator, something like two semicolons (;;) or a pipe
(|), so that replacing it later with a line break in Writer should be
simple and safe.
 
Or better, put a special line break character there so that you have
less work to do in Writer each time you export. The following works
on-screen for me in FLEx, though I've not tried exporting it via Pathway
myself:
- in Lexicon Edit, type the following into a blank definition in FLEx:
x shift+enter y
(Just FYI, that line break character is U+2028 LINE SEPARATOR.)
- copy both lines from the definition field (you should see x, then y on
a second line; copy both lines)
- go to reversals configuration, and paste into the Between field; you
should see x box y--delete the x and y but leave the box there
 
If you choose to instead do the line breaks in Writer, replacing ";;"
with "\n" works fine for me (with the Regular expressions box ticked).
Removing/replacing line breaks is much harder, but I don't think you
need to do this. (When I do need to, I tend to save as .DOC and use MS
Word, since Word's ^p metacharacter works for both finding and replacing.)
 
Jon
 
 
On 05/17/2012 3:53 PM, Robert Hedinger wrote:


 

 Regular expressions

J V C <jvco...@gmail.com> May 23 04:22PM +0800  

This reply is rather late, but one technique I've found useful over and
over is to refer to both the beginning (^) and the end ($) of the field
in one regex. This forces the whole field to match, so the following
example doesn't just match on "one or more occurrences of s or z"
somewhere in the field; it forces the entire field to consist of such
characters.
 
^[sz]+$
 
To force the field to contain only characters that are NOT s or z, you
can use this (note the completely different meanings of the two ^ here):
^[^sz]+$
 
If you want empty fields to match as well, you could use asterisk instead:
^[^sz]*$
 
The \b is somewhat similar to ^ and $ in that it matches on a word
boundary (an edge/context rather than an actual character that could be
stored/replaced). But it's not quite identical because \b can also match
on word boundaries in the middle of the field. So, o\b will find all
fields containing any word ending in o, whereas o$ will only match where
the last character in the field is o.
 
The shortcut [0-9] is equivalent to [0123456789]; the shortcuts [a-z]
and [A-Z] and [a-zA-Z] are similar (the last one is useful when "Match
case" is ticked but you want any letter of either case).
 
Jon
 
On 05/10/2012 11:10 PM, Sargon Hasso wrote:


 

You received this message because you are subscribed to the Google Group flex-list.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the discussion group "FLEx list". This group is hosted by Google Groups and is open for anyone to browse.
To post to this group, send email to flex...@googlegroups.com
To unsubscribe from this group, send email to flex-list+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/flex-list

--
Lynnika Butler
Linguistics Ph.D. student
University of Arizona

Language Program Manager
Wiyot Tribe
Loleta, CA