Jin (Korean surname)
Jin (진) is the romanization of a number of Korean surnames, written as 陳, 秦, 眞, or 晉 in hanja.
| Jin | |
| Hangul | 진 |
|---|---|
| Hanja | |
| Revised Romanization | Jin |
| McCune–Reischauer | Gin |
陳 (Chen:첸)
Jin (陳), the most common version, derived from the Chinese surname Chen.
- Jin Soo (陳秀) from Song Dynasty—13th century
- Jin Woo Ryang (陳友諒) from Ming Dynasty—13th century
- Jin Lin (陳璘) from Ming Dynasty—16th century
秦 (Qin:친)
Jin (秦) is derived from the Chinese surname Qin (surname).
- during the 7th century Tang Dynasty, Jin Pil Myung (Chinese: 秦弼明; pinyin: Qin Biming) was a Tang general who participated in the Conquest war of Silla, and later returned to China.
- during the 13th century Song Dynasty, another Jin (秦) family emigrated from China to Goryeo, becoming the Modern Korean Jin (秦) family.
眞 (Zhen:전)
Jin (眞:Zhen), Korean surname of Baekje, Silla, Hubaekje.
- Jin Godo (眞高道), general of Geunchogo of Baekje
- Jin Mu (眞武), prime minister of Baekje
- Jin Gong (眞功) was prime minister of Silla
- Jin Ho (眞虎), prime minister of Hubaekje
晉 (Jin:진)
Jin (晉:Jin)
- Jin Ham Jo (晉含祚) was officer of goryeo
- Jin Sun-Kuk (born 1970), South Korean track and field sprinter
gollark: I can write some code for this if desisred.
gollark: Surely you can just pull a particular tag of the container.
gollark: I can come up with a thing to transmit ubqmachine™ details to osmarks.net or whatever which people can embed in their code.
gollark: It's an x86-64 system using debian or something.
gollark: > `import hashlib`Hashlib is still important!> `for entry, ubq323 in {**globals(), **__builtins__, **sys.__dict__, **locals(), CONSTANT: Entry()}.items():`Iterate over a bunch of things. I think only the builtins and globals are actually used.The stuff under here using `blake2s` stuff is actually written to be ridiculously unportable, to hinder analysis. This caused issues when trying to run it, so I had to hackily patch in the `/local` thing a few minutes before the deadline.> `for PyObject in gc.get_objects():`When I found out that you could iterate over all objects ever, this had to be incorporated somehow. This actually just looks for some random `os` function, and when it finds it loads the obfuscated code.> `F, G, H, I = typing(lookup[7]), typing(lookup[8]), __import__("functools"), lambda h, i, *a: F(G(h, i))`This is just a convoluted way to define `enumerate(range))` in one nice function.> `print(len(lookup), lookup[3], typing(lookup[3])) #`This is what actually loads the obfuscated stuff. I think.> `class iｎt(typing(lookup[0])):`Here we subclass `complex`. `complex` is used for 2D coordinates within the thing, so I added some helper methods, such as `__iter__`, allowing unpacking of complex numbers into real and imaginary parts, `abs`, which generates a complex number a+ai, and `ℝ`, which provvides the floored real parts of two things.> `class Mаtrix:`This is where the magic happens. It actually uses unicode homoglyphs again, for purposes.> `self = typing("dab7d4733079c8be454e64192ce9d20a91571da25fc443249fc0be859b227e5d")`> `rows = gc`I forgot what exactly the `typing` call is looking up, but these aren't used for anything but making the fake type annotations work.> `def __init__(rows: self, self: rows):`This slightly nonidiomatic function simply initializes the matrix's internals from the 2D array used for inputs.> `if 1 > (typing(lookup[1]) in dir(self)):`A convoluted way to get whether something has `__iter__` or not.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.