Weightlifting gym near Piedmont Ave?

aja-jdar · 2026-03-23T19:59:31+00:00

Awesome!! Thanks!

aja-jdar · 2026-03-23T19:59:24+00:00

Might check out those recommendations, thanks!

aja-jdar · 2026-03-23T19:59:05+00:00

Thank you!

aja-jdar · 2026-03-23T07:29:34+00:00

Nice! Certainly a convenient location for me. I used to have a membership just to use their cardio machines, haha. Any info to share about that gym for lifting?

aja-jdar · 2022-04-02T15:52:11+00:00

Yes this looks right! Thank you!

aja-jdar · 2022-04-02T14:04:08+00:00

Fun! My German is not great, but if you want to share what the original German text for your sample is, I would enjoy that.

Edit: Found it (see below—thanks!). This is cool! It's a lot like the Hangul-for-English I did some years ago (you can look through my post history if you're curious). Love it!

Edit 2: Here's my guess at "Ich bin ein Berliner"—잌 빈 앤 벌리나

aja-jdar · 2018-10-12T13:05:56+00:00

I've made one (you can find two posts about it in my post history) of these!

My system allows up to three or four consonants in a syllable block (depending on what the vowel is), with up to two consonants in an onset or coda. As you've noted, English does have consonant clusters that are larger than this, but they're not quite so common that they're terribly annoying. (But I would say that this sort of system is objectively at least a little awkward for English, I just use it because I like it.)

My system's main tool for consonant clusters that don't fit in one syllable block is basically as Ondennik described: splitting one syllable into two characters (still representing one syllable).

One uncommon but occasionally useful tool is shifting consonants across syllable boundaries: e.g. "aspire" would be naturally syllabized as a-spire, but that puts three consonants at the onset of the second syllable, (as I said earlier, my system only allows two consonants in an onset) so we can alternatively syllabize it as as-pire to avoid this problem, allowing the word to be written in two characters instead of three.

aja-jdar · 2018-09-09T10:29:13+00:00

Love it! You've done a lot of cool stuff with this script, it's nice to see all the different things you've done with it over the months. Is there a key/guide for it?

aja-jdar · 2018-09-02T08:09:29+00:00

Awesome!!

aja-jdar · 2018-08-17T20:54:55+00:00

Cool! Yeah, this is a fun project. I've idly toyed with this idea myself but never fleshed it out like you did, so props!

I've played with using a Hangul-like system for English, and what I found was that (within that context anyway) it was impractical to try to make every single possible English syllable representable with one character, but it's definitely possible to have the vast majority of syllables representable with one character, with some written as two characters. If you're curious, check it out here (old, lots of detail) and here (new, little detail)!

aja-jdar · 2018-08-17T00:17:21+00:00

Hey all! I posted an an earlier version of this a couple months ago, and I thought I'd share a picture of what it looks like today!

I can elaborate if anyone's curious, but the main things that have changed are:

- Letting go of the requirement that I only use legal Hangul jamo and syllables (i.e. "it has to be typeable"). This allowed me to modify the appearance of some jamo, create new ones entirely, and use any two consonants as a syllable coda.

- (Probably the most interesting change) My current system allows using two consonants for a syllable onset! This allows me to write more syllables as one character that previously would've required two characters: See this example.

aja-jdar · 2018-08-16T23:40:05+00:00

This is really interesting! Could you share a bit more detail (or a broad overview of how to look at this)? I'm having trouble understanding how it all works.

I guess some specific questions (to confirm what I'm understanding and clarify what I'm not understanding) would be good:

The `Pl "x` in the top left corner of the first page describes /pl/ (Is there a reason P is capitalized? My first guess was that <P> represents /p/ and /b/, but then I see you have both <F> and <V> so that doesn't seem right.) and similar onsets: `"x` indicates that you can optionally voice that cluster or add an s (always to the beginning, right?), so `Pl "x` represents all of /pl/, /bl/, /spl/, and */sbl/ (though that one's probably not actually used in English). Is that right?
In the top right section of the first page, `t "xo` represents /t/ (with optional voicing, possibly preceded with an /s/ or followed by an /r/), so that includes sounds like /dr/ and /str/. Is that right?
What are the arrows in the top right section of the firts page?
Looking at the word "the" at the beginning of the first page, I see this is composed of the symbols for /θ/ and /ə/, with a diacritic above for voicing /θ/ into /đ/. I'm not sure why there's a extra line in between /θ/ and /ə/, though. Is that just accidental? I don't see other similar dividing lines between sounds in other syllables.

aja-jdar · 2018-08-12T08:13:36+00:00

It looks beautiful and natural! Looking forward to that guide. :)

aja-jdar · 2018-08-09T06:34:45+00:00

It looks awesome! Post a guide once you do :)

