Hello, you have come here looking for the meaning of the word User talk:Sartma. In DICTIOUS you will not only get to know all the dictionary meanings for the word User talk:Sartma, but we will also tell you about its etymology, its characteristics and you will know how to say User talk:Sartma in singular and plural. Everything you need to know about the word User talk:Sartma you have here. The definition of the word User talk:Sartma will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofUser talk:Sartma, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.
While reviewing some Cuneiform sign entries, I also modified some cuneiform transliterations, and I started using Unicode subscript numbers to indicate indexes. But I'm having doubts whether that's the best approach (even though it does look neater on screen from a typographical point of view, at least to me). Unicode subscript numbers are not easy to type in general outside the Wiktionary editing window. So I'm curious to know what your opinion on this matter is. Which of the following options for indexing transliterations do you think would be better to use on Wiktionary?
Unicode subscript numbers: ₀₁₂₃₄₅₆₈₉? Ex.: du₃, gu₄, gi₁₇, etc. (they can be found and easily entered selecting Miscellaneous in the drop down menu on bottom left of the page when in editing mode.)
@Sartma: My opinion is that Unicode subscript numbers are easy to type. I directly input Unicode by name or hex via the function in my IME (search name subscript NUMBER and select), or otherwise via dedicated applications like gucharmap or KCharSelect, so I have never once used the Wiktionary editing window to find signs. Such Unicode input even exists in bare GTK and QT environments by default. The machine readability of the them is also better than with HTML tags. Fay Freak (talk) 15:04, 26 April 2021 (UTC)Reply
Hi, @Tom 144! I've seen you changed the vowel length in the Pronunciation section of šarrāqum, stating in your comment that "Vowels could have three lengths.". Where did you find this information? I find it quite difficult to believe that we could understand such a minor thing from the cuneiform script, but I'm willing to change my mind if I see valid proof! Cheers, Sartma (talk) 15:55, 28 April 2021 (UTC)Reply
Problemi con l'UNICODE
Latest comment: 3 years ago5 comments2 people in discussion
Ciao Sartma, sto provando a trascrivere in unicode i testi in cuneiforme che sono incrostati nelle voci di Wikipedia con delle immagini. Sto incontrando però alcune difficoltà, come con l'albero ḫalub perché non trovo il simbolo corrispondente a ub2. Il mio riferimento è la tabella dn-works. Potrei farti altri esempi, ma l'idea è quella. Che tu sappia, c'è un modo per ovviare a questo problema, come la "composizione di caratteri"? Grazie --Ruthven (talk) 08:08, 26 September 2021 (UTC)Reply
Bello strumento, grazie! Ho provato, ma non ritrovo i caratteri che cerco. Nella finestra "classic" ho scritto ḫalūb e il risultato non corrisponde esattamente a quanto mi aspettavo (che corrisponde all'immagine qui di lato, per intenderci, che ho trovato anche in un'altra fonte).
rimani su “Advanced” e nella finestra di input (quella più in basso di una riga solo) digita “kha” per 𒄩, “lu” per 𒇻 e “ub2” per 𒂠. I caratteri compaiono nella finestra più grande sopra.
per “anzūd” digita “an” per 𒀭, “zu” per 𒍪, “ash2” per 𒀾 (ud₂) e “mushen” per 𒄷.
purtroppo non sono presenti tutte le pronunce di alcuni caratteri, quindi se non trovi il carattere che vuoi con una pronuncia devi provare con un’altra. Io in questi casi uso “An Akkadian Handbook”, che ha una lista di tutte le pronunce e il rimando ai caratteri corrispondenti. Se vieni sul canale Discord di Wiktionary puoi chiedermi I caratteri che non trovi via chat. Sartma (talk) 19:47, 26 September 2021 (UTC)Reply
@ShlomoKatzav: Hi! The question with Unicode cuneiform signs is a bit complicated. The sign you're looking for does exist and is 𒈬. If you want to display Neo-Assyrian signs you'll have to use a Neo-Assyrian font. By default you'll see a representation of the lapidary style (the one Hammurabi's code is written in, for example). So, it's not a question of Unicode symbol, but of font. Sartma (talk) 10:44, 17 November 2021 (UTC)Reply
@ShlomoKatzav It's a matter of display. I've always been working with lapidary style cuneiform, so I wouldn't really know what to suggest. You can find free Neo-Assyrian fonts on different places online. I know of this site, for example: Cuneifont. Once you installed the font you want, you need to set your browser to use those fonts (if your browser allows it. I'm on Chrome and still didn't quite understand how to do that). Sartma (talk) 13:57, 17 November 2021 (UTC)Reply
@ShlomoKatzav: Update on the Neo-Assyrian font front. To change the font Wiktionary uses to display Akkadian, you need to create your private common.css file. Create the page User:ShlomoKatzav/common.css and copy paste the following line in it:
After that, go to this site and download the font called Assurbanipal (choose it from the Download menu on the top right) and install it on your computer. Restart your browser and all Akkadian entries should appear in Neo-Assyrian cuneiform now. Let me know if it worked! Sartma (talk) 09:22, 29 June 2022 (UTC)Reply
@ShlomoKatzav Yes, there are some images of Neo-Assyrian cuneiform stored on Wikimedia Commons. You can find them here: Cuneiform signs.
To add them to the character info box, you need to add their Unicode code point and the name of the corresponding image file to this module: Module:Unicode data/images/012.
Hi! Thank you for getting in touch. We don't need an {{akk-signs}} template though, since Akkadian entries are given in their Normalised forms (Latin letters) and Akkadian cuneiform spellings are given with the {{cunsp}} template. See for example: 𒀭(šamû). Sartma (talk) 07:58, 2 February 2022 (UTC)Reply
Latest comment: 2 years ago3 comments2 people in discussion
Since you have added Akkadian categories to this I assume there should be an Akkadian L2 header somewhere, right? I didn't add it myself because I wasn't 100% sure on how to break up the entry. 37.110.218.4312:17, 9 February 2022 (UTC)Reply
Yes indeed! I fixed it, thank you! If you are interested in adding more Sumerian/Akkadian, just check other Sumerian lemmas or Akkadian lemmas and copy the page structure. Don't be afraid of adding content, I check new entries regularly and will edit them if they need editing. At the moment I'm pretty much the only editor for Akkadian and Sumerian, I could use a hand! :D Sartma (talk) 12:24, 9 February 2022 (UTC)Reply
Latest comment: 2 years ago2 comments2 people in discussion
Hello, if it's a valid/required POS header, maybe you should get it added to WT:POS. (I just noticed that this was already discussed, but the page hasn't been updated.) – Jberkel21:00, 7 April 2022 (UTC)Reply
Hi! It is in Biblical Hebrew (where in general participles are not written with plene spellings). See entry in BDB and Gesenius' Lexicon: אָפָה. Sartma (talk) 08:16, 17 April 2022 (UTC)Reply
Looks like there's a difference in Biblical Hebrew and Modern Hebrew. I can change the entry to look like אוֹפֶה \ אֹפֶה. What do you think? Taokailam (talk) 00:43, 2 July 2022 (UTC)Reply
Latest comment: 2 years ago2 comments2 people in discussion
Hi Sartma
I don't mind putting the HE root template under ==Hebrew== as you suggested in ראש.
1. There are entries with different roots, eg: כילה. I think in those pages, the HE root template is best after ===Etymology 1===, ===Etymology 2===, etc.
2. The section WT:AHE#Formatting Hebrew entries seem to suggest that HE root be used under the section ===Etymology===. A rewording will be useful for future editors.
Latest comment: 1 year ago2 comments2 people in discussion
Hi Sartma!
Thanks a lot for your work on the sumerian pages, it's really fun to find and browse this resource!
I'm an amateur and I would like to use it but also to make it more discoverable by "inverting" the translations, the pages go -> english meaning right now, and I would like to invert this and possible add pages for other languages. Not by editing the pages as they exist, but by finding the linked to words and adding it to their list of translations.
In that process I would also create a -> set that could also be of use on the sumerian pages?
I'm hesitating to just go full steam ahead on my own, it's probably relatively easy to cause damage that's at the very least annoying to fix.
Do you have ideas or suggestions how that might be done? I would analyze the pages with the python programming language.
Also I'm not sure if this is the best place to discuss these things, is there maybe some public chat channel or hashtag or some other platform where discussions are taking place?
Looking forward to hearing from you!
Bmaxv
Hi Bmaxv! Thank you for you post! Unfortunately I'm terrible when it comes to the technical side of things. I'm not even 100% sure I fully understood your request... I would say that, if you are confident with how Wiktionary works and you know your tools, then... go for it?
@Bmaxv A few things: (1) Please sign using ~~~~ in place of typing in your name. (2) When you say "'inverting' the translations" I take it you want to take the English glosses of Sumerian terms and invert them to get Sumerian translations of English terms. You are aware that English terms already have translation tables? If what you're proposing is to augment the existing translation tables based on the English glosses of Sumerian terms, that cannot be done automatically because there may be several Sumerian terms mapping to the same English term, and the translation table should not blindly list all the Sumerian terms but only the most common one(s); and if more than one are common and worthy of listing, they need to be ordered by how common they are. Think of a regular print dictionary, which uses the same principles. Discussions of this nature are perhaps best carried out at the WT:Beer Parlour so you get the widest possible audience. Benwing2 (talk) 04:39, 24 December 2022 (UTC)Reply
Akkadian ux’s
Latest comment: 1 year ago2 comments2 people in discussion
@Biolongvistul: No, I take them from CAD. I do my best to find the original cuneiform spelling, but if I can't find it I just use plausible spellings (i.e., spellings I find elsewhere in CAD). — Sartma【𒁾𒁉 ● 𒊭 𒌑𒊑𒀉𒁲】21:05, 29 January 2023 (UTC)Reply
Biblical Hebrew pronunciations
Latest comment: 1 year ago2 comments2 people in discussion
@Biolongvistul: I would not accept them. I believe that at the moment the consense for Biblical Hebrew pronunciation reconstruction is based on Tiberian pronunciation. Those edits look more like a reconstruction of Paleo-Hebrew. This is definitely something that should be discussed and agreed upon. If there was no previous discussion about it, I’d remove them all. — Sartma【𒁾𒁉 ● 𒊭 𒌑𒊑𒀉𒁲】14:05, 31 July 2023 (UTC)Reply
Suqum
Latest comment: 1 year ago2 comments2 people in discussion
Yes, I am trying to learn Sumerian, my friends and I have various resources on discord. I told them about wiktionary but many of them don't know that this site exists for some reason. Tony022 (talk) 09:35, 21 February 2024 (UTC)Reply
Latest comment: 9 months ago1 comment1 person in discussion
Hey, could you also take a look at the etymology section of Old Armenian մաքառիմ, where this Sumerogram was cited? There, it is transliterated as 'maḫāru', which presumably would also be incorrect. Thanks in advance! AntiquatedMan (talk) 11:56, 25 February 2024 (UTC)Reply
Reminder to vote now to select members of the first U4C
Latest comment: 6 months ago1 comment1 person in discussion
You are receiving this message because you previously participated in the UCoC process.
This is a reminder that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) ends on May 9, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.
Please share this message with members of your community so they can participate as well.
Hi, @Mynewfiles. Where did you find that definition? It doesn't look correct to me, since the only case that the second term of a genitive construction in Akkadian is genitive, not a "specific case ending". While the first term (the one in the construct state) usually has a specific form that can be different from its absolute state, there's really nothing special about the second term, it just is a noun in the genitive case. I know some grammars have a term for this noun, but it would be ideal if you could add some references to your definition. — Sartma【𒁾𒁉 ● 𒊭 𒌑𒊑𒀉𒁲】10:16, 13 June 2024 (UTC)Reply
Hello Sartma,
Thank you for the reply. I obtained the definition from a book on Akkadian grammar. I can't remember the exact title. Would you be so kind as to revise and improve the entry I created? mynewfiles (talk) 20:08, 13 June 2024 (UTC)Reply