use of different languages

I am not a heavy user of Biblioscape but I should be one.

I need bibliography information all the time and as a matter of fact I have now a project which based entirely in bibliography.

However I have a problem which I have never been able to solve completely.

My bibliography database contains a lot of books in Hebrew and also in Portuguese. Occasionaly also in French and Spanish which use basicly the same accented letters as Portuguese. What is actually happening is that any accented letter shows as an Hebrew letter.

I use Windows XP and in other programs I normaly have the possibility to write in both Portuguese and Hebrew. One good exemple is Microsoft Word.

Does anybody have a solution for me?

I will appreciate your inputs.

Inacio

Mixed language text and cut and paste

This may be a symptom of the same problem. I have just started loading a heap of references from rich text format files. They contain titles like "SADDUCEES; Saddoukaios (Σαδδουκαιος)." and so have a bit of Greek (and in other cases Hebrew or Syriac) and a bit of English. The notes associated with these references also contain a mix of languages. If I cut and paste such references or notes from electronic references into even the humble MS Wordpad then my formatting is preserved (as it appears to have been when I pasted the above example into this comment). However, I was surprised to find that when I try to do the same into a Biblioscape note or title field, then all the non-English text was converted to strings of question marks. Am I right in thinking that this is also a Unicode support related problem and if so then do you have any sort of target date for a release which will provide the necessary changes (my next few projects are likely to need a lot of this type of notes). If not, then is there any way I can work round it?

There is no get around for

There is no get around for the unicode problem. One of the main goals of version 8 is unicode support. I don't have a date for it. But I am sure it won't happen in 2008. We will continue to add new features in each 7.x patch releases this year.

Unicode is not supported in Biblioscape yet

I don't know Hebrew. But I think the problem is caused by the lack of unicode support in Biblioscape. For most western languages, the first 255 chars will do it. This is supported by most other character set as well like Chinese, Japanese, Korean. So you can have Chinese and English records at the same time. But because Biblioscape does not support unicode, you can't mix Chinese with Japanese. This can only be made possible when unicode is supported. It won't be in version 7. May be in version 8.

Paul 

I vote for Unicode support

I suggest that Unicode is a matter of priority. Mixed-language referencing is a must these days in most research writing I see and I know a few people who abstain from all bibliographic software because of poor support for this.

Can we have a separate project made for this please?

A new project added for unicode support in database

I have just added a new project for unicode support in database at http://207.36.181.237/project/unicode_database. I am sure unicode won't be supported in version 7. But we plan to add unicode support when we move to dot net. That means unicode support only under dot net, not Win 32.

Hebrew and Portuguese

Hebrew seems to be working alright.

The problem is with Portuguese, Spanish and French in which the accented letters appear as Hebrew letters.

Windows settings

If you are getting Hebrew but not Spanish, French, Portuguese, it is a result of your Windows settings. (The alternative would be to get Spanish, French, and Portuguese, but not Hebrew.) In Control Panel, if you go to "Regional and Language Options" (at least that is what it is called in XP Pro), you will see a tab that says "Advanced". On that tab, there is a setting for language to be used for non-Unicode programs. Among other things, this controls how Windows interprets character codes (i.e. what code page to use). For example, if you have Hebrew selected, the hex character codes E0, E1, E2, and E3 will ne interpreted as א ב ג ד, while if you have some Western language selected (such as English), they will be interpreted as à á â ã. The former is good if you want Hebrew, the latter if you want French/Spanish/Portuguese.

Without Unicode, or at least Biblioscape-internal support for multiple code pages, there is no way to get all these languages to cooperate. (In the Notes, it is possible to use multiple code pages.)

Yehuda N. Falk
Associate Professor of English Linguistics
The Hebrew University of Jerusalem

I´ve been working with

I´ve been working with french, portuguese and spanish (even some slovenian) authors and titles, and never had real problems in Biblioscape.

By now, the problems I have with latin languages are 1) a wrong alphabetization order and 2) a diminished capacity to search (Biblioscape seems not recognize á, ç, ü...

The charactes you mention in hebrew could be the major problem... why you do not try all the latin references in a database and the hebrew in another?

 

 

For sorting order in another

For sorting order in another language, please see http://207.36.181.237/node/59

Biblioscape Fast Search does have a problem with umlauts. We will try to fix this problem in future release.

Wester European + Russian

Is it possible to mix these so that different references are in different languages in one database? How? It does not seem to work for me...

If it is not possible - can I reiterate that Unicode support is a priority (I am guessing Unicode is THE solution in the long run).

som Western European +

som Western European + Russian should not be a problem. If your Windows default language is set to Russian, the Russian character set should include all the characters commonly used in English (I am not sure about others). Unicode will be added when we move to .net.