From: Torsten F. <to...@fa...> - 2012-08-31 17:15:19
|
Karsten, I agree, that it seems to be the best shortterm solution to do it with a "de-formal", especially as you are prepared to contribute to the maintaining. I will add a folder for that into the repsitory, for that you can use the i18n.tiki.org website to translate directly into the Tiki core. Please mind, that there is some time delay to get this into the downlodable files. In respect to that you should get commit access to be able to translate locally into your language.php and commit the updates to the core. Did you ever have been working with a version control system, especially with SVN? Gregor and me could explain that to you if necessary. In my mind it would be the easiest, if you work with Linux, but there are also tools for Windows and Mac. I will write you off-list, when I prepared the folder and files. Please consider to join the 'German Language User Group' and the german mailing-list, if not yet done. Cheers Torsten Am 31.08.2012 15:09, schrieb Karsten Wemheuer: > Hi Torsten, > > thanks for Your response. > > I agree, that alternative A is not a good solution. I think, the same > disadvantages are valid for alternative "B" (Every webmaster have to do > it by his own). Your Idea with language options sounds pretty good. > > As I am looking for a solution based on Tiki 9.0, I think, "language > options" are currently no alternative for me. They will (if ever) be > implemented in trunk, I think. > > I'll try the "de-formal" approach (as told off list). I'll keep You and > the list informed. > > Cheers, > > Karsten > > Am Freitag, den 31.08.2012, 12:35 +0200 schrieb Torsten Fabricius: >> Hi Karsten, >> >> this is a quite good catch and we should think about how to get away >> with this problem in the most efficient way in respect of maintaining >> two nearly identical language variations. >> >> It would be easy to setup an alternative language folder for formal >> German "de-formal", but right now I am not really convinced, if that >> would be the best way to do it - because most of the content would be >> exatly the same than the existing informal "de", which is mainly >> maintained by Gregor and only a few other users. >> >> If we do so, then somebody would have to merge all new translations >> and fixes from "de" to "de-formal" or else "de-formal" would be >> outdated quiet soon! >> >> What would be the alternative? >> >> A) manual customisation for each website >> >> local addings to the individual websites language.php seem not to be >> appropriate, because this would not be in the Tiki core and each >> webdeveloper/webmaster had to maintain formal-language by himself >> At each upgrade (FTP and SVN) the customisations would have to be >> manually copied into the new version - additionally danger of >> data-loss for the SVN version. >> >> B) translation in the database >> >> we have already the possibility to translate in each Tiki in the >> database, which generates a custom.php for every language folder which >> gets manually made translations in Tiki. >> For ex. translate en-de in tiki-admin.php?page=i18n and from >> the first translation on a custom.php is created by the Tiki >> in the folder /lang/de >> This aswell is a local project based approach and not appropriate for >> a more global problem like a formal language variation. But at least >> there is no danger of data-loss for the SVN version. >> Question: I do not know, if the custom.php "overrides" the >> language.php like "cascading language sheets" (like the CSS >> options override the default CSS in a cascading style sheet) >> >> C) language options >> >> Given that language variants like "Lower German" or "Swiss German" are >> languages by itself whith a quite large amount of different vocabulary >> and grammar, it makes sense to set them up as individual languages. >> >> But a formal variation of German would be just guessed about 95% the >> same - especially the vocabulary would be different. >> >> My idea is to split the language.php in three parts -> 1) common >> language.php 2) option1 informal.php 3) option2 formal.php >> >> This way we would not have to maintain the same language at two places >> and it would suit the needs of many people and projects. >> >> BUT it would need a little bit of recoding. If you and Gregor would >> agree with me that this would be a good idea, I would write this into >> the german-language-user-list and I would setup a feature request on >> this. >> >> I believe that there are a few languages out there, which use >> formal/informal variations. >> Can you imagine, that you company would fund the coding of >> that feature? If s.b. could pay one of the developers, this >> should be possible to get in Tiki right away and I assume, >> that this would not be such a big hack - I do not know, as I >> am not a coder by myself. >> BTW: did you already join the german language user group at >> http://tiki.org/GLUG ? >> At the moment is mostly to know who else of the registered users speak >> the language and to have a listed overview about german language spots >> inside the community. >> >> Cheers >> Torsten >> >> >> Am 31.08.2012 10:17, schrieb Gregor Adamczyk: >> >>> Hi Karsten, >>> >>> >>> this issue was discussed whithin GLUG (german translation user >>> group). We decided to stay with "Du" as it's commonly used. So >>> please don't change lang/de files to "Sie". >>> >>> >>> >>> But feel free to start a formal translation (via i18n or svn), if >>> you want to. As tiki is almost 100 % translated it should'nt be >>> difficult - but time consuming. If I have some time to spare I'll >>> assist you. >>> >>> >>> >>> Gregor >>> >>> ____________________________________________________________________ >>> Von: Karsten Wemheuer <kw...@gm...> >>> An: tik...@li... >>> Gesendet: 9:55 Freitag, 31.August 2012 >>> Betreff: [Tikiwiki-users] German language translation >>> >>> >>> Hi list, >>> >>> tikiwiki has international support for the German language. In >>> German >>> there are two different forms to address "You": the more privately >>> used >>> "Du" and the more formal used "Sie". As we want to setup tikiwiki >>> for >>> usage by our customers, we want to use the formal way. >>> >>> The official translation available in tikiwiki is the more privately >>> used form "Du". Is a translation for the other form available? If >>> not: >>> Is patching the files in language/de the right way? Or should I >>> create a >>> new directory in language (maybe de-formal) >>> >>> Thanks, >>> >>> Karsten >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. >>> Discussions >>> will include endpoint security, mobile security and the latest in >>> malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> TikiWiki-users mailing list >>> Tik...@li... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-users >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> >>> >>> _______________________________________________ >>> TikiWiki-users mailing list >>> Tik...@li... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-users >> -- >> Torsten Fabricius >> fon: +49 178 8 272 383 >> to...@fa... >> to...@ti... >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ TikiWiki-users mailing list Tik...@li... https://lists.sourceforge.net/lists/listinfo/tikiwiki-users > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TikiWiki-users mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-users > -- Torsten Fabricius fon: +49 178 8 272 383 to...@fa... to...@ti... |