Whoops. Fixed.

is there a way to add css to a cell in a table (for example, adding a border around it or changing the background color) when that cell also has the rowspan/colspan feature in use? i have tried various combinations and i can't get any to work. (this is for languages, not the forum btw)

looks like the way to do it is to switch to the html editor. time to get back in the old geocities saddle lol

...This is of course way too late, but when you use [td| ... ] in WF, the ... can be any attributes that would normally go on a <td> tag. So [td|rowspan=2 colspan=2 style="border: 5px red solid; background: blue; color: black"] is totally viable. Just remember to set both background and foreground colours, so it looks OK on both light and dark themes of the site. (Also remember for borders in tables you may need to argue with border-collapse to get them to show through the site's default CSS.)

In the Eleutean lexicon's main page, words beginning in a stressed vowel (like àver) don't appear, nor suffixes beginning with an en dash (–). If I rewrite them with a hyphen (-), no problemo.

quoting Izambri, Duke, the Findible League:

In the Eleutean lexicon's main page, words beginning in a stressed vowel (like àver) don't appear, nor suffixes beginning with an en dash (–). If I rewrite them with a hyphen (-), no problemo.

i'm having a similar issue in the ka'ekala dictionary. words beginning with a macron don't appear on the index page, and the pagination is screwy (the little navigator things at the top left say "(-kū–pām) / (pe'–yuk)" but there are several words beginning with apostrophes that are alphabetized before -kū, and several words after "pām"). the missing words show up in search results, but not on the index pages

This is likely the same issue as this one:

quoting Rhetorica, Kelatetía: Dis, Major Belt 1:

...the Lilitika dictionary does not do this, either. So I'm thinking maybe the site started using a binary collation order in the Annie db, against my wishes.

I don't know if this avenue was ever pursued.

Dictionary, Tag, and Entry have been updated with new magic from Memory versions. Changes:

1. No more comma after headwords. I can't find a single dictionary that does this unless there's a pronunciation after. The comma is restored if there is a pronunciation.
   
2. New, more efficient print mode that is less likely to blow up and looks more like a real paper dictionary. I've been looking at a lot of paper dictionaries recently.
   
3. Made sure everything was utf8mb4_general_ci by default. The missing suffixes and other fun words have been confirmed to have returned in Ka'ekala and Eleutean. Important: You don't need to put dashes (or hyphens) on words if they have the "prefix" or "suffix" part of speech. The dictionary will display that automatically.
   
4. You can now choose your collation on a per-dictionary basis from the "edit" page. Now you can switch to the Danish collation and do this to your dictionary. Please do not.
   
5. The completely undocumented inflection scheme facilities are now exposed in the UI.
   
6. The completely unimplemented diachronic scheme facilities are now exposed in the UI. Behaviour is the same as inflection schemes.
   
7. One or two minor bugfixes involving unexpected scoping problems between Cadre templates. Cadre's lexical scope is so powerful that any variables with the same name in any script anywhere are a potential namespace collision! This is not the same as global variables. (Just remember to use var, 5head)

Nice thing, that hyphen/dash solution.

And it's nice to see all the words in the main list. However, the problem persists in the 'Related' section of each word entry. Words like Ölmuc or Öggyan Dainunt have their own entries, as you can see, but they don't appear in the 'Related' section of entries like this one.

A similar thing happens with an entry like Irmyr ar Ölsössàs, which doesn't begin in a vowel with special characters, although the third component, Ölsössàs, does it. The entry appears in the dictionary's main list, but it doesn't appear activated in the 'Related' sections of entries, as in this case.

Would it be possible to set Annie up for HTTPS? Firefox complains rather loudly that it doesn't use it.

On the plus side: someone is posting here.
On the minus side: It's a spammer: http://anthologi.ca/?id=269268

A long-overdue round of spam cleanup has been applied.

The reason why Annie still doesn't have HTTPS is a bit convoluted, but basically, as long as you don't re-use passwords, we don't really need it.

Another one about dictionaries.

In the related section, what are we supposed to write when we have homophones and we use the <!>numeral code?

For example, I have both yr and –yr, but in this entry you can see that in related the first one appears as «yr1» if I put yr<!>1 there.

quoting Izambri, Duke, the Findible League:

Another one about dictionaries.

In the related section, what are we supposed to write when we have homophones and we use the <!>numeral code?

For example, I have both yr and –yr, but in this entry you can see that in related the first one appears as «yr1» if I put yr<!>1 there.

There was some missing code in how the related words section was displayed. It should be spiffy now.