Change viewing parameters
Switch to Russian version

Search for data in: Indo-European family: Romance group (58 lists)

Select another database


If you want to search for specific values in the database, enter them below

Fieldi

A complete list of fields included in the selected database. In lexicostatistical databases, most fields fall into two types: (a) primary language fields, containing the primary wordlist entries for specific languages, (b) note fields, containing notes (such as bibliographical, grammatical, etymological etc. information) on said wordlist entries. By default, search procedures take into account the information that is stored in both types of fields.

In the «Search in several databases at once» option, since it covers all the lexicostatistical databases on the site, the list of fields is naturally not available.

Include in report?i

By default, this option is checked for all the fields in the database. Uncheck it manually for those fields that you do not wish to include in the query report, for some reason.

Valuei

Enter the word / word form / character string that you are searching for in this line. The basic «Search» (in one database) option allows you to look for any string in any particular field (primary language field or note field). The «Search in several databases» option has two sub-options: «In any primary language field» or «In any field» (i.e. primary language or note fields). Using the second option will yield more results, but can also yield «noise», since note fields often contain a lot of additional commentary text that will be confused with proper data.

Note that you can send in complex queries, entering different values in different fields; e. g. entering "kaka" in one language field and "papa" in another language field will yield all the records where Language 1 has "kaka" and Language 2 has "papa", etc. (The "or" function, however, is not yet supported).

If you simply want to look at one Swadesh item and its forms in various languages (in one database or all databases), all you have to do is select the corresponding item in the "Word" window and send in the query.

Virtual keyboard: If you want to enter a search query that contains special symbols, used in the UTS (Unified Transcription System), you can use a semi-concealed «virtual keyboard» by clicking the mouse on the empty space between the «Value» and «Query method» columns next to the field for which the value is being entered. The «virtual keyboard» contains most of these symbols, including diacritics. Hide the «virtual keyboard» away by clicking on the same empty space one more time.

Query methodi

There are four different ways in which the search algorithm can understand the input strings of characters (we will illustrate this with examples drawn from the Ejagham language in the Ekoid database):

Match substring:
By default, the algorithm just gives you all the entries in which the string has been encountered. Thus, looking for the string y in Ejagham will yield such words as ò=yà ʽbellyʼ, yûm ʽbiteʼ, è=yǜg ʽcoldʼ, yûi ʽkillʼ, ɛ̀=yâ ʽyearʼ, etc.
Match beginning:
The algorithm only returns the entries in which the string has been encountered in the initial position. Therefore, looking for y in Ejagham will yield such words as yûm ʽbiteʼ, yûi ʽkillʼ, but not ò=yà ʽbellyʼ or è=yǜg ʽcoldʼ, since the latter do not begin with y.
Like beginning:
The algorithm returns the entries whose beginning is not only identical with the input string, but is also phonetically similar to it. (See help info on the «Highlight phonetically similar items» for the definition of what constitutes «phonetic similarity» in StarLing algorithms). Thus, looking for the string at in Ejagham will yield such words as ɛ̀tí-ɛ̀tî ʽmanyʼ and ɛ̂d ʽweʼ, since they are judged by the machine as phonetically similar to at.
Like substring:
The algorithm returns the entries any part of which (not just the beginning) is phonetically similar to the input string. Thus, looking for the string t in Ejagham, in addition to ɛ̀tí-ɛ̀tî ʽmanyʼ and ɛ̂d ʽweʼ, will yield such words as =kpídì ʽnearʼ and =sǝ́dɛ́ ʽsayʼ, because their middle parts (-di, -dɛ) are phonetically similar to t.

Whole wordsi

If this option is checked, the search algorithm will only return those results in which the string that you have entered forms an entire word, not part of the word. For example, looking for the string ka in the Ejagham (Ekoid) language with the option Whole words unchecked will return two results: =kárè ʽgiveʼ and ka- ʽnotʼ. If the option Whole words is checked, the algorithm will only return ka-, but not =kárè. If you are looking for a short (e.g. monosyllabic) word, checking this option will help get rid of additional «noise».

Not emptyi

