Going between Lexicon Edit and Bulk Edit

[Susanna]

In FieldWorks 6.0 (FLEx 3.0) when you set a filter in Bulk Edit
Entries, when you return to Lexicon Edit (or Browse) FLEx maintains
the filter. I think there are some bugs to fix to make this work
really smoothly. However, before we do that, I want to check that this
is the most useful way round. The other approach we could take is that
when you go back to Lexicon Edit, it is sorted and filtered just the
way it was when you were last there, rather than the same way as Bulk
Edit Entries. Do you know what you'd prefer?
Here are some pros and cons I can think of:
1. Shared sort and filters:
Pro: when you set up a sort/filter in Lexicon Edit you then find it
active in Bulk Edit, so you don't have to set up the filter again to
perform the bulk edit on that data.
Con: when you go from Bulk Edit to Lexicon Edit, you have to turn off
the filter if you want to review an entry that is excluded by the
current Bulk Edit filter. Then you have to reinstate the filter when
you go back to Bulk Edit.
2. Separate sort/filters:
Con: if you notice a pattern when filtering/sorting in Browse or
Lexicon Edit, you have to redo that filter when you move to Bulk Edit.
Pro: if you want to flip to Lexicon Edit whilst working in Bulk Edit,
you can do this without losing or disturbing the filters in Bulk Edit,
and you have the freedom to look up something completely different.

What do you think would be more convenient?

At the moment it seems FLEx is attempting to maintain the filters
between the views, but is not maintaining the sort. Probably not the
best behaviour....

Thanks for your input,
Susanna

[Heidi J. Rosendall]

As an instructor of Fieldworks for students of many levels of ability, I
prefer that all filters and sorts set in any view be maintained until I turn
them off. This predictable behavior requires less thinking for an
experienced user and is MUCH easier to teach. My students struggle when what
they have set disappears or changes from one view to the next.

It would also be nice if we could set the column settings (Which columns and
in what order) in, say, the Browse View for a default setting WE choose
which would then carry over to the other views unless changed in that view
with a button for the settings to go back to our chosen default of columns
in whatever view we are in. We are forever changing columns for particular
tasks and then trying to get them set back up again properly afterwards.

As well, I still have the serious request that settings be saved as part of
the backup so that when a project is restored on another computer the
student sees the exact setup he had previously. This loss of settings when
restoring is a serious problem for me as an instructor in a computer lab
without networking capabilities.

But mostly you have not heard from me because we are quite happily using the
program...

Blessings,


Heidi J. Rosendall
Language Software and Typesetting Manager
Wycliffe Nigeria Group
Heidi_R...@wycliffe.org
Skype: heidi.james.rosendall

--
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

[Craig Farrow]

Susanna,

I can't remember if there's been discussion on saved Filter/Sort
configurations, but if that was in the pipeline then it could be a
simple matter of choosing a saved filter whenever/wherever you need it
without forcing the user to have the same filter in all places.

Craig.

8/12/2009 6:34 a.m. dï, Susanna pišdimiš:

[Bruce Hooley]

Hi Susanna

I guess the way I have been working is to use filters in Lexicon Edit to try
and find various things I'm looking for. Then once I know what I want to do,
I go to Bulk Edit and there I have all the examples I want to change,
already marked and ready to go. So I guess I would vote for shared sort and
filters. I think there is some advantage in being consistent across the
various options. So if you are working with a filtered set in one area, you
don't have to remember things have changed when you go to another. But I am
sure either way would work once you got used to it.

Bruce
--------------------------------------------------
From: "Susanna" <susann...@sil.org>
Sent: Tuesday, December 08, 2009 3:34 AM
To: "FLEx list" <flex...@googlegroups.com>

Subject: [FLEx] Going between Lexicon Edit and Bulk Edit

__________ Information from ESET Smart Security, version of virus signature database 4668 (20091207) __________

The message was checked by ESET Smart Security.

http://www.eset.com

[Mark Penny]

My vote would be to keep the same filters. But I suspect that if you
were to poll all users you'd get a 50/50 mix. I like Craig's
suggestion of having saved filters (or even just recent filters in the
drop-down list).

Another idea is to have one default behaviour (whichever is most
popular), and then enable the other behaviour by using a shift-Click
instead of a regular click when you select the view. Am I asking too
much to have the best of both worlds? :)

Mark

