Item13451: BuildContrib should warn about non-ascii topic uploads

pencil
Priority: Enhancement
Current State: Confirmed
Released In: n/a
Target Release:
Applies To: Extension
Component: BuildContrib
Branches:
Reported By: AdminUser
Waiting For:
Last Change By: BaseUserMapping_333
With the migration to utf-8, extension topics should really be ascii safe, as we cannot predict the encoding of the target store. We could potentially re-encode during installation in Configure::Package, but this is not necessarily safe either.

Note that BuildContrib should warn, not reject the upload. Private repositories can chose to distribute in utf-8 and this should be acceptable.

See also Item13446

-- AdminUser - 09 Jun 2015

 

ItemTemplate edit

Summary BuildContrib should warn about non-ascii topic uploads
ReportedBy AdminUser
Codebase trunk
SVN Range
AppliesTo Extension
Component BuildContrib
Priority Enhancement
CurrentState Confirmed
WaitingFor
Checkins
ReleasedIn n/a
CheckinsOnBranches
trunkCheckins
masterCheckins
ItemBranchCheckins
Release01x01Checkins
Topic revision: r1 - 09 Jun 2015, AdminUser - This page was cached on 12 May 2020 - 16:52.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy