Hello !

I am searching for some guys who interested in translating my glossary component in an other language besides German. At the moment my files are in English or better in a language I think it is English . Any hint are welcome.

Thanks in advance

More information’s about the component: http://forum.joomla.org/index.php/topic,25281.0.html

Language file:

Have'nt tried the component but here is a french translation (in ISO-8559-1)

Another contribution without trying the component 
Here is a danish translation (in ISO-8559-1)

I've tried the component, here is the Hungarian translation.
Edit: attached the admin translation too.

Here is a croatian translation. 
Tested in component.

Admin part added.

Spanish (formal, without testing).

I tested the component and it works really great.
also the bots for the components are great.

here is the spanish translation for the admin.
tested in site.
thanks

atrevidoweb

Russian. Was cooked in couple minutes without testing 

Thanks for your support!

At the moment I have:

+ Frontend language files: danisch, french, german, germani, hrvatski, hungarian, russian, spanish, english
+ Backend language files: russian, spanish, hrvatski, hungarian, english
+ Help files: german, russian, english

lukewill,
I downloded version 1.0 both from the Forge and from your site. In none of them the spanish files where included. 

elmoch wrote:lukewill,
I downloded version 1.0 both from the Forge and from your site. In none of them the spanish files where included. 

@elmoch,

Lo siento mucho.

Please, download the file named rd_glossary_v1_0_1.zip there are the spanisch translation files included.

@lukewill
Thank you. I had already grabbed the files from this thread, but other people may have missed them. 

Other questions:

1.- The tooltips and texts hardcorded in the backend should be in a unique language file which would hold all the constants (both front-end and back-end ones) and ideally would be located int the /rd_glossary/language/ directory.

2.- In the back-end, a direct access to the Control Panel is needed, both in the standard admin pull-down menu, under RD Glossary, and also in the HTML layout of the component itself.

Otherwise, this is a good work! 

Here is the Greek translation.

By the way, I installed the com in Joomla 1.0.5 but

1) The Greek displayed as question marks (you do not support UTF?)
2) There was no way I could add term on the front end (no "create" link or anything.
3) When clicked on the edit icon link on front end there was an error "default category not set" (I could not find an option to set category).
4) No menu item was created although I checked the user menu in the config.

Do you have a demo somewhere?

elmoch wrote:Other questions:

1.- The tooltips and texts hardcorded in the backend should be in a unique language file which would hold all the constants (both front-end and back-end ones) and ideally would be located int the /rd_glossary/language/ directory.

I use the xml-files and the mosParameters Class for configuration, at the moment there is no good multilanguage Support for xml-files. In the version for 1.1 I will intergrate ml-support. Stay tuned

elmoch wrote:2.- In the back-end, a direct access to the Control Panel is needed, both in the standard admin pull-down menu, under RD Glossary, and also in the HTML layout of the component itself.

I don't understand your question. Which CP do you mean? You can access the GLOSSARY CP if you click on RD Glossary in the admin pull down menu.

translatum.gr wrote:Here is the Greek translation.

Thanks!

translatum.gr wrote:
By the way, I installed the com in Joomla 1.0.5 but

1) The Greek displayed as question marks (you do not support UTF?)

I haven't done anything special.

translatum.gr wrote:2) There was no way I could add term on the front end (no "create" link or anything.
3) When clicked on the edit icon link on front end there was an error "default category not set" (I could not find an option to set category).

If you disable the category chooser you have to set up a default category. Look at the menu item configuration.

translatum.gr wrote:4) No menu item was created although I checked the user menu in the config.

You have do to it.

translatum.gr wrote:Do you have a demo somewhere?

not yet

Hi lukewill,

Here are my replies

1) The Greek displayed as question marks (you do not support UTF?)
[/quote]
I haven't done anything special.

I changed the encoding in xml files to UTF but still did not work. I think you have to take UTF into account as from 1.1 UTF will be in the core of joomla.

translatum.gr wrote:2) There was no way I could add term on the front end (no "create" link or anything.
3) When clicked on the edit icon link on front end there was an error "default category not set" (I could not find an option to set category).

If you disable the category chooser you have to set up a default category. Look at the menu item configuration.

I can see no menu item configuration in the component. I can only see About, Administration, Category, Items. I could not see the selections of your image in any of these.

translatum.gr wrote:4) No menu item was created although I checked the user menu in the config.

You have do to it.

Yes, I created a component link. Still, no way to add terms from front end.

translatum.gr wrote:Hi lukewill,

Here are my replies

1) The Greek displayed as question marks (you do not support UTF?)

I haven't done anything special.

I changed the encoding in xml files to UTF but still did not work. I think you have to take UTF into account as from 1.1 UTF will be in the core of joomla.

Yes it will be, but what is now? Support 1.0.5 utf?

translatum.gr wrote:

translatum.gr wrote:2) There was no way I could add term on the front end (no "create" link or anything.
3) When clicked on the edit icon link on front end there was an error "default category not set" (I could not find an option to set category).

If you disable the category chooser you have to set up a default category. Look at the menu item configuration.

I can see no menu item configuration in the component. I can only see About, Administration, Category, Items. I could not see the selections of your image in any of these.

