Default English Pack

[paulhh]

The default English pack is US English.  As much as possible, we will try and keep this the same as British and International English, to avoid unnecessary maintenance of language packs.

If there are any corrections or suggestions for improvements to the default language pack, please use this thread to raise and discuss them.

Cheers
Paul.

[lgr]

Hi,

A few typos in V1 files :
webclient :
action_mail=Semd email to

version-service :
version_service.err_unsupported=The current implmentation of the version service does not support the creation of branches.
version_service.err_restore_no_version=cannot be restore since there is no version information availble for this node.
version_service.err_revert_mismatch=The verion provided to revert to does not come from the nodes version history.

coci-service.properties :
coci_service.err_bad_copy=The original node can not be found.  Perhaps the copy has been corrupted or the origional has been deleted or moved.

And just another question :
what is the difference between node, content, document and item ?
Do we have to maintain four terms for more or less the same meaning ?

Laurent.

[kevinr]

Thanks for spotting those issues, i'll get the main code line and language pack updated.

And just another question :
what is the difference between node, content, document and item ?
Do we have to maintain four terms for more or less the same meaning ?

They do have different, if subtle meanings:
node = any single object in the system, including all system objects, the word node is really from the JSR-170 spec definition.
content = either a content node or the content of any node that supports a ContentData property
document=a node containing content which for the default model happens to be of type "cm:content" - so i understand the confusion there. But there may be many different types of document in the future, especially custom types.
item=a non-system object in the system, so a folder or document generally.

Kevin

[lgr]

Hmm, ok, thanks for these details.

In fact, my problem is to be able to translate all these terms in french. I was also wondering how i must translate them, as only basic users will read them, and i don't think that they will be aware of these differences.

If I, as a technical guy, can hardly understand the subtle differences between these terms, how could it be possible that a basic, non technical, user can understand them ?

My proposal should be to isolate all technical messages, that could contain some technical terms (of course, for debugging purposes, it is important to know that a node and not a document is not working properly). ANd we could use a more generic term for user oriented messages, like "content".

What is your onipion ?

Best regards,

Laurent.

[lgr]

Hi,

Small typo in v1.1 :
compare_property_value_evaluator.no_content_property=A content proerty must be…

Laurent.

[lgr]

Hello,

Some messages are found twice in the v1.1 language files extracted from alfresco.war from the tomcat linux tarball (also in v1 language zip file) :

application-model.properties
      2 app_applicationmodel.aspect.app_inlineeditable.description
      2 app_applicationmodel.aspect.app_inlineeditable.title
webclient.properties
      2 actions
      2 advanced_search
      2 all_spaces
      2 approve_flow
      2 author
      2 choose_space_icon
      2 click_add
      2 click_upload
      2 copy
      2 delete_category
      2 description
      2 items
      2 local
      2 location
      2 reject_flow
      2 subject
      2 system_info
      2 title
      2 view
      2 view_details

No message is found more that twice.

Laurent.

[lgr]

Hi,

Is it possible that you rename the default language pack included in the common Alfresco distribution, adding "en_EN", so that multilanguage works well when we add some other language ?

As far as i know, it won't disturb a mono-language installation of Alfresco.

Laurent.

[kevinr]

Is it possible that you rename the default language pack included in the common Alfresco distribution, adding "en_EN", so that multilanguage works well when we add some other language ?

As far as i know, it won't disturb a mono-language installation of Alfresco.

Unfortuntely at the moment it will, there is a  bug raised that adding the en_EN to the default english pack causes an issue. I can't actually remember what the issue if off hand, but we'll take a another look at it so this can be the case.

Thanks,

Kevin

[lgr]

Unfortuntely at the moment it will, there is a  bug raised that adding the en_EN to the default english pack causes an issue. I can't actually remember what the issue if off hand, but we'll take a another look at it so this can be the case.

Yes, I confirm.
I've renamed *.properties into *_en_EN.properties (i have french message files _fr_FR in the message directory as well), alfresco launched well, but catalina.out has been filled with plenty of error messages dealing with application.model.

My CIFS share has also been broken, and only a server and workstation reboot has made it work again.

Laurent.

[lgr]

Unfortuntely at the moment it will, there is a  bug raised that adding the en_EN to the default english pack causes an issue. I can't actually remember what the issue if off hand, but we'll take a another look at it so this can be the case.

Yes, I confirm.
I've renamed *.properties into *_en_EN.properties (i have french message files _fr_FR in the message directory as well), alfresco launched well, but catalina.out has been filled with plenty of error messages dealing with application-model.

But it worked 🙂

Laurent.