nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Default English Pack

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.

Find more posts tagged with

Comments

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.

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

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.

Hi,

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

Laurent.

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.

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.

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

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.

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.

Hi,

Here is some modifications on v1.1.1 language pack :

Typos :
———
In Webclient :

lock_service.insufficent_preveleges=You have insufficent priveleges to realese the lock on the node (id: {0}). The node is locked by another user.
lock_service.insufficent_preveleges=You have insufficient privileges to release the lock on the node (id: {0}). The node is locked by another user.

As you see, the token "lock_service.insufficent_preveleges" should also be renamed to "lock_service.insufficient_privileges".

Duplicate terms
——————
In application-model.properties:
app_applicationmodel.aspect.app_inlineeditable.description

In Webclient:
      2 actions
      2 advanced_search
      2 all_spaces
      2 approve_flow
      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

It seems that these duplicates weren't removed from v1.1. Is it right they should be removed, or i am wrong ?

Laurent.

It seems that these duplicates weren't removed from v1.1. Is it right they should be removed, or i am wrong ?

You are quite right, we didn't get around to removing them for v1.1.1, applogies for that. I'll try to remove them for a nightly build shortly.

Thanks again for your help,

Kevin

Hi,

Always the same kind of modifications on the v1.2RC1 language pack : some messages are entered twice.

application-model_en_US.properties
      2 app_applicationmodel.aspect.app_inlineeditable.description
      2 app_applicationmodel.aspect.app_inlineeditable.title

webclient_en_US.properties
      2 actions
      2 advanced_search
      2 all_spaces
      2 approve_flow
      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

Laurent.

and you've got the same typo in lock-service :
lock_service.insufficent_preveleges=You have insufficent priveleges to realese

I think you should replace "Privelege" and "Prevelege" with "Privilege"
and modify "realese".

Laurent.

Appologies for not getting to these sooner. I have now corrected all the duplicates ready for RC2.

Thanks,

Kevin

version-service_en_US
"The node {0} cannot be restore since there is no version information available for this node."

Should be restore_d_

action-service_en_US
"A content proerty must be specified when comparing to a property of type content."

should be pro_p_erty

Can you split some messages before 1.2 release to assure smooth translation?

File: webclient_en_US

Words:
'Go', if used not only in search, should be split for translation, as is has many options of translation

'To' should be split as it's used several ways:
   as in 'from/to'
   as in 'copy to'
   as in 'send message to'
      that have to be translated separately

'Post' and 'Reply' act as both nouns and verbs.
should be split to separate translation.

BTW, what is the planned release date of 1.2? I wish my Russian LP to be available at the time 😉

Thank you.

I've added a JIRA task for this:

http://www.alfresco.org/jira/browse/AWC-504

Thanks,

Kevin

Hi Kevin,

There are some modifications in 1.2rc2.

A typo in lock-service_en_US.properties : lock_service.insufficent_privileges=You have insufficent privileges to realese

In patch-service.properties, you should use two single quotes in the following line :
patch.savedSearchesPermission.result.applied=Granted CONTRIBUTOR role to EVERYONE on 'Saved Searches' folder: {0}.

Laurent.

I've fixed them now - will be in for the next release.

Thanks again,

Kevin

I'm not sure this is a correct place to post this message…

As for lock-service_en_US.properties : lock_service.insufficent_privileges, it seems to have been worse in ver 1.2.

Now it is
lock_service.insufficent_preveleges=You have insufficent priveleges to realese the lock on the node (id: {0}). The node is locked by another user.

I couldn't find how to translate "Create" menu titile which is located at the left of "More Actions" on the spaces' menu area.

I think there is no property having just 'Create' value in default Language pack.

I guess 'create_options' is missing in Language packs.

Hi All,

Here is some comments about v1.3 messages in dictionnary-messages :

- d_dictionary.constraint.err.type_and_ref and d_dictionary.constraint.err.type_or_ref have the same message with an "and".

- d_dictionary.constraint.string_length.non_string and d_dictionary.constraint.list_ov_values.non_string have the same message (i don't think this is an error).

- d_dictionary.property.err.cannot_relax_mandatory and d_dictionary.property.err.cannot_relax_mandatory_enforcement end with "''{0}" (no double single quotes end)

Laurent.

Hi,

Some duplicates found in webclient.properties :
- content_format
- recover_all_items
- delete_all_items

Laurent.

Some duplicates found in webclient.properties :
- content_format
- recover_all_items
- delete_all_items

I have removed those duplicates ready for the next release drop.

Thanks,

Kevin

Hi All,

Many message are hardcoded in the source, and they can't be translated. An example:
In ./java/org/alfresco/web/bean/wizard/NewUserWizard.java :
throw new AlfrescoRuntimeException("A Home Space with the same name already exists.");

In fact, i haven't found any AlfrescoRuntimeException taking a translated message as an argument.

Will these message be translatable someday, or is it impossible to do so ?

Laurent.

All exception messages are translatable (the constructor to AlfrescoRuntimeException() takes a Msg String ID by default) - the message in NewUserWizard can be considered a bug if it is not passing an ID.

Thanks,

Kevin

Hi Kevin,

I'm sorry, but i didn't saw any MessageID in AlfrescoRuntimeException.
Some examples :
in ./java/org/alfresco/repo/content/cleanup/ContentStoreCleaner.java :
            throw new AlfrescoRuntimeException("Property 'transactionService' not set");
            throw new AlfrescoRuntimeException("Property 'stores' not set");

in ./java/org/alfresco/repo/webdav/PropFindMethod.java :
            throw new AlfrescoRuntimeException("XML processing error", ex);
            throw new AlfrescoRuntimeException("XML write error", ex);

in ./java/org/alfresco/util/ISO8601DateFormat.java :
            throw new AlfrescoRuntimeException("Failed to parse date " + isoDate, e);
            throw new AlfrescoRuntimeException("Failed to parse date " + isoDate, e);

They are not messagesID at all, but as i did not go very further in the java code, perhaps they aren't used ? (or aren't all AlfrescoRuntimeException untranslatable ?)

Laurent.

You are correct, they are not many message IDs being used in AlfrescoRuntimeException. The exception class is expecting a message ID, when it fails to lookup a message by ID (e.g. when a string is passed like you have seen) then it defaults to displaying the original string as the message instead. This is how we created backward compatibility for AlfrescoRuntimeException when we added I18N support for it.

Generally a runtime exception is a serious runtime issue that is not supposed to be visible by the user. However in the real word this happens quite a lot

so you can seeing these messages appearing. The bug fix is that we replace those messages with IDs instead.

Thanks,

Kevin

ok, so you'll be glad if we notice you some exceptions that appear in the real world instead of a message ID being used ?

Things seems clear now

Laurent.

Hi,

There is a typo in bpm messages, key bpm_businessprocessmodel.type.bpm_workflowTaskTitle.

Worflow => Workflow

Laurent.