On Dec 8, 3:51 am, "Bruce Hooley" <bruce_hoo...@sil.org> wrote:
> Hi Susanna
>
> I guess the way I have been working is to use filters in Lexicon Edit to try
> and find various things I'm looking for. Then once I know what I want to do,
> I go to Bulk Edit and there I have all the examples I want to change,
> already marked and ready to go. So I guess I would vote for shared sort and
> filters. I think there is some advantage in being consistent across the
> various options. So if you are working with a filtered set in one area, you
> don't have to remember things have changed when you go to another. But I am
> sure either way would work once you got used to it.
>
> Bruce
> --------------------------------------------------

> From: "Susanna" <susanna_im...@sil.org>

[Robert Hedinger]

I think the best would be to have both worlds, by being able to name and
save filter and brows view/sort settings.

Robert

--------------------------------------------------
From: "Mark Penny" <jampa...@gmail.com>
Sent: Tuesday, December 08, 2009 6:04 AM
To: "FLEx list" <flex...@googlegroups.com>
Subject: [FLEx] Re: Going between Lexicon Edit and Bulk Edit

[Jeff and Peg Shrum]

Heidi wrote:


It would also be nice if we could set the column settings (Which columns and
in what order) in, say, the Browse View for a default setting WE choose
which would then carry over to the other views unless changed in that view
with a button for the settings to go back to our chosen default of columns
in whatever view we are in. We are forever changing columns for particular
tasks and then trying to get them set back up again properly afterwards.

--------------------------------------------------------------------------

Earlier in the year on another thread, the need for the ability to name and
save settings for specific tasks was discussed. (Much like TW and Pt7
does). I would include in that capability the ability to save the filters
that one has been using.

Jeff S.

[Dennis Walters]

Craig Farrow wrote:
> Susanna,
>
> I can't remember if there's been discussion on saved Filter/Sort
> configurations, but if that was in the pipeline then it could be a
> simple matter of choosing a saved filter whenever/wherever you need it
> without forcing the user to have the same filter in all places.
>
> Craig.
>

I'd like to second this suggestion of Craig's.

Also, the general behavior of retaining a set filter from one view to
the next seems like a good choice.

Dennis

[Bruce Hooley]

Hi,

Is there a way to ignore characters (or rather non-characters) in sorting
one's dictionary?

At the moment the sort order, when dealing with entries having more than one
word, sorts the ones with a space between the words first, then it starts
again and sorts those with hyphens next before it sorts the one word items.
I think I would like to ignore both the space and the hyphen and just sort
everything in together. At least I would like to look at how it comes out
before I decide. Is there a way to do what I want? I couldn't find an answer
in help.

Thanks

Bruce Hooley

__________ Information from ESET Smart Security, version of virus signature database 4720 (20091227) __________

[Robert Hedinger]

I have been wanting the same too, but have not yet worked out how to do it.

Robert

--------------------------------------------------
From: "Bruce Hooley" <bruce_...@sil.org>
Sent: Monday, December 28, 2009 7:59 AM
To: <flex...@googlegroups.com>
Subject: [FLEx] Sorting

[Beth]

On Dec 27, 2009, at 10:59 PM, Bruce Hooley wrote:

> Is there a way to ignore characters (or rather non-characters) in
> sorting
> one's dictionary?

Ken sent me this back in June. Right now I'm not finding *which* of
his technical docs has this in it.

At the end it talks about ignoring characters. I'm not certain about
ignoring space, but presumably you could use \u0020?

Hopefully there is enough here to get you guys started?

-Beth

On Jun 4, 2009, at 6:31 AM, Ken Zook wrote:
> Here's my latest technical doc that includes sorting. Most of this
> is also in the help file.
>
> Some quotes from it explains ignoring apostrophe.
>
> Note: In an ICU rule, any non-alphanumeric ASCII character is
> reserved for syntax characters. If you need to control collation of
> any of these characters, you must put an apostrophe in front of the
> character. To control the collation of an apostrophe you would thus
> add two apostrophes (not a double quote). In this context, using
> the Unicode code point \u0027 will not work.
> To sort t' after t, you would use the rule
> &t<t''
>
> The following rules would be one way to handle IPA sorting
> &d<d͡ʒ
> &e<ɛ<f<ɸ
> &i<ɨ
> &k<k''
> &n<ŋ
> &p<p''<r<ɾ
> &s<ʃ<ʂ
> &t<t''<t͡s<t͡s''<t͡ʃ<t͡ʃ''<ʈ͡ʂ<ʈ͡ʂ''
> &z<ʒ<ʐ<ʔ
> Suppose you want to ignore an apostrophe after m and n, but you
> want ng to sort after n, and ng’ to sort after ng. The following
> rules allow for this.
> The = syntax states that the right side is identical to the left side.
> &m=m''
> &M=M''
> &n=n''
> &N=N''
> &n<ng<<<Ng<<<NG<ng''<<<Ng''<<<NG''
>
> Suppose you want to ignore 02BC;MODIFIER LETTER APOSTROPHE in
> sorting. There are two ways you could handle this. The following
> rule doesn’t totally ignore the apostrophe, but it treats it in a
> secondary level so that it is ignored unless words are identical
> otherwise. In this case it always comes after other diacritics.
> &\u030E<<\u02BC
> This would result in the following order: ba, bad, bäd, baʼd,
> bʼad, bade, bat, bät, baʼt, bʼat, bate.
> The second approach is to totally ignore 02BC.
> &[last tertiary ignorable] = \u02BC
> This would result in the following order ba, baʼd, bad, bʼad,
> bäd, bade, baʼt, bat, bʼat, bät, bate. Since ba, baʼd, and
> bʼad all have identical sort keys, their order is random. The
> ‘last tertiary ignorable’ rule should be after all other rules,
> or it will disable the other rules.
> If you need to ignore more than one character, separate the
> characters with commas. The following rules would sort k after d
> and would ignore apostrophe and question mark.
> &d<k<<<K
> &[last tertiary ignorable] = '', '?
>

