Right now we have a nice little rectangle suited for patterns stored in the phonology:
p b t d k g
f v s z x ɣ
However we could do better. It could be useful to have a second partially overlapping rectangle, or even just more spaces to place patterns in for example one chemistry proposal talked about adding ŋ so that it could have enough sonorants for a pattern. The rectangle we have will likely be used in nearly all words, and that causes a problem: word recognisability. A word pair like moo vs new (the only difference in my accent is m vs n) is not a problem, however, if every word is similarly similar there is a problem, Ro, Ygyde, and Ars Signorum, among others arguably massively failed to achieve their goals because it was very easy to hear one sound as another and context wasn't enough to clarify because of the shear amount of similar sounding words. In my opinion when you look at the possible number of syllables/words in a phonological system, you need to look at it on a log scale, because the more complex the phonology, the more words there can be, but also the more things people need to be able to tell apart. Sounds that sound radically different (such as clicks) are far less affected by this tho.
Here are some sounds (and related thoughts) that could potentially expand the workable area, they would likely never appear word final, or even as a coda, and they would almost certainly not contrast voicedness.:
ŋ:
Most of this pattern is already here: m, and n would go with ŋ
Prenasalized stops:
Extra step between nasals and stops in the rectangle
Clicks:
Radically different sound (hard to confuse with non-clicks)
Would most likely end up being nasalized clicks, as those are easy to produce for non-click-language speakers
Ejectives:
Less, but still a different sound (hard to confuse with non-ejectives)
Both plosives and fricatives can become ejectives
I'm thinking of one of my main conlangs having (bʱ>)pʰ>ʘ, (dʱ>)tʰ>ǀ, and (gʱ>)kʰ>ǂ with some related minority languages going (bʱ>)pʰ>pʼ, (dʱ>)tʰ>tʼ, and (gʱ>)kʰ>kʼ while some other minority languages stop at (bʱ>)pʰ, (dʱ>)tʰ, and (gʱ>)kʰ. Is this at all believable or would you recommend changing things up a bit?
I just learnt how to pronounce the clicks, and as a real conlanger, discovering a new feature means creating a language around it. For ejectives, I already knew how to pronounce them, but I thought I'd just put them together in one post.
I mean, other than unplugging it the middle of data transfer of course.
So title says it all. I’m also very new to this so please be patient if I’m dumb.
I recently found a ps3 slim at a garage sale for 10 bucks. It was a no brainer, so I bought it. Plugged it in, and everything works. But there was an account on it and everything so I went to do a full system reset. But then I had to go to bed, so about 10 minutes in a clicked circle to cancel it. When I turned it back on, it seemed like it fully reseted and I cheated the system, so I set the simple stuff up and shut it off cause i had no discs.
After going to a store and picking up a couple games, I went to put one in and it went in. But it didn’t seem to read it. So I tried to eject it, and I heard the thing spin and try but it wouldn’t eject. After looking up a quick fix I angled the console downwards for a few seconds, set it flat, clicked eject again and it popped out. So that’s about it. Hope one of you know what I need to do next. Thanks!
I have this super simple backup robocopy script in my USB stick which I use to transfer some data between two computers. I would like the script to eject the USB stick after the file copying is done. I found this script to do it, so after modifying my own script a bit I got:
# Do copying
$from = $pwd.Path + "other\path"
$to = "Y:\project\path"
robocopy $from $to /E /XO
# Pause w/ custom message
function pause{ $null = Read-Host 'Press anything to eject and close Powershell'}
pause
# Eject
$driveEject = New-Object -comObject Shell.Application
$driveLetter = (get-location).Drive.Name + ":"
$driveEject.Namespace(17).ParseName($driveLetter).InvokeVerb("Eject")
However, ejecting never works if I start the script by double-clicking it (backup part works fine). If I start the script from an open powershell terminal then ejecting works. Even if I remove all the robocopy parts and the pause and only do the ejecting, it does nothing when double-clicking. Again, works fine if I start it from a powershell terminal.
I also tried putting the ejecting on a separate .ps1 file and calling it via & (also tried .) but no luck, neither of the scripts (main.ps1 and eject.ps1) do not eject when double-clicked. And everything works fine when starting from a powershell terminal.
What is going on here? Can someone share some insight on this?
EDIT: The script is in the USB drive which seems to be the issue. It works fine if I move the script. So perhaps the drive is still "in use" because the script is launched from there or something.
EDIT EDIT: Fixed it, somewhat. You seem to be able to use Start-Process to do this, but I could not get it working with a separate .ps1 file (where the ejection script is). This does initiate ejection:
#Eject
$Ejectblock= {
$driveEject = New-Object -comObject Shell.Application
$driveEject.Namespace(17).ParseName('F:').InvokeVerb('Eject')
}
#Start-Process powershell.exe -ArgumentList "-noexit -command (Invoke-Command -Scriptblock {$testblock})"
exit
But unfortunately Windows then prompts you if you really want to do it as it is in use. It does not help to use Select-Location within the scriptblock to change the powershell from the initial directory (inside the USB drive) to somewhere else. Here is the nail on the coffin: https://stackoverflow.
I dont want to go to "This PC" to right click the virtual drive to eject it. Windows can automatically mount iso's by double clicking them to open them (although autoplay doesn't work for some reason), there's also a context menu item called "Mount".
Is it possible to eject ISO's from the folder where the ISO itself is located instead of going to the This PC view?
Hello!
Like the title says, I was looking for a place to whip up a phonemic inventory with a premade chart, picturing something like toggleable phonemes, that sort of thing. There was an editable google sheet by u/TriMill a while back, which is very helpful, but not quite what I set out to find. So, I figured what the hell, and whipped one up. You can find it here: https://ipa-maker.herokuapp.com/
Essentially, you can click any phoneme and add it to your inventory. Items you've added will be in bold and will be added to the "orthography" section at the bottom of the page. Once a phoneme is in that section, you can add whatever your transliteration is if you feel so inclined. I don't currently have any kind of "save" functionality, but the "printerize" button at the bottom should make everything vaguely printer-friendly, if not particularly friendly on the eyes. You may have to futz with the margins a bit to make it work, though.
Now that being said, some disclaimers:
- I'm very much an amateur conlanger. Hell, I've never actually completed a conlang lol. So, I very well may have made some mistakes. Please let me know! I'll do what I can to patch things up in my spare time.
- I made this in like 3 days on my vacation. So it's pretty ugly and probably buggy. That and the code sucks, but hey who's counting ¯\\\_ (ツ)_/¯
- Obviously this thing is pretty bare-bones. Its only purpose is to quickly slap together a phonemic inventory and basic orthography and be on your way. If I have the time I might come back to it and add more complexity like saving, etc. But, for now, it's for making some charts quickly and easily. I hope it does that well!
Anyway, I hope this is helpful for people like me who are new to this whole thing! Please lemme know if you got any major issues I might be able to fix. Thanks!
Edit: Yo! Thanks for all the good feedback y'all. I posted this at like 2am my time so I'm just seeing everything lol. I'm happy people like it so far!
Edit 2: Just made some updates! Mostly adding those missing vowels and adding custom affricates and ejectives. Thanks for all the feedback!
This happens even if 0 tasks are active in background. Would be time that Apple Devs improve disk ejection in MacOS. Who hates such problem too?
This get worse, if you connect sync / backup rules, you set the external drive as download folder, etc.
Obviously would be much safer to avoid manual disk ejection or force ejection.