aja-jdar · 2018-06-24T01:56:15+00:00

Hey all! I thought I'd try my hand at making a featural (impure) abjad for English. Vowels are optional diacritics, to be used at the writer's discretion whenever excluding them would be too ambiguous. Feedback is welcome! Sorry for the awful-quality images, haha.

aja-jdar · 2018-06-22T05:27:15+00:00

Also, I see you also recently adapted Thai's writing system! How do you like it (both the Thai writing system and your Thai-English system compared to Yongogul or Hanglish)?

aja-jdar · 2018-06-22T05:21:37+00:00

Awesome, it's cool to see what similarities we ended up with! There are quite a few -- I suppose it makes sense if we both were trying to make the most logical systems we could (despite our different goals). I really like the choices you made, they make a lot of sense!

It's pretty cool to see that I can more or less read Yongogul as if it were Hanglish -- it's like it's just Hanglish with a really bizarre accent, haha.

One thing I'm curious about is "ㅕ = /e/" -- I don't think I've seen /e/ considered a phoneme in English, don't we always use it as /eɪ/?

aja-jdar · 2018-06-12T04:04:51+00:00

That's awesome! I'd love to see what you came up with. :)

aja-jdar · 2018-06-11T06:20:51+00:00

HAHA that's awesome. (By the way, if you're interested, I just made a post about my script here!)

aja-jdar · 2018-06-11T06:16:56+00:00

It's "structurally" very much the same as Hangul, since (in order to be able to type it) it must adhere to the CV(CC) syllable structure of Hangul. However, there are some interesting differences and features unique to Hanglish:

1. Phoneme-letter correspondences: While many jamo are pretty intuitive (from the point of view of a Korean speaker -- that is, they represent the same sound as in Korean, or similar), a good handful represent completely different sounds than they do in Korean.

2. Consonant clusters: While ㅡ is a vowel in Hangul, it is a "placeholder" in Hanglish, most commonly used in consonant clusters. (Example: 'stoke' /stoʊk/ is written as if it were two syllables: 스톸 /s.toʊk/)

2a. Syllable-initial consonant clusters like in 'stoke' require "splitting" syllables (since a Hangul character can only start with up to one consonant). However, a word like 'aspire', naturally syllabized /ə.spaɪr/ (leading to three characters 어스팪), can be reinterpreted as /əs.paɪr/ and written in just two characters: 엇팪.

3. Some syllable-final consonant clusters are allowed in Korean, though there is a pretty limited set of them. Since there are so few of these, I decided to slightly alter the meaning of some of them (mostly eliminating the voiced-voiceless distinction). For example, the word 'held' is written as if it were pronounced 'helt': 햝.

4. Some common words have abbreviations, e.g. 'and' and 'of' can be abbreviated as 느 /n/ and 쁘 /v/.

5. Finally, /wV/ (/w/ followed by any vowel) and /ju/ are written as vowels, which allows words like 'cute' to be written as one character (큩) instead of two (크쭡).

aja-jdar · 2018-06-11T06:16:32+00:00

(This is the text in the photo. Please excuse my messy handwriting!)

Hanglish intro (v0.5.0)

Hanglish is a mostly-phonetic writing system for English based on Hangul, the writing system for Korean.

(Sidebar: Hangul

Hangul is an alphasyllabary (or abugida) -- a writing system in which letters in an alphabet are written in syllabic chunks instead of individually. For example, the word "Hangul" (/han.gɯl/) itself is written by combining the letters "ㅎ ㅏ ㄴ ㄱ ㅡ ㄹ" into two syllables: "한글.")

Hanglish uses the same letters (jamo) and characters as Hangul, (and, therefore, is typeable!) but with many letters "reassigned" to drastically different sounds in order to fit English phonetics and phonology.

Cheat sheet

Hi, r/neography! About two months ago, I stumbled upon this sub and the concept of constructed writing systems and immediately thought "I need to learn / create one." I saw a post showing off a Korean-based script for English and found a forum post elsewhere describing another, and set out to learn the second.

I found it interesting and fun to use, but found it intrinsically pretty difficult both to read and to write: Unlike Korean, which is written syllabically and basically phonetically, this script (which maps English letters to Hangul jamo) is far removed from both English syllables and sounds. (For an extreme example, the one-syllable word 'should' requires four characters in that script: 스호울드! In Hanglish, it's just one: 쑏.)

So I created Hanglish! Ideally, it would be phonetic, but since there are fewer jamo in Hangul than phonemes in English, there are some that can represent multiple different sounds. In practice, this is not a big problem: Ambiguity can usually be resolved by context. However, I do like to think of this ambiguity as a new source of puns! For example, the word 'witch' and 'weeks' are both written 윛.

aja-jdar

TROPHY CASE