[Bruce Hooley]

Thanks Beth, but I couldn't make it work.

I tried using the statement Ken suggested, namely &\u030E<<\u02BC, but changing the 02BC to 002D for the hyphen and 0020 for the space, but in both cases I got the following message:

Install language failed on file C:\ProgramData\SIL\Fieldworks\Languages\bzh.xml with code -24. The writing system could not be modified. There is a problem in your language definition. See the FieldWorks ReadMe for help in this area.

I haven't checked that yet, but I am obviously doing something wrong because I just copied Ken's statement, but changed the character reference.

I did several attempts with the &[last tertiary ignorable] = '', '? statement too, trying to use the - and the space or the \u0020, but none of them worked. I received messages along the following lines each time:

The sorting specification is not valid. An error occurred in line 1 offset 215 between the text "norable]= "and" ". Please correct the error to continue.

 

I guess it is pretty obvious (to the program at least!!) that I don't know what I am doing. I was hoping that using Ken's statements with slight modifications, I could achieve what I wanted, but it seems it is not that easy.

 

Thanks for trying anyway.

 

Bruce

--------------------------------------------------
From: "Beth" <lxb...@yahoo.com>
Sent: Monday, December 28, 2009 8:17 PM
To: <flex...@googlegroups.com>
Subject: Re: [FLEx] Sorting

> --
> 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
>

> __________ Information from ESET Smart Security, version of virus signature database 4723 (20091228) __________

>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>

__________ Information from ESET Smart Security, version of virus signature database 4723 (20091228) __________

[Robert Hedinger]

I added this:

&Ɛ<ə<<<Ə
&[last tertiary ignorable] = \u02BC \u0020, '-

 

which FLEx accepted, but I still don't get the results I expect.

 

I get

 

bwɛl 

bwɛl éʼ ngande e mbúú 

bwɛl éʼ yukalítus 

bwɛl-amǐnɛ 

 

What I expect is:

 

bwɛl 

bwɛl-amǐnɛ 

bwɛl éʼ ngande e mbúú 

bwɛl éʼ yukalítus 

 

I get the first message below when I put a comma between the \u02BC, \u0020, but strangely it when I go back later the comma is still there.

 

Robert

[Ken Zook]

I finally discovered some misunderstandings on ICU sort specs that I had documented previously and that are in the current help files. I hope to post some new technical documentation soon with corrections to this and the fixes are being added to the help files for FieldWorks 6.0.1.

 

Here are some revised sections that I hope will clear up these problems related specifically to ignoring certain characters when sorting.

 

Note: In an ICU rule, any non-alphanumeric ASCII character is reserved for syntax characters. If you need to control collation of any of these characters, you must quote them with a \ or enclose them in apostrophes. A single apostrophe can also be represented as two apostrophes. Here are some examples of alphanumeric and punctuation characters with or without the \u syntax.

a                         letter a
\u0061                letter a
3                         digit 3
ng                       digraph ng
'ng'                      digraph ng (quotes are optional for alphanumeric characters)
\u006e\u0067     digraph ng
\-                         hyphen
'-'                        hyphen
' '                         space
\                          space (there is a space following the \)
'\u0020'               space
\\u0020               space
\'                         apostrophe
''                          apostrophe
\u0027\u0027     apostrophe

To control the collation of an apostrophe you would thus add two apostrophes (not a double quote). To sort t' after t, you would use the rule

&t<t''

The following rules would be one way to handle IPA sorting

