cons=
optional.Currently, the cons=
parameter is mandatory: either a singular construct form must be specified, or cons=-
to indicate that no singular construct form exists, or the word will be added to Category:Hebrew noun articles missing singular construct forms. However, for long modern nouns, the issue isn't so much whether it exists, as whether it meets CFI. I've been adding the hypothetical construct form without vowels (i.e., for nouns ending in ־ה I've been changing it to ־ת, and for other nouns I've just duplicated the consonants of the indefinite form), but that's potentially misleading, since it would be very rare to actually see someone use that form. I think that cons=
should be made optional — either the category is only added when cons=?
, or maybe the category is added by default, but cons=nocat
suppresses it, or maybe simply cons=-
shouldn't be so bold as to state that no singular construct form exists, and should mean simply "hey, template: don't list the singular construct form". Any thoughts? —RuakhTALK 14:30, 24 May 2008 (UTC)
cons
should be optional; I like your "cons=?
" and "cons=-
shouldn't be bold" suggestions.—msh210℠ 20:21, 26 May 2008 (UTC)Opiaterein (talk • contribs) has left a note on my talk-page, suggesting that plcons= and plconswv= be added to this template. I'm neutral on the matter — a lot of dictionaries present that, at least for irregular nouns, but on the other hand we theoretically provide full declension tables anyway — but as a matter of process, I figured I should mention it here and wait a day or so before actually doing it. —RuakhTALK 17:21, 1 July 2009 (UTC)
I've created a proposed new version at User:Ruakh/Template. The proposed version strives to behave exactly like the current version (and I intend to do a lot of testing to ensure that; so far I've done just a bit). The improvements are all internal; the proposed version separates three concerns that are badly intermingled in the current version:
{{he-noun/helper}}
.{{he-noun/helper}}
as pl=.The reason for the change would be that the new version should be much easier to make improvements to. For example, my cons=? idea above has languished for more than three years, due in part to its being a pain to implement: all the formatting code that checks to see if a singular construct form is specified (in order to figure out where/whether to include punctuation) would have to be modified to see if it's specified and not ?. With the proposed version, this becomes much simpler, since the formatting logic depends only on whether cons=... is generating actual wiki-code.
Another bit of refactoring may also be warranted, creating some sort of {{he-infl-link}}
to handle the repeated {{Hebr|lang=he|face=head|]}} logic (cf. {{he-onym}}
); the current proposed refactoring is probably independent of that one, though.
Any questions/comments/objections/concerns/whatnot?
—RuakhTALK 02:14, 1 September 2011 (UTC)
Here you can see a strange behavior: during the template processing, the point moves from ג to ב. I suppose this is a RTL issue. Maybe someone can take a look into it. -- 88.74.222.163 06:20, 12 March 2012 (UTC)
Could you try adding this bit of JavaScript to User:Stf/common.js? :
addOnloadHook
( function ()
{ jQuery('.Hebr').each
( function(index, element)
{ if(/\u05BC/.test(element.innerHTML))
element.innerHTML =
element.innerHTML.replace(/(+)\u05BC/g, 'ּ$1');
}
);
}
);
that will find any places where MediaWiki has put a dagésh after other nikúd, and will forcibly undo that. If it works for you, we might want to add it to site-wide JavaScript.
—RuakhTALK 22:04, 13 March 2012 (UTC)
Maybe I found a new variant of this problem: on אפשר#Adjective (template:head), the shin dot moves from right to left. Same with השתמש#Verb (template:he-verb) on the first shin. Maybe you can catch it with your script? Thank you. -- Stf (talk) 20:23, 15 April 2012 (UTC)
addOnloadHook
( function ()
{ jQuery('.Hebr').each
( function(index, element)
{ if(//.test(element.innerHTML))
element.innerHTML =
element.innerHTML
.replace(/(+)\u05C1/g, 'ׁ$1')
.replace(/(+)\u05C2/g, 'ׂ$1')
.replace(/(+)\u05BC/g, 'ּ$1');
}
);
}
);
{{Hebr|שֶׁמֶשׁ|lang=he}}
, reads shemes (first shin, second sin), but this ->שֶׁמֶשׁ<- (plain text) looks fine. If I get it right, only the shin as the last character of a word within a linking template is affected: the entry שלג is OK, אש and שמש are broken. At this moment, I recomment to disable the JavaSript since it causes some extra trouble (disapearing dageshs, sin for shin). I recently updated to Mac OS Maverick, I assume there was a change in some system libraries. -- Stf (talk) 00:06, 31 October 2013 (UTC)
{{lang|he|שֶׁמֶשׁ|שֶׁמֶשׁ}}
look? (And שֶׁמֶשׁ?)—RuakhTALK 00:42, 31 October 2013 (UTC)
‎{{Hebr|שֶׁמֶשׁ|‏שֶׁמֶשׁ‏|lang=he}}‎
is "shemes", ‎‏שֶׁמֶשׁ‏‎
is "shemesh". -- Stf (talk) 05:58, 31 October 2013 (UTC)What is the right way to encode alternative plural forms? See גב for my first attempt, but in this manner the template produces a wrong link (of course). -- Stf (talk) 06:12, 19 October 2012 (UTC)
Could someone please add documentation for the parameters dwv
and pldwv
? I've seen them here and I guess that they are for spellings that differs between vocalized and unvocalized forms. Thanks. Stf (talk) 22:21, 4 November 2012 (UTC)
בת ים is categorized as a feminine noun with plural ending in ים. As a string of letters, the plural does, but the plural ending is -ות, added to the first word. The ים at the end means "sea"; it's not a plural. PierreAbbat (talk) 05:07, 12 May 2016 (UTC)