Project

General

Profile

Actions
Copy link

Bug #23527

closed

Not possible to use different transliteration for same letter in different language

Added by Tanel Põld about 14 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-09-12
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

For example:

German transliteration for Ä = AE and Estonian transliteration for Ä = A
Both use latin iso-8859-1 character set.

Setting Estonian transliteratin to the end of the file t3lib/uniadata/Translit.txt overwrites German.

Makes it impossible to use RealURL and folder/file renaming in multilingual multilingual environments where languages share char set but transliterations must be different for same letters.

(issue imported from #M15687)

Actions
Copy link
 #1

Updated by Stefan Neufeind about 14 years ago

Used in typo3_src-4.4.2/t3lib/class.t3lib_cs.php, function initUnicodeData($mode=null)

Hmm, I don't see how this would be possible with the current setup because it always uses just the one file you mentioned:

// process custom decompositions
                $customTranslitFile = PATH_t3lib.'unidata/Translit.txt';
                if (t3lib_div::validPathStr($customTranslitFile) && @is_file($customTranslitFile))      {

That's not a "per-language"-thing or so.

You'd mean we'd need a more fine-grained solution for the Translit-thing in general that would allow prefering one language over the other by providing a TypoScript-var which can be set based upon the website-language to use?

Do you know other such examples, maybe also for other languages? Do you how of a list available somewhere which shows how to "decompose" certain characters in various languages?

Actions
Copy link
 #2

Updated by Alexander Opitz about 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions
Copy link
 #3

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions
Copy link
 #4

Updated by Tanel Põld over 10 years ago

Think I have missed the feedback...Sorry.

But yes the problem is still active in latest TYPO3 versions and I think NEOS as well.

Exactly:

You'd mean we'd need a more fine-grained solution for the Translit-thing in general that would allow prefering one language over the other by providing a TypoScript-var which can be set based upon the website-language to use?

Transliteration rules are language specific. I have hard time finding documentation for different languages. Probably not so well documented at all.

Right now I'm overwriting the rules as shown below. But it means I can't have correct transliteration in both languages, German and Estonian.

Estonian transliteration rules I'm using in Translit.txt:

00C4; 0041;        LATIN CAPITAL LETTER A WITH DIAERESIS => A 
00E4; 0061;        LATIN SMALL LETTER A WITH DIAERESIS => a                 
00D6; 004F;        LATIN CAPITAL LETTER O WITH DIAERESIS => O 

00F6; 006F;        LATIN SMALL LETTER O WITH DIAERESIS => o 

00DC; 0055;        LATIN CAPITAL LETTER U WITH DIAERESIS => U 

00FC; 0075;        LATIN SMALL LETTER U WITH DIAERESIS => u 

00D5; 004F;        LATIN CAPITAL LETTER O WITH TILDE => O        
00F5; 006F;        LATIN SMALL LETTER O WITH TILDE => o

Actions
Copy link

Also available in: Atom PDF