&d<d͡ʒ
&e<ɛ<f<ɸ
&i<ɨ
&k<k''
&n<ŋ
&p<p''<r<ɾ
&s<ʃ<ʂ
&t<t''<t͡s<t͡s''<t͡ʃ<t͡ʃ''<ʈ͡ʂ<ʈ͡ʂ''
&z<ʒ<ʐ<ʔ

Suppose you want to ignore an apostrophe after m and n, but you want ng to sort after n, and ng' to sort after ng. The following rules allow for this.

The = syntax states that the right side is identical to the left side.

&m=m''
&M=M''
&n=n''
&N=N''
&n<ng<<<Ng<<<NG<ng''<<<Ng''<<<NG''

Suppose you want to ignore 02BC;MODIFIER LETTER APOSTROPHE in sorting. There are two ways you could handle this. The following rule doesn’t totally ignore the apostrophe, but it treats it in a secondary level so that it is ignored unless words are identical otherwise. In this case it always comes after other diacritics.

&\u030E<<\u02BC

This would result in the following order: ba, bad, bäd, baʼd, bʼad, bade, bat, bät, baʼt, bʼat, bate.

The second approach is to totally ignore 02BC.

&[last tertiary ignorable] = \u02BC

This would result in the following order ba, baʼd, bad, bʼad, bäd, bade, baʼt, bat, bʼat, bät, bate. Since ba, baʼd, and bʼad all have identical sort keys, their order is random.

If you need to ignore more than one character, use = to separate the list of characters. The following rule would ignore an apostrophe, a question mark, a hyphen, a space, and the ng digraph

&[last tertiary ignorable] = '' = '?' = '-' = ' ' = ng

or

&[last tertiary ignorable] = \' = \? = \- = \  = ng

This could also be represented as

&[last tertiary ignorable] = \u0027\u0027 = '\u003f' = '\u002d' = '\u0020' = \u006e\u0067

If you simply want to ignore all punctuation as well as white space, you can use the following rule

[alternate shifted]

 

One answer to Robert’s specific question to ignore 2bc, space, and hyphen is

  &[last tertiary ignorable] = \u02bc = \  = \-

 

Ken

[Ken Zook]

Sorry for misleading. When I wrote my previous e-mail I was experimenting with the ICU locale explorer on the Internet and what I wrote was accurate for that. Unfortunately, the ICU explorer uses the current version of ICU which is 4.2 at this point, but FieldWorks 6.0 and 6.0.1 are still using ICU 4.0. It turns out the backslash (\) quote is a new feature of ICU 4.2 that is not currently supported in FieldWorks.

 

I’ve added this note to my technical documentation:

 

·         ICU provides a useful Web site for testing collation rules at http://demo.icu-project.org/icu-bin/locexp. Click the root language link, then near the bottom under Collation rules, click Demo.
Note: This demo uses the currently released version of ICU which may not apply to what is currently available in FieldWorks. For example FieldWorks 6.0 and 6.0.1 use ICU 4.0, but as of this date, ICU has released ICU 4.2 which adds a new \ quoting character. So although the demo works with \, FieldWorks will not currently accept this.

 

and the previous explanation should have been:

 

Note: In an ICU rule, any non-alphanumeric ASCII character is reserved for syntax characters. If you need to control collation of any of these characters, you must quote them with a \ (only ICU 4.2 or greater) or enclose them in apostrophes. A single apostrophe can also be represented as two apostrophes. Here are some examples of alphanumeric and punctuation characters with or without the \u syntax. (See the Note in the second bullet under section 8.1 regarding the backslash limitation.)

a                         letter a
\u0061                letter a
3                         digit 3
ng                       digraph ng
'ng'                      digraph ng (quotes are optional for alphanumeric characters)
\u006e\u0067     digraph ng

\-                         hyphen [not currently in FW]
'-'                        hyphen
' '                         space
\                          space (there is a space following the \) [not currently in FW]
'\u0020'               space
\\u0020               space [not currently in FW]
\'                         apostrophe [not currently in FW]
''                          apostrophe
\u0027\u0027     apostrophe

or [not currently in FW]

&[last tertiary ignorable] = \' = \? = \- = \  = ng

This could also be represented as

&[last tertiary ignorable] = \u0027\u0027 = '\u003f' = '\u002d' = '\u0020' = \u006e\u0067

If you simply want to ignore all punctuation as well as white space, you can use the following rule

[alternate shifted]

 

One answer to Robert’s specific question to ignore 2bc, space, and hyphen is

  &[last tertiary ignorable] = \u02bc = ' ' = '-'

 

Ken