I'm trying to implement the multi language or bilingual content and i notice the follwoing:
create a content
change content language filter from user profile.
update content with the preferred language
Now, the content is bilingual or muli language this is the alfresco scenario, is there any other scenario for doing this ? is there any other way inline ? is there any other way using Alfresco API ?
Any help or guidance will be highly appreciated.
Thanks.
Mohammed amr
API wise, it depends slightly on what you're trying to do.
One option is to define properties to be Multilingual, and then set multiple values (one value per locale). See Multilingual Document Support on the Alfresco wiki for details of the modelling and use of this.
Alternately, you can have one node per language, and link them together as translations. This is provided by the Multilingual Content Service
If you want to mark something as a translation in the UI, then in Explorer go to the document details of a node. On the right hand side, hit "Make Multilingual", and then specify the language it's in. You can then add translations of it for the additional languages you want for it.
Related
I am building a website using Symfony. I am wondering how can I change the language of my website by pressing a button.
Say I have two links in the footer (English and German) and when I click any of them, the whole website and all future views I access will remember my choice of language.
There are numerous websites who have this facility and I am wondering how can I achieve this goal.
Thank you!
Recommend checking out the jms/i18n-routing-bundle. You can use buttons or links to change the locale (language) and once changed the site will remain on that language. Just a bit of advice, use the "prefix" strategy when you set it up so that your site's urls will always be domain.com/language/.....
You'll have to learn how to use the translation bundle and setup translation files as well as having to learn how to setup Twig for translations, using the translation in your services and forms, but once you get the hang of it, it is really easy but time consuming.
I need to present Word and PDF documents in a read-only preview, via an ASPX/HTML page to my internal users. In a related requirement, I need to present editable Word documents, via ab ASPX/HTML page, to parties outside of our network - effectively the public.
We cannot rely upon Word or Adobe-type PDF plugins being available on the destination PC.
Can anyone suggest a way to do this?
Edit - For clarity, the document/data would ideally stay on our own servers.
What about using Google Docs API? You could use either their word-like doc or a form to get the data you need, and then present that internally.
Not sure if this meets all of your requirements, or is an available option.
For our company, we have a few tools that utilize Google Docs. We upload data dynamically to them for specific needs.
Based on your requirements, maybe it's best to just write your own. I haven't created a Rich Text Editor. But it looks like there are quite a few tutorials online. Here is a basic tutorial for a rich text editor. It's using javascript, HTML, & CSS. If you prefer to not use js, then you may need to look for other tutorials.
This isn't the most glamorous solution, as it looks like the users view would be HTML. I'd think you could have it updating dynamically off to the side with an actual rich text view (similar to how Stack Overflow has theirs below an answer or question being written).
Update
Over the weekend I was exploring HTML5's contenteditable attribute, I came across an editor that builds off of that called Aloha Editor. It's a WYSIWYG type editor. But if that's something that you desire for your clients, than this would probably be a pretty simple integration. I have yet to use it, but it seems like it would be a great fit - if you decide to go the route of building your own editor.
You could use the Zoho API or, if you need to keep all data on your own servers and validated clients at all times, you could try the Aspose components.
If you're interested to provide documents in a view-only way then you can try GroupDocs as well: http://groupdocs.com/. They offer viewers for different file types which you can add to your website very easily: http://groupdocs.com/apps/viewer.
Since you need to keep data on your own server, aceoffix can be one of your alternative. It is a plugin installed on your own server and save all data on your server too.
I have to display product and its description in listview/gridview,like any other eComm application.User want's to set the layout and attribute of product which he want to show while displaying the product.
I am planing to use templates, and provide user to generate templates(XSLT) based on the templates,the layout and attribute would be displayed,however I have no idea weather it is possible or not.Please guide
Check out how www.ventrian.com does their modules - especially the NewsArticles system.
Instead of providing the users an XSLT file to edit to control the layout they have their own templating / token system. There are a lot of modules that use this strategy, XSLT is a little serious if you are expecting 'users' to manage them. Even a lot of people who use DNN to build websites for others professionally have trouble wrapping their head around XML transformations.
But the answer to your question is definitely yes - you can provide XSLT files that transform your XML since it all works just like ASP .NET. But, most the popular modules provide a way for the user to customize layout that is not as complex as this.
I want to have a group in Plone that can only translate for 1 specific language. Is this possible? And if yes, how?
Use case is that there are quite a bit of languages in a site, and that the translators can only translate for their language.
Not without very substantial customization. With some code added, you could make the translate drop-down actions smarter, so that they only offered particular languages to users from particular groups. That might give you what you need.
If you need security to match, it would be harder. You'd have to intervene (via code) after translation creation to set sharing.
So, possible yes. Practical, probably not.
If this is a very high priority project, and you have resources available, get in touch with the folks working on the next generation of LinguaPlone, and offer to help develop (or to fund development) for the feature. That might be the very best way to make it happen.
Actually — this doesn't have to be so hard.
By granting the translator add and edit permissions in the required language subfolder, and not in the other language subtrees, this should all simply work.
The only real need for customisation might be to hide the translate actions from the menu if the user doesn't have permissions to translate to there.
I'm trying to make a multilingual website in Drupal. My languages that I need are german, dutch, english and french. I've added the i18n module and added the languages.
I work with views to show my content on the website. For the moment I have one page that I want to translate in the 4 languages. I've created a view for each translation. Now I want to link my view to the correct node. Therefore I use a view field in my content node.
PROBLEM:
My problem lies in the url. The first time everything is fine.
my url: localhost/?q=nl/activiteiten
Now when I select english in my language bar the language changes but not the url. my url: localhost/?q=en/activiteiten
Here "activiteiten" must be "activities". How do I solve this?
I've searched a while for this problem on the drupal forums but I can't seem to find a good solution to this problem. The only thing I've found is working with a view field in the content node or with input_views in the body of your node. These two won't work for me.
i18 module with no need to create a view for each
language, you have to translate content using the i18, then
charge between changing the language.
You can have problems from the beginning did not use the module
all languages declared, you have to edit each
content and save it to associate it well.
Well, just reading your own answer I think you've taken a wrong turn somewhere (or you're trying to do something else and I didn't quite catch on).
To create multilingual views for pages (which is what I think you want to do) you would first create a page view (duh), specify what you want to be shown and define a path to it. Then you enable (if it's not enabled already) the URL-alias ("URL-aliassen") module and define aliases for each language (ie. FR : activites - I don't like accents in URLs :p - NL : activiteiten, DE : aktivitaten - if memory serves me right anyway, again with accents removed :p). These aliases will be used as the path from that moment on.
For an article describing this process refer to : Translating Views paths in Drupal.
BTW You could also use the Pathauto module to create these aliases based on the title of your nodes of course instead of defining them manually, you can even (re)create them in batch when you alter the settings.
Eventually I've solved my problem with a view field. I've made my view and in my node I've selected that view in the list. Then in the body you can type something for that language.