Links
Tags
Creators
Details
0.2.0+mc1.21.10
Compatibility
Changes
Modern Hangul Jamo Composed Syllables
Support for composing modern Hangul Jamo into Hangul syllables. This only supports modern jamo and follows the composition calculation to map proper jamo sequences to pre-composed Unicode characters.
Also now includes fabric-resource-loader-v0 just in case so textures will for sure show. Would have silently needed Fabric API.
Technicals (updated)
The internals are still being polished. You can check the first few lines of
the GlomphoscheImpl class and even the mentioned Node classes there that you
may find of interest.
import io.github.startsmercury.glomphosche.impl.client.GlomphoscheImpl;
import net.minecraft.network.chat.FontDescription;
class Example
{
void initialize()
{
// register modern Hangul Jamo handler, or your own handler
// for a different use, if you implemented one
GlomphoscheImpl.ROOT
.inner()
.add(new ComposableHangulJamoNode());
// the letter 'f'
Node node1 = GlomphoscheImpl.LOOKUP
.computeDiscreteIfAbsent('f');
// the theoretical glyph 'fi'
Node node2 = node1.getOrCreate('i');
// register the font that retextures 'f' as the glyph representing 'fi'
node2.register(FontDescription.DEFAULT); // replace with your own
// This one is for 'ffi' by retexturing 'f'
GlomphoscheImpl.ROOT
.getOrCreate('f')
.getOrCreate('f')
.getOrCreate('i')
// replace with your own
.register(FontDescription.DEFAULT);
}
}
Acknowledgements
Great help from https://steve-p.org/korean/. Explained the concepts and had the formula to calculate the precomposed syllables!
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| glomphosche-0.2.0+mc1.21.10-sources.jar | Unknown | 26.78 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:n48fBTaW:CR3sqEGz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:n48fBTaW:CR3sqEGz"
}

