From: Karla S. <sm...@wi...> - 2013-02-27 20:09:52
|
Hi, I just got a report from staff that diacritics are not displaying properly in the call number on the holdings table. They display fine elsewhere--including the call number found in the 999 field where all the other holdings info is. Here's an example: http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=AllFields&submit=Find Any suggestions how to fix this? I am on v1.3. Thanks, --Karla Karla Smith, ILS Manager Winnefox Library System Oshkosh, WI 54901 sm...@wi... |
From: Demian K. <dem...@vi...> - 2013-02-27 20:50:27
|
It probably means that your ILS driver is not returning the call numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or some other format and need to be converted before being passed to VuFind. (There were some problems like this in the Voyager driver that were resolved fairly recently -- probably between 1.3 and 1.4; I wouldn't be surprised to see similar things in other drivers). Let me know if you need more details! - Demian > -----Original Message----- > From: Karla Smith [mailto:sm...@wi...] > Sent: Wednesday, February 27, 2013 3:08 PM > To: vuf...@li... > Subject: [VuFind-Tech] Diacritics in call numbers > > Hi, > I just got a report from staff that diacritics are not displaying properly in > the call number on the holdings table. They display fine elsewhere--including > the call number found in the 999 field where all the other holdings info is. > > Here's an example: > http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=AllFields& > submit=Find > > Any suggestions how to fix this? I am on v1.3. > > Thanks, > --Karla > Karla Smith, ILS Manager > Winnefox Library System > Oshkosh, WI 54901 > sm...@wi... > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: Karla S. <sm...@wi...> - 2013-02-27 21:36:05
|
Thanks..I need mroe details, please! Are you referring to the driver.pl script that resides on our ILS server, or the Unicorn.php driver? --Karla On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: > It probably means that your ILS driver is not returning the call numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or some other format and need to be converted before being passed to VuFind. (There were some problems like this in the Voyager driver that were resolved fairly recently -- probably between 1.3 and 1.4; I wouldn't be surprised to see similar things in other drivers). > > Let me know if you need more details! > > - Demian > >> -----Original Message----- >> From: Karla Smith [mailto:sm...@wi...] >> Sent: Wednesday, February 27, 2013 3:08 PM >> To: vuf...@li... >> Subject: [VuFind-Tech] Diacritics in call numbers >> >> Hi, >> I just got a report from staff that diacritics are not displaying properly in >> the call number on the holdings table. They display fine elsewhere--including >> the call number found in the 999 field where all the other holdings info is. >> >> Here's an example: >> http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=AllFields& >> submit=Find >> >> Any suggestions how to fix this? I am on v1.3. >> >> Thanks, >> --Karla >> Karla Smith, ILS Manager >> Winnefox Library System >> Oshkosh, WI 54901 >> sm...@wi... >> >> >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_feb >> _______________________________________________ >> Vufind-tech mailing list >> Vuf...@li... >> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > Karla Smith, ILS Manager Winnefox Library System Oshkosh, WI 54901 sm...@wi... |
From: Demian K. <dem...@vi...> - 2013-02-28 00:49:17
|
The problem could be on either end, but it might be easier to fix in Unicorn.php -- you might want to look at the part of the code that is outputting the call numbers and see if mb_detect_encoding or mb_convert_encoding can help you. - Demian ________________________________________ From: Karla Smith [sm...@wi...] Sent: Wednesday, February 27, 2013 4:35 PM To: Demian Katz Cc: vuf...@li... Subject: Re: Diacritics in call numbers Thanks..I need mroe details, please! Are you referring to the driver.pl script that resides on our ILS server, or the Unicorn.php driver? --Karla On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: > It probably means that your ILS driver is not returning the call numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or some other format and need to be converted before being passed to VuFind. (There were some problems like this in the Voyager driver that were resolved fairly recently -- probably between 1.3 and 1.4; I wouldn't be surprised to see similar things in other drivers). > > Let me know if you need more details! > > - Demian > >> -----Original Message----- >> From: Karla Smith [mailto:sm...@wi...] >> Sent: Wednesday, February 27, 2013 3:08 PM >> To: vuf...@li... >> Subject: [VuFind-Tech] Diacritics in call numbers >> >> Hi, >> I just got a report from staff that diacritics are not displaying properly in >> the call number on the holdings table. They display fine elsewhere--including >> the call number found in the 999 field where all the other holdings info is. >> >> Here's an example: >> http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=AllFields& >> submit=Find >> >> Any suggestions how to fix this? I am on v1.3. >> >> Thanks, >> --Karla >> Karla Smith, ILS Manager >> Winnefox Library System >> Oshkosh, WI 54901 >> sm...@wi... >> >> >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_feb >> _______________________________________________ >> Vufind-tech mailing list >> Vuf...@li... >> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > Karla Smith, ILS Manager Winnefox Library System Oshkosh, WI 54901 sm...@wi... |
From: Tuan N. <tu...@yo...> - 2013-02-28 15:23:22
|
Karla, As Demian suggested, you can look in Unicorn.php at the end of the querySirsi and change it to the following to see if it works. // get the response data $response = $httpClient->getResponseBody(); if(mb_detect_encoding($response) != "UTF-8") { $response = utf8_encode($response); } return rtrim($response); On 2013-02-27, at 7:47 PM, Demian Katz wrote: > The problem could be on either end, but it might be easier to fix in Unicorn.php -- you might want to look at the part of the code that is outputting the call numbers and see if mb_detect_encoding or mb_convert_encoding can help you. > > - Demian > ________________________________________ > From: Karla Smith [sm...@wi...] > Sent: Wednesday, February 27, 2013 4:35 PM > To: Demian Katz > Cc: vuf...@li... > Subject: Re: Diacritics in call numbers > > Thanks..I need mroe details, please! > > Are you referring to the driver.pl script that resides on our ILS server, or the Unicorn.php driver? > > --Karla > > On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: > >> It probably means that your ILS driver is not returning the call numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or some other format and need to be converted before being passed to VuFind. (There were some problems like this in the Voyager driver that were resolved fairly recently -- probably between 1.3 and 1.4; I wouldn't be surprised to see similar things in other drivers). >> >> Let me know if you need more details! >> >> - Demian >> >>> -----Original Message----- >>> From: Karla Smith [mailto:sm...@wi...] >>> Sent: Wednesday, February 27, 2013 3:08 PM >>> To: vuf...@li... >>> Subject: [VuFind-Tech] Diacritics in call numbers >>> >>> Hi, >>> I just got a report from staff that diacritics are not displaying properly in >>> the call number on the holdings table. They display fine elsewhere--including >>> the call number found in the 999 field where all the other holdings info is. >>> >>> Here's an example: >>> http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=AllFields& >>> submit=Find >>> >>> Any suggestions how to fix this? I am on v1.3. >>> >>> Thanks, >>> --Karla >>> Karla Smith, ILS Manager >>> Winnefox Library System >>> Oshkosh, WI 54901 >>> sm...@wi... >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Everyone hates slow websites. So do we. >>> Make your web apps faster with AppDynamics >>> Download AppDynamics Lite for free today: >>> http://p.sf.net/sfu/appdyn_d2d_feb >>> _______________________________________________ >>> Vufind-tech mailing list >>> Vuf...@li... >>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >> >> >> > > Karla Smith, ILS Manager > Winnefox Library System > Oshkosh, WI 54901 > sm...@wi... > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: Tuan N. <tu...@yo...> - 2013-02-28 18:34:22
|
Karla, how about running the sel command on the command line to see if the diacritics show up? Sent from my iPhone On 2013-02-28, at 12:31 PM, Karla Smith <sm...@wi...> wrote: > Thanks Demian, Tuan, > > I tried Tuan's suggestion below, but it didn't make any difference--apparently utf_encode only encodes an ISO-8859-1 string to UTF-8 > > According to mb_detect_encoding, the encoding of $response is ASCII. > > So then I tried > $response = mb_convert_encoding($response, 'ASCII', 'UTF-8'); > > I would have expected that to work, but it didn't. > > Any other ideas? > > Since everything else is displaying properly, we might just decide to live with it. > --Karla > > On Feb 28, 2013, at 8:57 AM, Tuan Nguyen wrote: > >> Karla, >> >> As Demian suggested, you can look in Unicorn.php at the end of the querySirsi and change it to the following to see if it works. >> >> >> // get the response data >> $response = $httpClient->getResponseBody(); >> if(mb_detect_encoding($response) != "UTF-8") { >> $response = utf8_encode($response); >> } >> return rtrim($response); >> >> >> On 2013-02-27, at 7:47 PM, Demian Katz wrote: >> >>> The problem could be on either end, but it might be easier to fix in Unicorn.php -- you might want to look at the part of the code that is outputting the call numbers and see if mb_detect_encoding or mb_convert_encoding can help you. >>> >>> - Demian >>> ________________________________________ >>> From: Karla Smith [sm...@wi...] >>> Sent: Wednesday, February 27, 2013 4:35 PM >>> To: Demian Katz >>> Cc: vuf...@li... >>> Subject: Re: Diacritics in call numbers >>> >>> Thanks..I need mroe details, please! >>> >>> Are you referring to the driver.pl script that resides on our ILS server, or the Unicorn.php driver? >>> >>> --Karla >>> >>> On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: >>> >>>> It probably means that your ILS driver is not returning the call numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or some other format and need to be converted before being passed to VuFind. (There were some problems like this in the Voyager driver that were resolved fairly recently -- probably between 1.3 and 1.4; I wouldn't be surprised to see similar things in other drivers). >>>> >>>> Let me know if you need more details! >>>> >>>> - Demian >>>> >>>>> -----Original Message----- >>>>> From: Karla Smith [mailto:sm...@wi...] >>>>> Sent: Wednesday, February 27, 2013 3:08 PM >>>>> To: vuf...@li... >>>>> Subject: [VuFind-Tech] Diacritics in call numbers >>>>> >>>>> Hi, >>>>> I just got a report from staff that diacritics are not displaying properly in >>>>> the call number on the holdings table. They display fine elsewhere--including >>>>> the call number found in the 999 field where all the other holdings info is. >>>>> >>>>> Here's an example: >>>>> http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=AllFields& >>>>> submit=Find >>>>> >>>>> Any suggestions how to fix this? I am on v1.3. >>>>> >>>>> Thanks, >>>>> --Karla >>>>> Karla Smith, ILS Manager >>>>> Winnefox Library System >>>>> Oshkosh, WI 54901 >>>>> sm...@wi... >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Everyone hates slow websites. So do we. >>>>> Make your web apps faster with AppDynamics >>>>> Download AppDynamics Lite for free today: >>>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>>> _______________________________________________ >>>>> Vufind-tech mailing list >>>>> Vuf...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>>> >>>> >>>> >>> >>> Karla Smith, ILS Manager >>> Winnefox Library System >>> Oshkosh, WI 54901 >>> sm...@wi... >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Everyone hates slow websites. So do we. >>> Make your web apps faster with AppDynamics >>> Download AppDynamics Lite for free today: >>> http://p.sf.net/sfu/appdyn_d2d_feb >>> _______________________________________________ >>> Vufind-tech mailing list >>> Vuf...@li... >>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >> >> >> >> > > Karla Smith, ILS Manager > Winnefox Library System > Oshkosh, WI 54901 > sm...@wi... > > > > |
From: Karla S. <sm...@wi...> - 2013-02-28 18:37:05
|
Thanks Demian, Tuan, I tried Tuan's suggestion below, but it didn't make any difference--apparently utf_encode only encodes an ISO-8859-1 string to UTF-8 According to mb_detect_encoding, the encoding of $response is ASCII. So then I tried $response = mb_convert_encoding($response, 'ASCII', 'UTF-8'); I would have expected that to work, but it didn't. Any other ideas? Since everything else is displaying properly, we might just decide to live with it. --Karla On Feb 28, 2013, at 8:57 AM, Tuan Nguyen wrote: > Karla, > > As Demian suggested, you can look in Unicorn.php at the end of the querySirsi and change it to the following to see if it works. > > > // get the response data > $response = $httpClient->getResponseBody(); > if(mb_detect_encoding($response) != "UTF-8") { > $response = utf8_encode($response); > } > return rtrim($response); > > > On 2013-02-27, at 7:47 PM, Demian Katz wrote: > >> The problem could be on either end, but it might be easier to fix in Unicorn.php -- you might want to look at the part of the code that is outputting the call numbers and see if mb_detect_encoding or mb_convert_encoding can help you. >> >> - Demian >> ________________________________________ >> From: Karla Smith [sm...@wi...] >> Sent: Wednesday, February 27, 2013 4:35 PM >> To: Demian Katz >> Cc: vuf...@li... >> Subject: Re: Diacritics in call numbers >> >> Thanks..I need mroe details, please! >> >> Are you referring to the driver.pl script that resides on our ILS server, or the Unicorn.php driver? >> >> --Karla >> >> On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: >> >>> It probably means that your ILS driver is not returning the call numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or some other format and need to be converted before being passed to VuFind. (There were some problems like this in the Voyager driver that were resolved fairly recently -- probably between 1.3 and 1.4; I wouldn't be surprised to see similar things in other drivers). >>> >>> Let me know if you need more details! >>> >>> - Demian >>> >>>> -----Original Message----- >>>> From: Karla Smith [mailto:sm...@wi...] >>>> Sent: Wednesday, February 27, 2013 3:08 PM >>>> To: vuf...@li... >>>> Subject: [VuFind-Tech] Diacritics in call numbers >>>> >>>> Hi, >>>> I just got a report from staff that diacritics are not displaying properly in >>>> the call number on the holdings table. They display fine elsewhere--including >>>> the call number found in the 999 field where all the other holdings info is. >>>> >>>> Here's an example: >>>> http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=AllFields& >>>> submit=Find >>>> >>>> Any suggestions how to fix this? I am on v1.3. >>>> >>>> Thanks, >>>> --Karla >>>> Karla Smith, ILS Manager >>>> Winnefox Library System >>>> Oshkosh, WI 54901 >>>> sm...@wi... >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Everyone hates slow websites. So do we. >>>> Make your web apps faster with AppDynamics >>>> Download AppDynamics Lite for free today: >>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>> _______________________________________________ >>>> Vufind-tech mailing list >>>> Vuf...@li... >>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>> >>> >>> >> >> Karla Smith, ILS Manager >> Winnefox Library System >> Oshkosh, WI 54901 >> sm...@wi... >> >> >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_feb >> _______________________________________________ >> Vufind-tech mailing list >> Vuf...@li... >> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > Karla Smith, ILS Manager Winnefox Library System Oshkosh, WI 54901 sm...@wi... |
From: Demian K. <dem...@vi...> - 2013-02-28 18:30:00
|
The problem with mb_detect_encoding is that depending on your mb_detect_order settings, it may or may not actually give you meaningful information. Another possible approach to figuring out the encoding would be trial and error -- have you tried changing your browser encoding while a bad call number is on screen to see if you can find one that causes it to render correctly? - Demian ________________________________________ From: Karla Smith [sm...@wi...] Sent: Thursday, February 28, 2013 12:31 PM To: Tuan Nguyen Cc: Demian Katz; vuf...@li... Subject: Re: [VuFind-Tech] Diacritics in call numbers Thanks Demian, Tuan, I tried Tuan's suggestion below, but it didn't make any difference--apparently utf_encode only encodes an ISO-8859-1 string to UTF-8 According to mb_detect_encoding, the encoding of $response is ASCII. So then I tried $response = mb_convert_encoding($response, 'ASCII', 'UTF-8'); I would have expected that to work, but it didn't. Any other ideas? Since everything else is displaying properly, we might just decide to live with it. --Karla On Feb 28, 2013, at 8:57 AM, Tuan Nguyen wrote: > Karla, > > As Demian suggested, you can look in Unicorn.php at the end of the querySirsi and change it to the following to see if it works. > > > // get the response data > $response = $httpClient->getResponseBody(); > if(mb_detect_encoding($response) != "UTF-8") { > $response = utf8_encode($response); > } > return rtrim($response); > > > On 2013-02-27, at 7:47 PM, Demian Katz wrote: > >> The problem could be on either end, but it might be easier to fix in Unicorn.php -- you might want to look at the part of the code that is outputting the call numbers and see if mb_detect_encoding or mb_convert_encoding can help you. >> >> - Demian >> ________________________________________ >> From: Karla Smith [sm...@wi...] >> Sent: Wednesday, February 27, 2013 4:35 PM >> To: Demian Katz >> Cc: vuf...@li... >> Subject: Re: Diacritics in call numbers >> >> Thanks..I need mroe details, please! >> >> Are you referring to the driver.pl script that resides on our ILS server, or the Unicorn.php driver? >> >> --Karla >> >> On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: >> >>> It probably means that your ILS driver is not returning the call numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or some other format and need to be converted before being passed to VuFind. (There were some problems like this in the Voyager driver that were resolved fairly recently -- probably between 1.3 and 1.4; I wouldn't be surprised to see similar things in other drivers). >>> >>> Let me know if you need more details! >>> >>> - Demian >>> >>>> -----Original Message----- >>>> From: Karla Smith [mailto:sm...@wi...] >>>> Sent: Wednesday, February 27, 2013 3:08 PM >>>> To: vuf...@li... >>>> Subject: [VuFind-Tech] Diacritics in call numbers >>>> >>>> Hi, >>>> I just got a report from staff that diacritics are not displaying properly in >>>> the call number on the holdings table. They display fine elsewhere--including >>>> the call number found in the 999 field where all the other holdings info is. >>>> >>>> Here's an example: >>>> http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=AllFields& >>>> submit=Find >>>> >>>> Any suggestions how to fix this? I am on v1.3. >>>> >>>> Thanks, >>>> --Karla >>>> Karla Smith, ILS Manager >>>> Winnefox Library System >>>> Oshkosh, WI 54901 >>>> sm...@wi... >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Everyone hates slow websites. So do we. >>>> Make your web apps faster with AppDynamics >>>> Download AppDynamics Lite for free today: >>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>> _______________________________________________ >>>> Vufind-tech mailing list >>>> Vuf...@li... >>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>> >>> >>> >> >> Karla Smith, ILS Manager >> Winnefox Library System >> Oshkosh, WI 54901 >> sm...@wi... >> >> >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_feb >> _______________________________________________ >> Vufind-tech mailing list >> Vuf...@li... >> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > Karla Smith, ILS Manager Winnefox Library System Oshkosh, WI 54901 sm...@wi... |
From: David M. <ma...@ha...> - 2013-03-01 20:15:57
|
At Thu, 28 Feb 2013 17:31:27 +0000, Karla Smith wrote: > > Thanks Demian, Tuan, > > I tried Tuan's suggestion below, but it didn't make any difference--apparently utf_encode only encodes an ISO-8859-1 string to UTF-8 > > According to mb_detect_encoding, the encoding of $response is ASCII. > > So then I tried > $response = mb_convert_encoding($response, 'ASCII', 'UTF-8'); > > I would have expected that to work, but it didn't. > This conversion won't do anything useful: ASCII is a subset of Unicode every valid ASCII character is also a valid UTF-8 encoded unicode character. > > Any other ideas? > What exactly does: Callnumbers are not displayed *properly* mean? What I can see is that the callnumber is `Obreht, Tea' while the name of the author is `Obreht, Téa'. In the case diacritics are not displayed at all. This does not look like an problem with character encoding -- maybe the ILS does not return the callnumber w/ diacritics in the first place? What *does* the ILS return? Best, -- David > Since everything else is displaying properly, we might just decide to live with it. > --Karla > > On Feb 28, 2013, at 8:57 AM, Tuan Nguyen wrote: > > > Karla, > > > > As Demian suggested, you can look in Unicorn.php at the end of the querySirsi and change it to the following to see if it works. > > > > > > // get the response data > > $response = $httpClient->getResponseBody(); > > if(mb_detect_encoding($response) != "UTF-8") { > > $response = utf8_encode($response); > > } > > return rtrim($response); > > > > > > On 2013-02-27, at 7:47 PM, Demian Katz wrote: > > > >> The problem could be on either end, but it might be easier to fix in Unicorn.php -- you might want to look at the part of the code that is outputting the call numbers and see if mb_detect_encoding or mb_convert_encoding can help you. > >> > >> - Demian > >> ________________________________________ > >> From: Karla Smith [sm...@wi...] > >> Sent: Wednesday, February 27, 2013 4:35 PM > >> To: Demian Katz > >> Cc: vuf...@li... > >> Subject: Re: Diacritics in call numbers > >> > >> Thanks..I need mroe details, please! > >> > >> Are you referring to the driver.pl script that resides on our ILS server, or the Unicorn.php driver? > >> > >> --Karla > >> > >> On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: > >> > >>> It probably means that your ILS driver is not returning the call numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or some other format and need to be converted before being passed to VuFind. (There were some problems like this in the Voyager driver that were resolved fairly recently -- probably between 1.3 and 1.4; I wouldn't be surprised to see similar things in other drivers). > >>> > >>> Let me know if you need more details! > >>> > >>> - Demian > >>> > >>>> -----Original Message----- > >>>> From: Karla Smith [mailto:sm...@wi...] > >>>> Sent: Wednesday, February 27, 2013 3:08 PM > >>>> To: vuf...@li... > >>>> Subject: [VuFind-Tech] Diacritics in call numbers > >>>> > >>>> Hi, > >>>> I just got a report from staff that diacritics are not displaying properly in > >>>> the call number on the holdings table. They display fine elsewhere--including > >>>> the call number found in the 999 field where all the other holdings info is. > >>>> > >>>> Here's an example: > >>>> http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=AllFields& > >>>> submit=Find > >>>> > >>>> Any suggestions how to fix this? I am on v1.3. > >>>> > >>>> Thanks, > >>>> --Karla > >>>> Karla Smith, ILS Manager > >>>> Winnefox Library System > >>>> Oshkosh, WI 54901 > >>>> sm...@wi... > >>>> > >>>> > >>>> > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> Everyone hates slow websites. So do we. > >>>> Make your web apps faster with AppDynamics > >>>> Download AppDynamics Lite for free today: > >>>> http://p.sf.net/sfu/appdyn_d2d_feb > >>>> _______________________________________________ > >>>> Vufind-tech mailing list > >>>> Vuf...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech > >>> > >>> > >>> > >> > >> Karla Smith, ILS Manager > >> Winnefox Library System > >> Oshkosh, WI 54901 > >> sm...@wi... > >> > >> > >> > >> > >> ------------------------------------------------------------------------------ > >> Everyone hates slow websites. So do we. > >> Make your web apps faster with AppDynamics > >> Download AppDynamics Lite for free today: > >> http://p.sf.net/sfu/appdyn_d2d_feb > >> _______________________________________________ > >> Vufind-tech mailing list > >> Vuf...@li... > >> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > > > > > > > Karla Smith, ILS Manager > Winnefox Library System > Oshkosh, WI 54901 > sm...@wi... > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: Karla S. <sm...@wi...> - 2013-03-01 19:20:50
|
Tuan, Running the API selcallnum command on the Symphony server gives me "Obreht, Tâea", or sometimes "Obreht, T?ea" depending which computer I'm using. The first result is weird, because it is outputting a diacritic mark--just the wrong one. It should be "Obreht, Téa". VuFind displays "Obreht, Taea" regardless what computer I'm on. Demian, Playing with the char encoding in my browser, oddly enough, doesn't change the call number display. It DOES change the display in the bib record display. It is as if VuFind can't fix the encoding because it doesn't recognize what charset Symphony is sending. Some of our libraries just leave the diacritics off when entering the call number, which might be the best solution. However, our biggest libraries just copy the author from the bib record into the copy's call number, which is how we spotted the problem in the first place. I wonder if the fact that they are copy-n-pasting the rendered text instead of using the character map to insert the accented character could make a difference? --Karla > -----Original Message----- > From: Tuan Nguyen [mailto:tu...@yo...] > Sent: Thursday, February 28, 2013 11:43 AM > To: Karla Smith > Cc: Demian Katz; vuf...@li... > Subject: Re: [VuFind-Tech] Diacritics in call numbers > > Karla, how about running the sel command on the command line to see if > the diacritics show up? > > Sent from my iPhone > > On 2013-02-28, at 12:31 PM, Karla Smith <sm...@wi...> wrote: > >> Thanks Demian, Tuan, >> >> I tried Tuan's suggestion below, but it didn't make any difference-- > apparently utf_encode only encodes an ISO-8859-1 string to UTF-8 >> >> According to mb_detect_encoding, the encoding of $response is ASCII. >> >> So then I tried >> $response = mb_convert_encoding($response, 'ASCII', 'UTF-8'); >> >> I would have expected that to work, but it didn't. >> >> Any other ideas? >> >> Since everything else is displaying properly, we might just decide to > live with it. >> --Karla >> >> On Feb 28, 2013, at 8:57 AM, Tuan Nguyen wrote: >> >>> Karla, >>> >>> As Demian suggested, you can look in Unicorn.php at the end of the > querySirsi and change it to the following to see if it works. >>> >>> >>> // get the response data >>> $response = $httpClient->getResponseBody(); >>> if(mb_detect_encoding($response) != "UTF-8") { >>> $response = utf8_encode($response); >>> } >>> return rtrim($response); >>> >>> >>> On 2013-02-27, at 7:47 PM, Demian Katz wrote: >>> >>>> The problem could be on either end, but it might be easier to fix > in Unicorn.php -- you might want to look at the part of the code that > is outputting the call numbers and see if mb_detect_encoding or > mb_convert_encoding can help you. >>>> >>>> - Demian >>>> ________________________________________ >>>> From: Karla Smith [sm...@wi...] >>>> Sent: Wednesday, February 27, 2013 4:35 PM >>>> To: Demian Katz >>>> Cc: vuf...@li... >>>> Subject: Re: Diacritics in call numbers >>>> >>>> Thanks..I need mroe details, please! >>>> >>>> Are you referring to the driver.pl script that resides on our ILS > server, or the Unicorn.php driver? >>>> >>>> --Karla >>>> >>>> On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: >>>> >>>>> It probably means that your ILS driver is not returning the call > numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or > some other format and need to be converted before being passed to > VuFind. (There were some problems like this in the Voyager driver that > were resolved fairly recently -- probably between 1.3 and 1.4; I > wouldn't be surprised to see similar things in other drivers). >>>>> >>>>> Let me know if you need more details! >>>>> >>>>> - Demian >>>>> >>>>>> -----Original Message----- >>>>>> From: Karla Smith [mailto:sm...@wi...] >>>>>> Sent: Wednesday, February 27, 2013 3:08 PM >>>>>> To: vuf...@li... >>>>>> Subject: [VuFind-Tech] Diacritics in call numbers >>>>>> >>>>>> Hi, >>>>>> I just got a report from staff that diacritics are not displaying > properly in >>>>>> the call number on the holdings table. They display fine > elsewhere--including >>>>>> the call number found in the 999 field where all the other > holdings info is. >>>>>> >>>>>> Here's an example: >>>>>> > http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=All > Fields& >>>>>> submit=Find >>>>>> >>>>>> Any suggestions how to fix this? I am on v1.3. >>>>>> >>>>>> Thanks, >>>>>> --Karla >>>>>> Karla Smith, ILS Manager >>>>>> Winnefox Library System >>>>>> Oshkosh, WI 54901 >>>>>> sm...@wi... >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ----------------------------------------------------------------- > ------------- >>>>>> Everyone hates slow websites. So do we. >>>>>> Make your web apps faster with AppDynamics >>>>>> Download AppDynamics Lite for free today: >>>>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>>>> _______________________________________________ >>>>>> Vufind-tech mailing list >>>>>> Vuf...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>>>> >>>>> >>>>> >>>> >>>> Karla Smith, ILS Manager >>>> Winnefox Library System >>>> Oshkosh, WI 54901 >>>> sm...@wi... >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------- > ----------- >>>> Everyone hates slow websites. So do we. >>>> Make your web apps faster with AppDynamics >>>> Download AppDynamics Lite for free today: >>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>> _______________________________________________ >>>> Vufind-tech mailing list >>>> Vuf...@li... >>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>> >>> >>> >>> >> >> Karla Smith, ILS Manager >> Winnefox Library System >> Oshkosh, WI 54901 >> sm...@wi... >> >> >> >> > > |
From: Demian K. <dem...@vi...> - 2013-03-01 19:59:16
|
I wonder if there are multiple layers of problems going on here. It's strange that you're getting inconsistent results from the lower-level API... and if VuFind is garbling things consistently, perhaps there is some combination of an API problem and character encoding mistranslation in the VuFind driver. These things tend to be annoying to fix! And if you add the possibility of people copying-and-pasting different character encodings into a single database, it gets really ugly. Do the call numbers display correctly anywhere? That might be the first place to start -- see if there's anything that is doing this right, and then try to figure out how to get everybody else in line with that. If everything is wrong everywhere, then there may just be a data cleanup issue that needs to be addressed first. - Demian ________________________________________ From: Karla Smith [sm...@wi...] Sent: Friday, March 01, 2013 11:26 AM To: vuf...@li... Subject: Re: [VuFind-Tech] Diacritics in call numbers Tuan, Running the API selcallnum command on the Symphony server gives me "Obreht, Tâea", or sometimes "Obreht, T?ea" depending which computer I'm using. The first result is weird, because it is outputting a diacritic mark--just the wrong one. It should be "Obreht, Téa". VuFind displays "Obreht, Taea" regardless what computer I'm on. Demian, Playing with the char encoding in my browser, oddly enough, doesn't change the call number display. It DOES change the display in the bib record display. It is as if VuFind can't fix the encoding because it doesn't recognize what charset Symphony is sending. Some of our libraries just leave the diacritics off when entering the call number, which might be the best solution. However, our biggest libraries just copy the author from the bib record into the copy's call number, which is how we spotted the problem in the first place. I wonder if the fact that they are copy-n-pasting the rendered text instead of using the character map to insert the accented character could make a difference? --Karla > -----Original Message----- > From: Tuan Nguyen [mailto:tu...@yo...] > Sent: Thursday, February 28, 2013 11:43 AM > To: Karla Smith > Cc: Demian Katz; vuf...@li... > Subject: Re: [VuFind-Tech] Diacritics in call numbers > > Karla, how about running the sel command on the command line to see if > the diacritics show up? > > Sent from my iPhone > > On 2013-02-28, at 12:31 PM, Karla Smith <sm...@wi...> wrote: > >> Thanks Demian, Tuan, >> >> I tried Tuan's suggestion below, but it didn't make any difference-- > apparently utf_encode only encodes an ISO-8859-1 string to UTF-8 >> >> According to mb_detect_encoding, the encoding of $response is ASCII. >> >> So then I tried >> $response = mb_convert_encoding($response, 'ASCII', 'UTF-8'); >> >> I would have expected that to work, but it didn't. >> >> Any other ideas? >> >> Since everything else is displaying properly, we might just decide to > live with it. >> --Karla >> >> On Feb 28, 2013, at 8:57 AM, Tuan Nguyen wrote: >> >>> Karla, >>> >>> As Demian suggested, you can look in Unicorn.php at the end of the > querySirsi and change it to the following to see if it works. >>> >>> >>> // get the response data >>> $response = $httpClient->getResponseBody(); >>> if(mb_detect_encoding($response) != "UTF-8") { >>> $response = utf8_encode($response); >>> } >>> return rtrim($response); >>> >>> >>> On 2013-02-27, at 7:47 PM, Demian Katz wrote: >>> >>>> The problem could be on either end, but it might be easier to fix > in Unicorn.php -- you might want to look at the part of the code that > is outputting the call numbers and see if mb_detect_encoding or > mb_convert_encoding can help you. >>>> >>>> - Demian >>>> ________________________________________ >>>> From: Karla Smith [sm...@wi...] >>>> Sent: Wednesday, February 27, 2013 4:35 PM >>>> To: Demian Katz >>>> Cc: vuf...@li... >>>> Subject: Re: Diacritics in call numbers >>>> >>>> Thanks..I need mroe details, please! >>>> >>>> Are you referring to the driver.pl script that resides on our ILS > server, or the Unicorn.php driver? >>>> >>>> --Karla >>>> >>>> On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: >>>> >>>>> It probably means that your ILS driver is not returning the call > numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or > some other format and need to be converted before being passed to > VuFind. (There were some problems like this in the Voyager driver that > were resolved fairly recently -- probably between 1.3 and 1.4; I > wouldn't be surprised to see similar things in other drivers). >>>>> >>>>> Let me know if you need more details! >>>>> >>>>> - Demian >>>>> >>>>>> -----Original Message----- >>>>>> From: Karla Smith [mailto:sm...@wi...] >>>>>> Sent: Wednesday, February 27, 2013 3:08 PM >>>>>> To: vuf...@li... >>>>>> Subject: [VuFind-Tech] Diacritics in call numbers >>>>>> >>>>>> Hi, >>>>>> I just got a report from staff that diacritics are not displaying > properly in >>>>>> the call number on the holdings table. They display fine > elsewhere--including >>>>>> the call number found in the 999 field where all the other > holdings info is. >>>>>> >>>>>> Here's an example: >>>>>> > http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=All > Fields& >>>>>> submit=Find >>>>>> >>>>>> Any suggestions how to fix this? I am on v1.3. >>>>>> >>>>>> Thanks, >>>>>> --Karla >>>>>> Karla Smith, ILS Manager >>>>>> Winnefox Library System >>>>>> Oshkosh, WI 54901 >>>>>> sm...@wi... >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ----------------------------------------------------------------- > ------------- >>>>>> Everyone hates slow websites. So do we. >>>>>> Make your web apps faster with AppDynamics >>>>>> Download AppDynamics Lite for free today: >>>>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>>>> _______________________________________________ >>>>>> Vufind-tech mailing list >>>>>> Vuf...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>>>> >>>>> >>>>> >>>> >>>> Karla Smith, ILS Manager >>>> Winnefox Library System >>>> Oshkosh, WI 54901 >>>> sm...@wi... >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------- > ----------- >>>> Everyone hates slow websites. So do we. >>>> Make your web apps faster with AppDynamics >>>> Download AppDynamics Lite for free today: >>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>> _______________________________________________ >>>> Vufind-tech mailing list >>>> Vuf...@li... >>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>> >>> >>> >>> >> >> Karla Smith, ILS Manager >> Winnefox Library System >> Oshkosh, WI 54901 >> sm...@wi... >> >> >> >> > > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Vufind-tech mailing list Vuf...@li... https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: Tuan N. <tu...@yo...> - 2013-03-01 20:12:12
|
Karla, Check the NLS_LANG line in /s/sirsi/Unicorn/Config/environ it is likely set to NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 if that is what you have then try to do export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 export LANG=en_US.ISO8859-1 then run the sel command again to see if that displays correctly On 2013-03-01, at 11:26 AM, Karla Smith wrote: > Tuan, > Running the API selcallnum command on the Symphony server gives me "Obreht, Tâea", or sometimes "Obreht, T?ea" depending which computer I'm using. The first result is weird, because it is outputting a diacritic mark--just the wrong one. It should be "Obreht, Téa". VuFind displays "Obreht, Taea" regardless what computer I'm on. > > Demian, > Playing with the char encoding in my browser, oddly enough, doesn't change the call number display. It DOES change the display in the bib record display. > > It is as if VuFind can't fix the encoding because it doesn't recognize what charset Symphony is sending. > > Some of our libraries just leave the diacritics off when entering the call number, which might be the best solution. However, our biggest libraries just copy the author from the bib record into the copy's call number, which is how we spotted the problem in the first place. I wonder if the fact that they are copy-n-pasting the rendered text instead of using the character map to insert the accented character could make a difference? > > --Karla > > > > >> -----Original Message----- >> From: Tuan Nguyen [mailto:tu...@yo...] >> Sent: Thursday, February 28, 2013 11:43 AM >> To: Karla Smith >> Cc: Demian Katz; vuf...@li... >> Subject: Re: [VuFind-Tech] Diacritics in call numbers >> >> Karla, how about running the sel command on the command line to see if >> the diacritics show up? >> >> Sent from my iPhone >> >> On 2013-02-28, at 12:31 PM, Karla Smith <sm...@wi...> wrote: >> >>> Thanks Demian, Tuan, >>> >>> I tried Tuan's suggestion below, but it didn't make any difference-- >> apparently utf_encode only encodes an ISO-8859-1 string to UTF-8 >>> >>> According to mb_detect_encoding, the encoding of $response is ASCII. >>> >>> So then I tried >>> $response = mb_convert_encoding($response, 'ASCII', 'UTF-8'); >>> >>> I would have expected that to work, but it didn't. >>> >>> Any other ideas? >>> >>> Since everything else is displaying properly, we might just decide to >> live with it. >>> --Karla >>> >>> On Feb 28, 2013, at 8:57 AM, Tuan Nguyen wrote: >>> >>>> Karla, >>>> >>>> As Demian suggested, you can look in Unicorn.php at the end of the >> querySirsi and change it to the following to see if it works. >>>> >>>> >>>> // get the response data >>>> $response = $httpClient->getResponseBody(); >>>> if(mb_detect_encoding($response) != "UTF-8") { >>>> $response = utf8_encode($response); >>>> } >>>> return rtrim($response); >>>> >>>> >>>> On 2013-02-27, at 7:47 PM, Demian Katz wrote: >>>> >>>>> The problem could be on either end, but it might be easier to fix >> in Unicorn.php -- you might want to look at the part of the code that >> is outputting the call numbers and see if mb_detect_encoding or >> mb_convert_encoding can help you. >>>>> >>>>> - Demian >>>>> ________________________________________ >>>>> From: Karla Smith [sm...@wi...] >>>>> Sent: Wednesday, February 27, 2013 4:35 PM >>>>> To: Demian Katz >>>>> Cc: vuf...@li... >>>>> Subject: Re: Diacritics in call numbers >>>>> >>>>> Thanks..I need mroe details, please! >>>>> >>>>> Are you referring to the driver.pl script that resides on our ILS >> server, or the Unicorn.php driver? >>>>> >>>>> --Karla >>>>> >>>>> On Feb 27, 2013, at 2:49 PM, Demian Katz wrote: >>>>> >>>>>> It probably means that your ILS driver is not returning the call >> numbers in UTF-8 format. Perhaps they are being stored in Latin-1 or >> some other format and need to be converted before being passed to >> VuFind. (There were some problems like this in the Voyager driver that >> were resolved fairly recently -- probably between 1.3 and 1.4; I >> wouldn't be surprised to see similar things in other drivers). >>>>>> >>>>>> Let me know if you need more details! >>>>>> >>>>>> - Demian >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Karla Smith [mailto:sm...@wi...] >>>>>>> Sent: Wednesday, February 27, 2013 3:08 PM >>>>>>> To: vuf...@li... >>>>>>> Subject: [VuFind-Tech] Diacritics in call numbers >>>>>>> >>>>>>> Hi, >>>>>>> I just got a report from staff that diacritics are not displaying >> properly in >>>>>>> the call number on the holdings table. They display fine >> elsewhere--including >>>>>>> the call number found in the 999 field where all the other >> holdings info is. >>>>>>> >>>>>>> Here's an example: >>>>>>> >> http://catalog.winnefox.org/Search/Results?lookfor=tigers+wife&type=All >> Fields& >>>>>>> submit=Find >>>>>>> >>>>>>> Any suggestions how to fix this? I am on v1.3. >>>>>>> >>>>>>> Thanks, >>>>>>> --Karla >>>>>>> Karla Smith, ILS Manager >>>>>>> Winnefox Library System >>>>>>> Oshkosh, WI 54901 >>>>>>> sm...@wi... >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ----------------------------------------------------------------- >> ------------- >>>>>>> Everyone hates slow websites. So do we. >>>>>>> Make your web apps faster with AppDynamics >>>>>>> Download AppDynamics Lite for free today: >>>>>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>>>>> _______________________________________________ >>>>>>> Vufind-tech mailing list >>>>>>> Vuf...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>>>>> >>>>>> >>>>>> >>>>> >>>>> Karla Smith, ILS Manager >>>>> Winnefox Library System >>>>> Oshkosh, WI 54901 >>>>> sm...@wi... >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------- >> ----------- >>>>> Everyone hates slow websites. So do we. >>>>> Make your web apps faster with AppDynamics >>>>> Download AppDynamics Lite for free today: >>>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>>> _______________________________________________ >>>>> Vufind-tech mailing list >>>>> Vuf...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>>> >>>> >>>> >>>> >>> >>> Karla Smith, ILS Manager >>> Winnefox Library System >>> Oshkosh, WI 54901 >>> sm...@wi... >>> >>> >>> >>> >> >> > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > |
From: David M. <ma...@ha...> - 2013-03-03 11:38:41
|
At Fri, 1 Mar 2013 16:26:16 +0000, Karla Smith wrote: > > Tuan, Running the API selcallnum command on the Symphony server > gives me "Obreht, Tâea", or sometimes "Obreht, T?ea" depending which > computer I'm using. "Obreht, T?ea" -- The computer does not known how to render the `â'. > The first result is weird, because it is outputting a diacritic > mark--just the wrong one. If the ILS gives `Obreht, Tâea' then we then call number is `Obreht, Tâea'. > > Some of our libraries just leave the diacritics off when entering > the call number, which might be the best solution. However, our > biggest libraries just copy the author from the bib record into the > copy's call number, which is how we spotted the problem in the first > place. I wonder if the fact that they are copy-n-pasting the > rendered text instead of using the character map to insert the > accented character could make a difference? Copy'n'pasting the rendered text has its dangers. Take for example http://catalog.winnefox.org/Record/945122/Details#tabnav 100 |a Obreht, Téa. The é is written as sequence of two characters LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT. These two letters are equivalent to the single letter LATIN SMALL LETTER E WITH ACUTE. I'm not sure if you see two characters, but believe me: They are there. The big question is: How does the application where you paste this string handle this? Maybe (!) the `â' is a side-effect of the application not handling these combined characters properly? Make an experiment! Best, -- David -- David Maus Herzog August Bibliothek - D-38299 Wolfenbuettel Phone: +49-5331-808-317 Email: ma...@ha... Digital Humanities Research Collaboration http://www.gcdh.de/en/projects/dh/ PGP Key 0x0CC2E093512F7385 Fingerprint 1AD2 EE67 224F 18C5 EA55 98AD 0CC2 E093 512F 7385 |