envlh / dicare-tools Goto Github PK

Many entries in BnF do provide information about place of birth P19 and death P20.
It would be very cool to include these in the generated QuickStatements.
For example https://catalogue.bnf.fr/ark:/12148/cb13426384t

Kind regards!

There are more and more lexemes written in FSW signwriting which is (I guess) hardly readably and it blows the layout of the table. I think you can convert all these languages to sutton signwriting which consumes much less space and is prettier to look at 😬.

There is an excellent library to do that, written in Javascript.

i recommend not to use float in such situations. A separate column would solve the problem

It would be very practical if the extracted statements could be made automatically instead of manually.
Similar to https://author-disambiguator.toolforge.org/ and https://mix-n-match.toolforge.org when creating a new item.

Currently klingon letters in the lexermes challange look like this:

With a dedicated font it could look like this:

You could simply define it as a fallback

@font-face {
  font-family: 'DIn pIqaD';
  src: url(dist/DIn pIqaD.woff);
  unicode-range: U+F8D0-F8E9,U+F8F0-F8F9,U+F8FD-F8FF;
}

body, input, select {
    font-family: "Open Sans", 'DIn pIqaD', sans-serif;
    font-size: 14px;
    background: #FFF;
}

or scope it to a specific language:

td:lang(tlh) {
   font-family: 'DIn pIqaD', monospace;
}

When checking the example from #6 I noticed
"Docteur en médecine (Paris, 1904)"

If present, this could be used to create P512 academic degree pointing to Q4618975 doctor qualified by P585 point in time and P276 location (and maybe even P812 academic field).

Cordialement

This might be motivating and informative.

At the moment, only languages with an ISO 639-1 code are offered as display languages. Any language should be available, without any limitation.

See documentation for workaround, using the language_display parameter: https://www.wikidata.org/wiki/User:Envlh/Lexemes_Party#Parameters