Issue Details (XML | Word | Printable)

Key: JRA-11331
Type: New Feature New Feature
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Vincent Thoulé
Votes: 7
Watchers: 6
Operations

If you were logged in you would be able to see more operations.
JIRA

I18n with CustomField

Created: 19/Oct/06 08:03 AM   Updated: 23/Jan/08 09:42 AM
Component/s: Custom Fields, Internationalisation
Affects Version/s: 3.6.5
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Marc Paquette, Mel Belacel, Nick Menere [Atlassian] and Vincent Thoulé
Since last comment: 36 weeks, 6 days ago
Labels:


 Description  « Hide
Following an old issue (JRA-6481), our requirment for i18n implementation is more and mroe important at the moment.
  • May we know when a such feature will be implemented in future release ?
  • Trying to understand how customfield rendering is done, I found a way to apply i18n translation.
    I proceed so :
    • Creating the CustomField as i18n keys : myCustomField
    • Adding the CustomField property value in a rebuild language_fr_FR.jar
      com/atlassian/jira/web/action/JiraWebActionSupport_fr.properties
      myCustomField=Mon Champ personnalisé
    • Adding the CustomField property value in a rebuild language_en_UK.jar
      com/atlassian/jira/web/action/JiraWebActionSupport_en.properties
      myCustomField=My Custom Field
    • ... and alos for any other required languages.
    • Modifying templates/plugins/jira/macros.vm as follow :
      • a new Macro
        ## I18n Headers required for CustomFields
        #macro(i18nCustomName $action $name)
            #set ($wordPos = $name.indexOf(" "))
            #if ($wordPos>0) 
            	#set($key=$name.substring(0,$wordPos)) 
            	$action.getText($key) $name.substring($wordPos,$name.length())
            #else
            	$action.getText($name)
            #end
        #end
      • Replacement of
        #if ($required)
            <span class="required" title="$action.getText("common.forms.requiredfields")"><sup>*</sup>
            $name:
            </span>
        #else
            $name:
        #end

        by

        #if ($required)
            <span class="required" title="$action.getText("common.forms.requiredfields")"><sup>*</sup>
            #i18nCustomName($action $name) :
            </span>
        #else
            #i18nCustomName($action $name) :
        #end
    • Modify includes/panels/issue/view_customfields.jsp as follow :
      Replacement of
      <tr id="rowFor<webwork:property value="./id" />">
          <td bgcolor="f0f0f0" width="20%" valign="top"><b><webwork:property value="name" />:</b></td>
          <td bgcolor="ffffff" width="80%">
              <webwork:property value="/customFieldHtml(../fieldLayoutItem,., /issueObject)" escape="false" />
          </td>
      </tr>

      by

      <tr id="rowFor<webwork:property value="./id" />">
          <td bgcolor="f0f0f0" width="20%" valign="top"><b><webwork:property value="text(./name)" />:</b></td>
          <td bgcolor="ffffff" width="80%">
              <webwork:property value="/customFieldHtml(../fieldLayoutItem,., /issueObject)" escape="false" />
          </td>
      </tr>

Please, let me know if I may implement this, waiting the future feature ?
What other problem may I encounter ? Probably Word and Excel rendering, I suppose ?

Rgds
Vincent



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Mel Belacel added a comment - 13/Nov/06 06:31 AM
Hi,

Is there any update on this issue?

MB


Vincent Thoulé added a comment - 13/Nov/06 06:45 AM
Hi Mel,

I am always waiting for a return, too !

Vincent


Vincent Thoulé added a comment - 05/Jan/07 05:55 AM
Is it possible to have a return for this issue ?
Rgds
Vincent

Mel Belacel added a comment - 05/Jan/07 08:14 AM
It is quite important indeed, some feedback would be appreciated.

Regards

Mel


Nick Menere [Atlassian] added a comment - 07/Jan/07 05:30 PM
Sorry guys,
No news on this one yet. We haven't scheduled it yet but will update when we do. Sorry I can't provide a more definitive answer.

Cheers,
Nick


Mel Belacel added a comment - 31/Jan/07 09:02 AM
Are there any plans to implement this feature at all?

Regards

Mel


Vincent Thoulé added a comment - 15/Feb/07 08:17 AM
Hi Nick and Atlassian guys,

I suppose that I18n for Customfield is not yet scheduled, but my initial request was not only if the requirement of this new feature.

I am also interesting to know if my proposed solution is acceptable and will not go against your future solution.

In my company, we are about to deploy JIRA for more that 3000 users with French, English and Italian people.

Thanks per advance.
Vincent


Nick Menere [Atlassian] added a comment - 25/Feb/07 05:26 PM
Sorry Vincent,
Been on holidays.

The main problem with i18n of custom fields is that the custom field names are configurable at run time and hence the translations will not be stored in property files, more likely the database.

That being said, your method should not go against our solution. I.e. you should require little change to make it compatible. (though it is hard to say before implementing the solution)

Cheers,
Nick


Marc Paquette added a comment - 23/Jan/08 09:42 AM
I just wanted to add my voice in favor of a permanent solution for this problem (I've already added my vote). It came as a suprise to me that this wasn't supported, but I understand the technical stumbling blocks behind this.

I wonder how many people think that "internationalized jira" includes "custom fields" ... ?

For the record, I've implemented Vincent's method in my copy of 3.10.2 and it works like a charm. Merci infiniment Vincent.