Dear Massoud thank you very much for your quick reply.

 

I understand. I also come to this conclusion, although based on this post 
<https://jira.duraspace.org/browse/DS-1134>  work has already been carried out 
in the core engine of DSpace, which I verified from a look in the database 
(i.e. the Community/collection names are stored as metadata in the 
metadatavalue and not in the community table as it was before).

 

However, I also could not find a way to “configure” the system to use (either 
via the Messages.properties file, or via another way) alternative translations 
for a community/collection name. I guess an update to the metadatavalue table 
with the “text_lang” column set to the corresponding locale for the same dspace 
object (e.g. the community name), but in different language would do the job(?).

 

Nevertheless, he solution you are proposing it is indeed a very clever one, 
easy to implement and I bump my head on the table, why on earth couldn’t I 
think of it for so long, but going to solutions such as changing the database 
schema, the core code, etc.

 

Thank you very much and I will surely implement it.

 

Best Regards,

 

-Fk

 

From: [email protected] 
[mailto:[email protected]] On Behalf Of ????? ???? ??????
Sent: Monday, May 6, 2019 12:40 PM
To: [email protected]
Cc: [email protected]
Subject: Re: [dspace-community] Localization of Community and Collection Names 
Dspace 6.3

 

Hello Filippos,





To my knowledge, DSpace is structured to support a single language user-defined 
policies only, including communities and collections names. This is the case 
for all DSpace versions, including unfortunately DSpace 7 as I was informed.





The work around such bilingually limited architecture is to use a separator 
between the two text, names and description of the communities, collections, 
groups, and any other element that is not part of the item record fields 
intended to be sorted or made for hybrid search.





Take a look to our implementation of the Arabic/ English DSpace with bilingual 
communities/ collections UX. 





http://repository.taibahu.edu.sa/en/

 

>From the language icon on top of the screen, Select العربية (to mean Arabic) 
>and you will see the names of communities and collections displayed in Arabic. 

 

This work needs writing a simple extra code to watch over these fields 
searching for the “|” character in the text to make sure that only the English 
part of the text is displayed while in English mode (RTL) and only the Arabic 
part if the text (expected to the to be the text to the left of the | 
separator) is displayed while in Arabic mode (RTL). 

 

I you find this helpful.

 

Thanks,

Massoud AlShareef

KnowledgeWare

 

Sent from my iPhone


On 6 May 2019, at 12:07 PM, [email protected] wrote:

Filippos

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-community.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/007501d504b8%24f0e3eb60%24d2abc220%24%40gr.
For more options, visit https://groups.google.com/d/optout.

Reply via email to