[TYPO3-ect] language-lables, another part for lib/div

Jan-Hendrik Heuing [DD] jhh at digitaldistrict.de
Tue Aug 29 19:19:56 CEST 2006


Hello!

True, we are not getting bored related to language stuff. First we had nice 
array's like "english|danish|german", then we had a beautiful array for 
language lables, now we got an awsom xml-array doing the same job with some 
additional parsing. But hey.. I really thought it's time for some change, 
don't you think so? :-)

To be true: I don't care a lot about how those lables are saved, as long as 
I can edit them in some handy way, and there is an API to access it. 
And -sure- it should be pretty fast ;)

There is one special case I have every now and then: There are snippets in 
that installation, which are language specific. Or Text-snippets at all. I 
am talking about things like "Search:", "Fergot my Password" and such.

So I thought I could have some table and a small backend module, to generate 
those language lables somehow. Well, so that the user can edit them.

As I am not a fan of those small and easy solutions, working within hours, I 
kept on thinking a few more moments and figured out that there is something 
we already have, the language lables.


What I would suggest is extending them:

- It should be possible to include them in an extension by default (done)
- An API should be available (done)
- A user should be able to edit PARTS of it, which you define
- The system should be flexible enough not not just work extension-wide, but 
site-wide.

What do you think?

The most easy way it seems:
- Add some getText-options to query those lables through typoscript (if not 
already available)
- Add some tabel to store those records you would like being part of the 
page, not part of extensions, this way you can make it available to 
customers through sysfolders


This is a pretty much forward solution, done in a small amount of time. Any 
feedback to this, and further thoughts? I got some other ideas about it, 
like having an interface for those xml-interface, which you can restrict and 
such. But this is all more work, and the question is if it's worth it. That 
really depends on YOUR ideas, what are your problems when doing language 
specific work?

Jan-Hendrik 





More information about the TYPO3-team-extension-coordination mailing list