Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mw:12831 #923

Open
funderburkjim opened this issue Sep 12, 2022 · 4 comments
Open

mw:12831 #923

funderburkjim opened this issue Sep 12, 2022 · 4 comments
Labels
help wanted Extra attention is needed

Comments

@funderburkjim
Copy link
Contributor

date: 07/06/2022 12:30:29
dict: mw
Lnum: 12831
hw: abhisampad
old: id.
new:
comm: In the original ("printed book") it is clear that "id." means content of the previous article, abhisampatti; but here, in the "electronic" form it is absolutely unclear. The means must be found to resolve situation.

@funderburkjim
Copy link
Contributor Author

funderburkjim commented Sep 12, 2022

Many of us have had a similar thought.
Here is the base form in mw.txt of this example:

THE PREVIOUS entry
<L>12830<pc>73,2<k1>aBisampatti<k2>aBi-sampatti<e>2
<s>aBi-sampatti</s> ¦ <lex>f.</lex> becoming anything, becoming similar or equal to, <ls>KātyŚr.</ls><info lex="f"/>
<LEND>
THE ENTRY WITH DANGLING 'id.'  
<L>12831<pc>73,2<k1>aBisampad<k2>aBi-sampa/d<h>2<e>2
<hom>2.</hom> <s>aBi-sampa/d</s> ¦ <lex>f.</lex> <ab>id.</ab>, <ls>ŚBr.</ls><info lex="f"/>
<LEND>

What new markup should be used? How should the new markup be displayed to the user?

One reason this problem doesn't bother me much is that I use list displays (such as that in simple search). In such a display, the 'previous entry' can be seen in the list on the left of display, and can be clicked on to see the previous entry.

But of course the user of such displays as advanced search will not have that contextual list, and so will be frustrated.

@funderburkjim funderburkjim added the help wanted Extra attention is needed label Sep 12, 2022
@Andhrabharati
Copy link

Andhrabharati commented Jul 14, 2024

But of course the user of such displays as advanced search will not have that contextual list, and so will be frustrated.

@funderburkjim

How about having another "field" taking the L-number as the search-entry?

One could key-in the L-number and get the prev. entry; of course this would 'miserably' fail in case of MW, where many L-numbers [23279 out of 287582, i.e. about 8%] contain decimal numbers, in many variant manners (added mostly in ad-hoc style) that a user cannot "predict"!

@Andhrabharati
Copy link

Two more ideas @funderburkjim, to cater to the issue--

  1. To show Next & Prev. entries, as done in showing next & Prev. pages of the Lexicon pages.
    image
    (The arrow marks could be at the L-number which is in a separate line at the end of the entry matter; this is a generic solution, to see the dict. data entry-wise)

  2. Always show the preceding entry (probably in grayed out background) and current entry (in white background as is done now), wrt the search key result.

As this is a server side activity (that "knows" the entry number sequence of the particular dictionary), these two options have no limitations or drawbacks (as against the idea mentioned in the above post).

@funderburkjim
Copy link
Contributor Author

To show Next & Prev. entries ... Next makes sense in the B and M displays, but not in the A display.

Another idea: revise the markup in mw.txt

<L>12831<pc>73,2<k1>aBisampad<k2>aBi-sampa/d<h>2<e>2
<hom>2.</hom> <s>aBi-sampa/d</s> ¦ <lex>f.</lex> 
<ab>id.</ab> (same as <s>aBisampatti</s>)

This would work in any of the displays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants