Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I thought that regarding which language is used the transliterations at general where replaced with the language-specific one
but this is not the case
parse_ini_file() http://de.php.net/parse_ini_file
pathauto_cleanstring()
Comments
Comment #1
gregglesIt's not clear to me what you'd like to see. Can you describe it in more detail? I understand that the i18n-ascii.example.txt has language specific settings. Please clarify how should those should be used.
Comment #2
gregglesComment #3
Tobias Maier CreditAttribution: Tobias Maier commentedcurrently, the values of each section overwrite each other
Try it with "ä". you don't get "ae", but "a" because of [fi-fi]
this should not be the case.
It should get the sites' default language and load the values of [default] and overwrite them with my language-specific one (for example [fi-fi] if I selected Finnish as my sites default language)
I hope i was able to clarify it...
Comment #4
gregglesJust two more clarifications -
The additional language that will be used is from the site defined one or the user's defined one?
If locale module is not enabled then we should just use the default set and ignore the others - correct?
Thanks for this feedback, I agree this is a problem that should be solved.
Comment #5
Tobias Maier CreditAttribution: Tobias Maier commentedI don't know what language we should use.
maybe the user - or better the admin - should be able to decide.
But in general I would use the sites' language
The best thing would be to have an hook or something like this so I can change the language used with a custom module...
for example: I have a multi language blog where I introduced a cck-field to define the language used
I could create a custom _submit-function, which sets the pathauto-language to something different.
But this is no must-need
You are right - if there is no locale.module ignore the other sections
Comment #6
gregglesWell, I "fixed" this by getting rid of the sections.
I don't intend this file to be the ultimate collection of transliterations. If someone else wants to maintain it then the should step up to manage the file and the code that imports it.
Otherwise, the system is designed so that you can define site specific overrides and that's the way that it should be used.
Comment #7
(not verified) CreditAttribution: commentedComment #8
gregglesMoving back to active so that it can be worked on prior to http://drupal.org/node/147475 (swedish specific sections) going in.
Note that I don't plan to work on this.
Comment #9
gregglesand that it's a feature and that it's "i18nstuff"
Comment #10
Freso CreditAttribution: Freso commentedThis won't be worked on as it is, so marking "won't fix". Once #247758: Use Transliteration module for transliteration and #255646: Add a language parameter to transliteration_get() are both fixed, we'll work on improving on our Transliteration integration, but i18n-ascii.txt will be deprecated by then, so I don't want to waste resources on trying to properly parse the language specific sections of that file.