They are two configuration possibilities.

1) Component Configuration
2) Menu Item Configuration (Item in mainmenu e.g.)

translatum.gr wrote:

translatum.gr wrote:4) No menu item was created although I checked the user menu in the config.

You have do to it.

Yes, I created a component link. Still, no way to add terms from front end.

This is the item you could configure the menu item, choose it and look at the parameters tab.

Thanks for your reply.

I changed the encoding in xml files to UTF but still did not work. I think you have to take UTF into account as from 1.1 UTF will be in the core of joomla.

Yes it will be, but what is now? Support 1.0.5 utf?

Well, if you take into account that you are creating a glossary component, and that most components work fine as they are in unicode in 1.0.5 then it is all the more logical to support a glossary component for UTF which my its very nature deals with many languages and consequently cries for UTF - if you catch my drift. 

lukewill wrote:

elmoch wrote:Other questions:

1.- The tooltips and texts hardcorded in the backend should be in a unique language file which would hold all the constants (both front-end and back-end ones) and ideally would be located int the /rd_glossary/language/ directory.

I use the xml-files and the mosParameters Class for configuration, at the moment there is no good multilanguage Support for xml-files. In the version for 1.1 I will intergrate ml-support. Stay tuned ;)

Other components, like Bookmarks, put all their language constants on a single language file, so that once translated the whole interface (both front-end and back-end) is displayed in the same language. It works like that since the old $ambo times.  :)

lukewill wrote:

elmoch wrote:2.- In the back-end, a direct access to the Control Panel is needed, both in the standard admin pull-down menu, under RD Glossary, and also in the HTML layout of the component itself.

I don't understand your question. Which CP do you mean? You can access the GLOSSARY CP if you click on RD Glossary in the admin pull down menu.

When I enter Administrator > Components > RD Glossary, I only see four options in the drop-down menu:

• About
• Administration - Configuration of the glossary (autopublish, notify, etc...)
• Category (category manager)
• Items (to manage terms)

BUT, when I save changes to Administration, I get the so called Control Panel.
This has four clickable icons giving access to the 4 options present in the drop-down menu. (That's the Control Panel I was talking about)

I would like not to need to go back to Components > RD Glossary every time I want to use a different option. How to: Implement a tab row as other components do. 

elmoch wrote:

lukewill wrote:

elmoch wrote:Other questions:

1.- The tooltips and texts hardcorded in the backend should be in a unique language file which would hold all the constants (both front-end and back-end ones) and ideally would be located int the /rd_glossary/language/ directory.

I use the xml-files and the mosParameters Class for configuration, at the moment there is no good multilanguage Support for xml-files. In the version for 1.1 I will intergrate ml-support. Stay tuned ;)

Other components, like Bookmarks, put all their language constants on a single language file, so that once translated the whole interface (both front-end and back-end) is displayed in the same language. It works like that since the old $ambo times.  :)

In the old mambo times, many components have a self programmed configurationen interface. Since some versions the class mosParameter gives the developer the possibility to configure the component with simple xml-files. But there isn't a (simple) chance to make a full translation for the configuration screens. With 1.1 this drawback would be gone.

elmoch wrote:

lukewill wrote:

elmoch wrote:2.- In the back-end, a direct access to the Control Panel is needed, both in the standard admin pull-down menu, under RD Glossary, and also in the HTML layout of the component itself.

I don't understand your question. Which CP do you mean? You can access the GLOSSARY CP if you click on RD Glossary in the admin pull down menu.

When I enter Administrator > Components > RD Glossary, I only see four options in the drop-down menu:

• About
• Administration - Configuration of the glossary (autopublish, notify, etc...)
• Category (category manager)
• Items (to manage terms)

BUT, when I save changes to Administration, I get the so called Control Panel.
This has four clickable icons giving access to the 4 options present in the drop-down menu. (That's the Control Panel I was talking about)

I would like not to need to go back to Components > RD Glossary every time I want to use a different option. How to: Implement a tab row as other components do.  :)

There is a simple navigation concept. With a submit you get one level up, if it makes no sense to hold the level (e.g. config -> CP). Or you hold the level e.g. items (term); save, delete and so on.

Form the other site, if you in the components menu you could choose RD Glossary and you get the CP or you could choose items directly. I think this is simple and logical and I don't know what I could make more.

translatum.gr wrote:I changed the encoding in xml files to UTF but still did not work. I think you have to take UTF into account as from 1.1 UTF will be in the core of joomla.

I don't know, if I wrong, but I think the encodig tag in the xml file is only for the xml-file and not for the component.

translatum.gr wrote:

Yes it will be, but what is now? Support 1.0.5 utf?

Well, if you take into account that you are creating a glossary component, and that most components work fine as they are in unicode in 1.0.5 then it is all the more logical to support a glossary component for UTF which my its very nature deals with many languages and consequently cries for UTF - if you catch my drift. 

I full agree with you, a glossary component thats support utf were great. At the moment I have not idea what I have to do to make a compoente utf ready. I think the framework must do the most work. If anyone here they can support me it would be appreciated.