This is a special condition that will filter out records with one or more empty fields; it is useful for queries oriented at comparative data (e. g. «find all the instances of the /sub/string ka in Language 1 that have parallels in Language 2»). By default, the option is unchecked. If you check it for all the fields in the database, the query will only return records that are completely filled, i.e. each field contains at least some information.

Number



Word
Archaic Latin 
Late Classical Latin 
Megleno Romanian 
Istro Romanian 
Aromanian 
Romanian 
Dalmatian 
Friulian 
Gardenese Ladin 
Fassano Ladin 
Rumantsch Grischun 
Sursilvan Romansh 
Surmiran Romansh 
Vallader Romansh 
Lanzo Torinese Piemontese 
Barbania Piemontese 
Carmagnola Piemontese 
Turinese Piemontese 
Vercellese Piemontese 
Bergamo Lombard 
Plesio Lombard 
Ravennate Romagnol 
Ferrarese Emiliano 
Carpigiano Emiliano 
Reggiano Emiliano 
Rapallo Ligurian 
Genoese Ligurian 
Stella Ligurian 
Venice Venetian 
Primiero Venetian 
Bellunese Venetian 
Old Italian 
Standard Italian 
Grosseto Italian 
Foligno Italian 
Neapolitan 
Logudorese 
Campidanese 
Palermitan Sicilian 
Messinese Sicilian 
Catanian Sicilian 
South-Eastern Sicilian 
Central Catalan 
North-Western Catalan 
Minorcan Catalan 
Castelló de la Plana Catalan 
Valencia Catalan 
Manises Catalan 
Castilian Spanish 
Asturian 
Standard Portuguese 
Galician 
Provençal Occitan 
Savoyard Franco-Provençal 
Old French 
Standard French 
Picard 
Walloon 
Archaic Latin notes 
Late Classical Latin notes 
Megleno Romanian notes 
Istro Romanian notes 
Aromanian notes 
Romanian notes 
Dalmatian notes 
Friulian notes 
Gardenese notes 
Fassano notes 
Rumantsch Grischun notes 
Sursilvan Romansh notes 
Surmiran Romansh notes 
Vallader Romansh notes 
Lanzo Torinese Piemontese notes 
Barbania Piemontese notes 
Carmagnola Piemontese notes 
Turinese Piemontese notes 
Vercellese Piemontese notes 
Bergamo Lombard notes 
Plesio Lombard notes 
Ravennate Romagnol notes 
Ferrarese Emiliano notes 
Carpigiano Emiliano notes 
Reggiano Emiliano notes 
Rapallo Ligurian notes 
Genoese Ligurian notes 
Stella Ligurian notes 
Venice Venetian notes 
Primiero Venetian notes 
Bellunese Venetian notes 
Old Italian notes 
Literary Italian notes 
Grosseto Italian notes 
Foligno Italian notes 
Neapolitan notes 
Logudorese notes 
Campidanese notes 
Palermitan Sicilian notes 
Messinese Sicilian notes 
Catanian Sicilian notes 
South-Eastern Sicilian notes 
Central Catalan notes 
North-Western Catalan notes 
Minorcan Catalan notes 
Castelló de la Plana Catalan notes 
Valencia Catalan notes 
Manises Catalan notes 
Castilian Spanish notes 
Asturian notes 
Standard Portuguese notes 
Galician notes 
Provençal Occitan notes 
Savoyard Franco-Provençal notes 
Old French notes 
Standard French notes 
Picard notes 
Walloon notes 

In any primary language field  


In any field  

Sort byCheck for polysemyi

This is a simple option, specially introduced for those who are interested in semantic change and polysemy. The algorithm looks for all instances of the marker word «polysemy» in the «Notes» section, and yields the corresponding results. This works best in tandem with single-word search across all databases. E.g., if you select «Search in all databases», select the value «bird» in Word, and check the «Check for polysemy» option, the query will yield all the occasions in the GLD where a polysemy was detected and notated for the word ʽbirdʼ, regardless of the language.


Total pages generatedPages generated by this script
9255182343676
Help
StarLing database serverPowered byCGI scripts
Copyright 1998-2003 by S. StarostinCopyright 1998-2003 by G. Bronnikov
Copyright 2005-2014 by Phil Krylov