On Sat, Mar 08, 2008 at 11:11:02AM +0800, Jayan Chirayath Kurian wrote:
> In a DSpace batch import, the importer stops at special characters
> (e.g. &). This can be resolved by converting into its equivalent
> entity represented as "&". Is there any other solution rather
> than changing this manua
d of issues.
http://repository.ntu.edu.sg/handle/113456789/7188
http://repository.ntu.edu.sg/handle/113456789/7176
Cheers! Jayan
From: [EMAIL PROTECTED] on behalf of Mark H. Wood
Sent: Sat 3/8/2008 3:32 AM
To: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tec
Let's turn the question around. Is UTF-8 a problem for you? why?
What would you need to make it no longer a problem?
--
Mark H. Wood, Lead System Programmer [EMAIL PROTECTED]
Typically when a software vendor says that a product is "intuitive" he
means the exact opposite.
pgpwGHIvxmG5p.pgp
D
Hello,
Am 07.03.2008 um 16:49 schrieb LARC/J.L.Shipman/jshipman:
> We are running dspace 1.4.2, postgresql 8, solaris 10.
> Is UTF8 a necessity for dspace. My understanding is
> that Sun's en_US.ISO8859-1 includes most of UTF8 except
> for the far east languages. Any help is appreciated.
@nasa
On Fri, Mar 07, 2008 at 04:24:24PM +, Bram Luyten wrote:
> the database manager class relies on the fact that the database is
> UTF8. If you wish to use another standard, you will need to perform
> some adjustments in that class.
It also depends what you want to put into your repository. Can
Dear,
the database manager class relies on the fact that the database is UTF8.
If you wish to use another standard, you will need to perform some
adjustments in that class.
with best regards,
Bram Luyten
On Fri, Mar 7, 2008 at 4:49 PM, LARC/J.L.Shipman/jshipman <
[EMAIL PROTECTED]> wrote:
> We
We are running dspace 1.4.2, postgresql 8, solaris 10. Is UTF8 a
necessity for dspace. My understanding is that Sun's en_US.ISO8859-1
includes most of UTF8 except for the far east languages. Any help is
appreciated.
757-864-7114
LARC/J.L.Shipman/jshipman
[EMAIL PROTECTED]
-
7 matches
Mail list logo
