Menu
▾
▴
Re: [VuFind-General] Facet-translation problem after upgrade to 1.4
|
From: Katharina W. <wol...@fh...> - 2013-02-08 13:28:41
|
Hi again, if I remember correctly, you're using Windows as a desktop yourself, Demian, so I wonder, if the only reason you're using jEdit to manage the language files is it's Unicode support? I've had a look at the sorting options (through a plugin as well) of my favourite editor Notepad++, which also comes with Unicode support and a _lot_ of other _really_ nice things (including svn + git plugins) - and with the TextFX-plugin you can choose to "Sort lines case sensitive (at column)" or "Sort lines case insensitive (at column)"... Perhaps that sounds intersting enough for you to have a look at notepad++ (especially as another option of the TextFX-plugin is "+Sort outputs only UNIQUE (at column) lines")? I haven't yet used these options since I haven't had a task which would have fitted the tools (or the other way round) but as far as I can guess it sounds promising. :-) Kate Am 08.02.2013 13:30 schrieb Demian Katz: > Don't worry, I understand that it's a big job! If it weren't, I would just do it myself -- I really hate saying "no" to a reasonable request. > > But certainly, if nothing else, it is helpful to have somebody paying attention to the issue. Even if we're just reminded that it exists every few months, that helps improve the odds of someone being around who is willing and able to take on the challenge. > > Regarding the sorting issue, I think we may have discussed this before, but I'll risk repeating myself to be on the safe side. The current sort order is a side effect of the tools I use. jEdit is the best text editor I've found for managing the language files, since it has good Unicode support. jEdit includes a plugin that sorts text -- but it sorts it in pure ASCII order, putting uppercase before lowercase. I can't find a simple, convenient way within the editor to sort in a more human-friendly way, so I do this since ASCII-sorted is better than not-sorted-at-all, especially since having them sorted this way allows me to use other jEdit tools to automatically remove duplicate lines, etc. Obviously, if I put some time into it, I could probably find a better way with different tools (or maybe even just different jEdit plugins); but this has been an easy way for me to manage the language files, so I've stuck with it. If somebody knows of a better workflow or better tool s for d oing the job, I'll be happy to adapt -- I just haven't found a solution quickly and haven't had time to do detailed research. > > Also, while I agree that sorting in a more human-readable way would make the language files a bit easier to read and understand, I don't know that it really helps too much with the problem of avoiding duplicate entries. For most texts that you would want to add to the file, you need to do full-text searches of a variety of keywords to make sure that there isn't already a string there that mentions the concept you are trying to add -- there are always several ways to express a particular concept, and the key word(s) aren't always at the beginning of the string, so browsing alphabetically usually isn't the best way. (At least, that's the way I've been doing this -- and that's why the weird sorting hasn't really been an inconvenience for me when managing the files). > > - Demian > ________________________________________ > From: Katharina Wolkwitz [wol...@fh...] > Sent: Friday, February 08, 2013 3:25 AM > To: vuf...@li... > Subject: Re: [VuFind-General] Facet-translation problem after upgrade to 1.4 > > Hi Demian, > > I've found the pages on translation in Vufind 2.0 after writing my last email, > so I have to apologise for calling out so loudly for a revamp, that had indeed > already taken place. > > But even as I can understand your need for a shepherd or sherpherdess, I'm > afraid that job is way to large and complicated for me to take on. I could > volunteer for a job as parttime sheepdog though, if such a position was on > offer. ;-) > > Offering as my first wooof: > I've found that the example en.ini-file listed on the wiki-page for translation > in Vufind 2.0 > http://vufind.git.sourceforge.net/git/gitweb.cgi?p=vufind/vufind;a=blob;f=languages/en.ini;hb=HEAD > is still not sorted strictly alphabetically but listing Uppercase before lower > case, thus making it possibe to have in total three places to find a phrase > beginning with the word "and" (AND, And, and), which is quite a lot if one's not > sure of the correct "spelling" (???). If one now adds the possibility of spaces, > underscores, hyphens and slashes to the mix I get the feeling, it's easier to > create a duplicate entry than finding the one that already exists. > > I'm not really sure how to avoid the problem of creating unwanted duplicate > entries in the language.ini-files, but I'd think sorting them case-insensitive > and thus more alphabetically would help. > > Kate > > Am 07.02.2013 17:47 schrieb Demian Katz: >>> Btw. are there translation-lists of language-"names" for the most-common (from >>> my point of view) languages (e.g. english, german, french, spanish) as an >>> "add-on" to the respective language .ini-files (en.ini, de.ini, fr.ini, >>> es.ini)? >> >> I'm sure these can be found somewhere if you look hard enough, but I don't have a reference available off the top of my head. >> >>> Is the translation-system getting a revamp in Vufind 2.0 like the programming >>> is? I think something like a having a good look at what's there and giving it >>> a good stir might be a good idea... ;-) >> >> I've already revamped the code for VuFind 2.0's translation system. It has a couple of important new features: >> >> 1.) A flexible mechanism for including tokens within messages... so you can translate a string like "<a href='%url%'>Export to %target%</a>." (In this example, %url% and %target% would be the same in all language files, as would the HTML markup, but the rest could be changed as needed). >> >> 2.) The ability to specify a default text to use if no match is found in the language files. This makes it possible for us to add more prefixes to strings within the language files to reduce ambiguity and improve organization without worrying about users seeing bizarre strings on screen if the language files are incomplete. For example, rather than having strings like "Book" in the file, we could use "facet_format_Book" and default to "Book" as the text if no translation for "facet_format_Book" is found. >> >> So that's the good news. >> >> The bad news is that in order to take full advantage of these new features, somebody needs to do a deep analysis of the text in our language files and how/where that text is used in our templates. We need to do a lot of cleanup -- being consistent about putting punctuation in the language strings in the file rather than hard-coding it in the templates, prefixing facet values as mentioned above, putting together chunked text into strings with tokens to allow better rearrangement in languages with different grammatical structures, etc. Unfortunately, this is a huge project that I don't have time for -- I think good translation support is important, but since my own institution only offers the interface in one language, it's hard to justify spending weeks or months on this kind of a revamp. >> >> I think in order to happen, somebody needs to volunteer to shepherd the project through. I'm definitely happy to support and advise such an effort; I just can't commit to doing it myself. Anybody interested? >> >> - Demian >> > > > -- > Mit freundlichen Grüßen > > Katharina Wolkwitz > > Fachhochschule Südwestfalen > Hochschulbibliothek > Haldener Straße 182 > 58095 Hagen > Tel.: 02331/9330-607 > FAX: 02331/9330-608 > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general > -- Mit freundlichen Grüßen Katharina Wolkwitz Fachhochschule Südwestfalen Hochschulbibliothek Haldener Straße 182 58095 Hagen Tel.: 02331/9330-607 FAX: 02331/9330-608 |