Posted by klonos on February 11, 2012 at 1:07am
8 followers
Jump to:
| Project: | Transliteration |
| Version: | 7.x-3.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
There's this core bug: #646466: Machine name generating not correctly for languages other than English
...and this related (some might claim duplicate) feature request: #567832: Transliteration in core
...that I believe can be solved with this module if we take advantage of #576180: Make the machine-name generation pluggeable. Am I correct?
Comments
#1
Will take a look at this in a few days.
#2
Thanx Andrei! I'm sure that a lot of people will appreciate this. Lets us know when you have something available for testing.
I've already mentioned in #567832: Transliteration in core that I've started this issue here, but I'm not sure how many people from that issue are following this one, so if your stuck at any point try posting a comment there ;)
#3
Machine name part, I don't think every language should be transliterated.
e.g. Chinese "你好" to "nihao", I'm more like a custom name "Hello". Shouldn't make this little feature to be more complex. and doesn't worth to load a big data file or a ajax call for it.
I preferred this #1447860: Show machine name input if every character is replaced.
#4
Besides, is there transliteration for Kanji and its multiple readings? Is there something we can do about it?
#5
Well, ideally, we'd provide transliteration where possible, and the other issue would be fixed as well.
#6
#1065626: Machine name not editable if every character is replaced. just got committed!
#7
Unassigning myself as I want to get transliteration in core before working on this. Anyone, feel try to take it on :)